Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 77 views

    Agile Summary

    Uploaded by

    Ali Asghar
    Agile project management breaks down long development cycles into short, iterative sprints of 2-4 weeks where small segments of a product are specified, developed, and tested. This reduces complexity compared to traditional approaches. Key aspects of agile include sprints, daily stand-ups, product backlogs prioritized by a product owner, and sprint planning and retrospectives to continuously improve the process.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Agile Summary

    Uploaded by

    Ali Asghar
    77 views6 pages
    Agile project management breaks down long development cycles into short, iterative sprints of 2-4 weeks where small segments of a product are specified, developed, and tested. This reduces complexity compared to traditional approaches. Key aspects of agile include sprints, daily stand-ups, product backlogs prioritized by a product owner, and sprint planning and retrospectives to continuously improve the process.

    Original Description:

    agile summary pmp

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Agile project management breaks down long development cycles into short, iterative sprints of 2-4 weeks where small segments of a product are specified, developed, and tested. This reduces complexity compared to traditional approaches. Key aspects of agile include sprints, daily stand-ups, product backlogs prioritized by a product owner, and sprint planning and retrospectives to continuously improve the process.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    77 views6 pages

    Agile Summary

    Uploaded by

    Ali Asghar
    Agile project management breaks down long development cycles into short, iterative sprints of 2-4 weeks where small segments of a product are specified, developed, and tested. This reduces complexity compared to traditional approaches. Key aspects of agile include sprints, daily stand-ups, product backlogs prioritized by a product owner, and sprint planning and retrospectives to continuously improve the process.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 6

    Agile Project Management

    Agile Project Management reduces complexity by breaking down the many-months-


    long cycle of building requirements for the whole project, building the entire product
    and then testing to find hundreds of product flaws. Instead small, usable segments
    of the product are specified, developed and tested in manageable, two- to four-week
    cycles.

    Some Important Terms


    • Agile: A conceptual framework for undertaking software projects. Agile methods
    are a family of development processes, not a single approach to software
    development

    • Agile Coach: The team facilitator is called the Agile Coach or Scrum Master.
    Their job is to implement and manage the Agile/Scrum processes in the project.
    Scrum masters serve a facilitator role and their authority is mostly indirect.

    • Scrum: Scrum is a lightweight agile method for software development. Scrum is


    named after the Scrum in rugby, which is a way to restart the game after an
    accidental infringement. It is based on the adaptive methodology of software
    development

    • Sprint / Iteration: A sprint is defined as a 2-5 week increment of software


    development activities that delivers working software and the end of the
    increment.

    • Product Owner: The customer for whom the project is being performed is
    termed the product owner. This person is knowledgeable of the business and is
    responsible for prioritizing the work that the team will tackle in each sprint

    • Sprint Planning: Is a pre sprint planning meeting attended by the core agile
    team. During the meeting the Product Owner describes the highest priority
    features to the team as described on the product backlog. The team then agrees
    on the number of features they can accomplish in the sprint and plans out the
    tasks required to achieve delivery of those features. The planning group works
    the features into User Stories and assigns Acceptance criteria to each story.

    • Daily Standup/Scrum: Each day the Scrum Master leads the team in the
    Daily Scrum Meeting. This meeting designed to provide status on the progress of
    the sprint. Each team member speaks to three questions: what did I do
    yesterday, what did I do today, and what impediments got in my way?

    • Sprint Review: Each Sprint is followed by a Sprint review. During this review
    the software developed in the previous Sprint is reviewed and if necessary new
    backlog items are added.

    • User Stories: A user story is a very high-level definition of a requirement,


    containing just enough information so that the developers can produce a
    reasonable estimate of the effort to implement it

    • Product Backlog: Acts as a repository for requirements targeted for release


    at some point. These are typically high level requirements with high level
    estimates provided by the product stakeholders. The requirements are listed on
    the backlog in priority order and maintained by the product owner.

    • Burndown: A burndown chart is a simple visual tool for measuring and


    managing sprint progress. Visually, a burndown chart is nothing more than a line
    chart representing remaining work over time. Burndown charts are used to
    measure the progress of an agile project at both a micro and macro level. ( Page
    62 )

    • Sprint Backlog: At the beginning of each sprint, the team has sprint planning
    with an end result being a backlog of work that the team anticipates completing
    at the end of the sprint. These are the items that the team will deliver against
    throughout the duration of the sprint

    • Team Velocity: It is a relative number which describes how much work the
    team can get done per sprint
    • Retrospective: A team meeting to review lessons learned. It is based on the
    principles of applying the learning from the previous sprint to the upcoming sprint.

    Agile Approaches
    1. SCRUM
    Sprint

    Sprint planning

    Daily scrum

    Sprint review

    Sprint retrospective

    Product backlog

    Sprint backlog

    Increments

    2. EXTREME PROGRAMMING
    User stories

    10-minute build

    Daily standups

    Daily deployment

    3. KANBAN METHOD
    It was applied at the main Toyota manufacturing facility in 1953

    Kanban Board

    The Kanban Method is a holistic framework for incremental, evolutionary process and systems
    change for organizations. The method uses a “pull system” to move the work through the process.
    When the team completes an item, the team can pull an item into that step.
    4. CRYSTAL METHODS

    5. SCRUMBAN
    In Scrumban, the work is organized into small “sprints” and leverages the use of kanban boards
    to visualize and monitor the work

    6. FEATURE-DRIVEN DEVELOPMENT

    7. DYNAMIC SYSTEMS DEVELOPMENT METHOD


    The framework will set cost, quality, and time at the outset, and then use formalized
    prioritization of scope to meet those constraints

    8. AGILE UNIFIED PROCESS

    9. SCRUM OF SCRUMS (Scrum of Scrums (SoS), also known as “meta


    Scrum,”)
    It is used when two or more Scrum teams consisting of three to nine members each need to
    coordinate their work instead of one large Scrum team.
    10. SCALED AGILE FRAMEWORK

    11. LARGE SCALE SCRUM (LeSS)

    12. ENTERPRISE SCRUM

    13. DISCIPLINED AGILE (DA)

     Uncertainty and complexity model page 14


     Characteristics of project life cycle page 18
     Iteration based and flow based agile page 24
     Servant leadership page 33
     Agile team roles page 41
     Story points burndown chart page 62
     Kanban board page 65
     Features chart page 67
     Agile in knowledge areas page 91 to 93

    You might also like