Agile Workshop: Handling Changing Requirements

2,298 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,298
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
71
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Agile Workshop: Handling Changing Requirements

    1. 1. Adapting to Changing Requirements Short Iterations Frequent Releases, Customer Collaboration <ul><li>Balachander Swaminathan </li></ul><ul><li>March 20, 2009 </li></ul>© ThoughtWorks 2009
    2. 2. <ul><li>The Idea of Adaptive Planning ..... </li></ul>© ThoughtWorks 2009
    3. 3. Adaptive Planning <ul><li>Is planning to deliver, not delivering to a plan </li></ul><ul><ul><li>Change can be accommodated, and is expected </li></ul></ul><ul><ul><li>The impact of change is visible to all stakeholders </li></ul></ul><ul><ul><li>Is repeated throughout the project lifecycle </li></ul></ul><ul><li>Is a simple process, transparent to the whole team </li></ul><ul><li>Balances different levels of precision/granularity </li></ul><ul><ul><li>Release Planning (weeks) and Quarterly Cycles </li></ul></ul><ul><ul><li>Iteration Planning (days) and Weekly Cycles </li></ul></ul>© ThoughtWorks 2009
    4. 4. 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 $ $ $
    5. 5. Decomposing a release… Prioritized Release Level Stories Iterations Stories Completed Business Value Delivered © ThoughtWorks 2009 Release X
    6. 6. 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
    7. 7. <ul><li>Segregating Stories into Release Buckets ….. </li></ul>© ThoughtWorks 2009
    8. 8. Segregation of Stories <ul><li>Segregate stories into releases </li></ul><ul><li>Each release provides business value </li></ul>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
    9. 9. Iteration Execution for a Single Release <ul><li>Iteration plan for only the next iteration </li></ul><ul><li>Retain flexibility to prioritize future stories </li></ul><ul><li>Done stories are done (new story to change) </li></ul>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
    10. 10. 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
    11. 11. 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
    12. 12. <ul><li>Short Iterations provide an avenue for the customer to provide quick feedback to the development team </li></ul><ul><li>Frequent Releases enable the customer to quickly take to market their ideas and thereby get direct feedback from their customers </li></ul><ul><li>Adaptive planning uses short iterations and frequent releases to meet up with continuously changing customer requirements </li></ul><ul><li>But this can only happen if there is constant collaboration between the customer and the development team </li></ul>Summary © ThoughtWorks 2009
    13. 13. <ul><li>Thank You </li></ul><ul><li>Balachander Swaminathan </li></ul><ul><li>(bala@thoughtworks.com) </li></ul>© ThoughtWorks 2009

    ×