Agile Workshop: Handling Changing Requirements

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    Agile Workshop: Handling Changing Requirements - Presentation Transcript

    1. Adapting to Changing Requirements Short Iterations Frequent Releases, Customer Collaboration
      • Balachander Swaminathan
      • March 20, 2009
      © ThoughtWorks 2009
      • The Idea of Adaptive Planning .....
      © ThoughtWorks 2009
    2. Adaptive Planning
      • Is planning to deliver, not delivering to a plan
        • Change can be accommodated, and is expected
        • The impact of change is visible to all stakeholders
        • Is repeated throughout the project lifecycle
      • Is a simple process, transparent to the whole team
      • Balances different levels of precision/granularity
        • Release Planning (weeks) and Quarterly Cycles
        • Iteration Planning (days) and Weekly Cycles
      © ThoughtWorks 2009
    3. Adaptive Planning: Change in outlook Frequent Releases © ThoughtWorks 2009 Fix / Integrate $ Test Code Design Specifications Use Cases / Functional Specs Requirements Gathering Project Plan/Estimation $ Inception $ $ $
    4. Decomposing a release… Prioritized Release Level Stories Iterations Stories Completed Business Value Delivered © ThoughtWorks 2009 Release X
    5. Release Plan Project Release Plan Release X Release X+1 Dev. QA Dev. QA Dev. QA Dev. QA Dev. QA Dev. QA Dev. QA Dev. QA Dev. QA Dev. QA Dev. QA Dev. QA Scheduled release Anal. Anal. Anal. Anal. Anal. Anal. Anal. Anal. Anal. Anal. Anal. Anal. Scheduled * release Scheduled release Scheduled milestone Scheduled milestone *Typical for large companies which have their own final QA (UAT) and Deployment setup. Scheduled release will factor in final QA and Deployment Iteration © ThoughtWorks 2009 Iteration
      • Segregating Stories into Release Buckets …..
      © ThoughtWorks 2009
    6. Segregation of Stories
      • Segregate stories into releases
      • Each release provides business value
      I 1 …….I n I 1 …….I n I 1 …….I n Release x Release x+1 Release x+2 © ThoughtWorks 2009 S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S
    7. Iteration Execution for a Single Release
      • Iteration plan for only the next iteration
      • Retain flexibility to prioritize future stories
      • Done stories are done (new story to change)
      I 1 …….I n Iterations Done In Progress Next Future Release x © ThoughtWorks 2009 S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S
    8. Changing Priorities… Changing Priorities Additions - Deletions - Change with New Story © ThoughtWorks 2009 S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S
    9. Changing Priorities … Including Release Boundaries New Plan Original Plan Iterations Release x Release x+1 Release x+2 Release x Release x+1 Release x+3 Release x+2 © ThoughtWorks 2009 S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S
      • Short Iterations provide an avenue for the customer to provide quick feedback to the development team
      • Frequent Releases enable the customer to quickly take to market their ideas and thereby get direct feedback from their customers
      • Adaptive planning uses short iterations and frequent releases to meet up with continuously changing customer requirements
      • But this can only happen if there is constant collaboration between the customer and the development team
      Summary © ThoughtWorks 2009
      • Thank You
      • Balachander Swaminathan
      • (bala@thoughtworks.com)
      © ThoughtWorks 2009

    + SiddhiSiddhi, 8 months ago

    custom

    557 views, 0 favs, 0 embeds more stats

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 557
      • 557 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 16
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories