Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile Release Planning

9,025 views

Published on

Understand how command & control release plans create false hopes and low quality products because there is no team buy-in.

Learn how to develop vision and use your your vision to drive the release plan workshop. Use patterns to validate your release.

Lastly you must learn from your release plan and improve the next release (inspect & adapt).

Published in: Software, Technology, Business
  • If you need your papers to be written and if you are not that kind of person who likes to do researches and analyze something - you should definitely contact these guys! They are awesome ⇒⇒⇒WRITE-MY-PAPER.net ⇐⇐⇐
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • There is a useful site for you that will help you to write a perfect. And valuable essay and so on. Check out, please HelpWriting.net
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Dating direct: ❶❶❶ http://bit.ly/2Qu6Caa ❶❶❶
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Dating for everyone is here: ❤❤❤ http://bit.ly/2Qu6Caa ❤❤❤
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Agile Release Planning

  1. 1. AGILE RELEASE PLANNING BY ADNAN AZIZ
  2. 2. AREAS OF LEARNING  Typical Story of a Release  Roadmap to Value  Vision  Product Roadmap  Release Planning  Learnings
  3. 3. TYPICAL STORY OF A RELEASE
  4. 4. SOMEONE DEFINES THE ROADMAP FOR YOU
  5. 5. FEATURES AND RELEASE DATE IS SELECTED FOR YOU
  6. 6. TEAM STARTS WORK ON RELEASE
  7. 7. AHHHA WE LIVE ON PLANET EARTH AND WORK IN THE SOFTWARE INDUSTRY
  8. 8. TIME RUNS OUT AND PRESSURE MOUNTS
  9. 9. Drumbeats get faster, faster ……and faster
  10. 10. TEAM IS WHIPPED UP TO RAMMING SPEED
  11. 11. WHAT THIS PRESSURE DOES TO A TEAM
  12. 12. Pressure Fatigue More Mistakes More Work do { ......... } while(true)
  13. 13. SUPERHEROS SAVES THE RELEASE
  14. 14. Does this situation bring out the best in people?
  15. 15. THIS SITUATION DAMAGES THE ENTHUSIASM
  16. 16. STAGES TO ALUE
  17. 17. ROADMAP TO VALUE
  18. 18. ROADMAP TO VALUE
  19. 19. ROADMAP TO VALUE
  20. 20. ROADMAP TO VALUE
  21. 21. ROADMAP TO VALUE
  22. 22. ROADMAP TO VALUE
  23. 23. ROADMAP TO VALUE
  24. 24. ROADMAP TO VALUE
  25. 25. ISION
  26. 26. VISION The goals of the product and its alignment with the company’s strategy OWNER Product Owner FREQUENCY At least annually
  27. 27. OADMAP
  28. 28. PRODCUT ROADMAP Holistic view of product features that create the product vision OWNER Product Owner FREQUENCEY At least biannually
  29. 29. ELEASE LANNING
  30. 30. RELEASE PLANNING High priority features release timing for specific product functionality OWNER Product Owner FREQUENCEY At least quarterly
  31. 31. PURPOSE  Define and understand a goal for the release  Define what features can be released  Confirm the date for the release  Have everyone in the team understand and commit to delivering the agreed release by the agreed date
  32. 32. A PLANNING SESSION  Features and themes are reviewed and prioritized  Key dates and milestones are established  Team determines roughly which features will be delivered in the timeframe identified  Goal is to produce a high-level release plan with delivery dates #TIP Don’t go into too much detail, leave that to iteration planning
  33. 33. CONTINUES PLANNING Shippable Increment After Every Release Release 4Release 3Release 2Release 1  In agile projects we plan continuously  Allow course correction in response to feedback
  34. 34. WHO IS INVOLVED Product Owner #TIP Involve any other stakeholders that can add valuable input Developers Testers UX SME’s BA’s
  35. 35. IN RELEASE PLANNING MEETING  Product owner explains the key objectives that business needs to achieve from this release  Product owner helps to understands the motivation behind the release  Based on prioritized backlog of features meaningful conversation beings #TIP Release planning will run more smoothly and take less time if you’re prepared
  36. 36. IN RELEASE PLANNING MEETING  Business value is questioned to build common consensus  Developers assess technical risks  Rough estimates are established  New stories are created if there are some technical unknowns  Consensus needs to be reached on the release plan with everyone present stating their commitment verbally #TIP Don’t get bogged down into details, it’s important to remain focused and to maintain a brisk pace
  37. 37. TEAM DECIDES AND TEAM COMMITS  Team knows its throughput based on their prior experiences  Team understands their capability to deliver the release  Enough details are provided for team to understand the motivation behind the release  Team is involved in rough estimation and risk identification conversation  Team decides which features can be delivered and gives commitment to the product owner #TIP Shared goals and shared conversation create great products
  38. 38. END RESULT Release 4 Release 3  Team committed to release plan with clear understanding  Build flexibility to better plan your future releases … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … Product Backlog
  39. 39. RELEASE GOTCHA’S Release 2 Release Planning Release Validation Release 1 Release Planning Release Validation Release 3 Release Planning Release Validation  Planning and validation must be considered when planning a release  Release validation ensures that desired outcomes are achieved
  40. 40. EARNINGS
  41. 41. DEVELOP A SHARED VISION
  42. 42. THINK ABOUT COMMON PURPOSE
  43. 43. BUILD SENSE OF SHARED OWNERSHIP
  44. 44. COMMUNICATE ‘WHY’
  45. 45. CREATE EXCITEMENT AROUND BUSINESS RESULTS
  46. 46. “High-quality games at a lower cost that are as fun to develop as they are to play”
  47. 47. Care to share your experience? THANK YOU www.agilehash.com twitter.com/adnanaziz * All images collected through Google, Flickr

×