Downloaded 542 times
Uploaded byAdnan Aziz
Agile Release Planning
The document outlines agile release planning, emphasizing the importance of defining goals, features, and timelines for successful software releases. It highlights the roles of the product owner and team collaboration in prioritizing tasks, assessing risks, and achieving shared commitment. Continuous planning and validation, as well as maintaining flexibility, are key components for delivering high-value products efficiently.
More Related Content
Similar to Agile Release Planning
Agile Release Planning
- 1.
- 2. AREAS OF LEARNING Typical Story of a Release Roadmap to Value Vision Product Roadmap Release Planning Learnings
- 3. TYPICAL STORY OF ARELEASE
- 4. SOMEONE DEFINES THE ROADMAPFOR YOU
- 5. FEATURES AND RELEASEDATE IS SELECTED FOR YOU
- 6. TEAM STARTS WORKON RELEASE
- 7. AHHHA WE LIVEON PLANET EARTH AND WORK IN THE SOFTWARE INDUSTRY
- 8. TIME RUNS OUT ANDPRESSURE MOUNTS
- 9. Drumbeats get faster,faster ……and faster
- 10. TEAM IS WHIPPED UPTO RAMMING SPEED
- 11.
- 12.
- 13.
- 14. Does this situationbring out the best in people?
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 24.
- 25.
- 26. VISION The goals ofthe product and its alignment with the company’s strategy OWNER Product Owner FREQUENCY At least annually
- 27.
- 28. PRODCUT ROADMAP Holistic viewof product features that create the product vision OWNER Product Owner FREQUENCEY At least biannually
- 29.
- 30. RELEASE PLANNING High priorityfeatures release timing for specific product functionality OWNER Product Owner FREQUENCEY At least quarterly
- 31. PURPOSE Define andunderstand 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. 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
- 34. CONTINUES PLANNING Shippable Increment After Every Release Release4Release 3Release 2Release 1 In agile projects we plan continuously Allow course correction in response to feedback
- 35. WHO IS INVOLVED ProductOwner #TIP Involve any other stakeholders that can add valuable input Developers Testers UX SME’s BA’s
- 36. IN RELEASE PLANNINGMEETING 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
- 37. IN RELEASE PLANNINGMEETING 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
- 38. TEAM DECIDES ANDTEAM 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
- 39. END RESULT Release 4 Release 3 Teamcommitted to release plan with clear understanding Build flexibility to better plan your future releases … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … Product Backlog
- 40. RELEASE GOTCHA’S Release 2 Release Planning Release Validation Release1 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
- 41.
- 42. DEVELOP A SHAREDVISION
- 43. THINK ABOUT COMMONPURPOSE
- 44. BUILD SENSE OFSHARED OWNERSHIP
- 45.
- 46.
- 47. “High-quality games ata lower cost that are as fun to develop as they are to play”
- 48. Care to shareyour experience? THANK YOU www.agilehash.com twitter.com/adnanaziz * All images collected through Google, Flickr
Editor's Notes
- #8 # Ahhha moment for team…. # Ohh project is not a rollercoaster ride # We live in planet earth and work in software industry
- #9 # Lots of meetings are organised # People are told to lift up their game
- #11 # Sometimes they are asked to work extra hours # Lots of meetings are held at that time # At times it feels like team is preparing for a ‘WAR’
- #12 # This type of pressure creates a negative spiral # It’s all downwards feeling from here onwards….
- #16 # Damages relations between team and those applying the pressure # It sets a precedent for work performance # We’ve to understand ‘pressure is a reality it is there at every level of organisation # It can boost performance in a short time but for long term we need to measure pressure
- #32 # what outcome you like to achieve from customer’s point of view # what will be specific shippable product increment
- #33 # Highly recommended planning session # Team determines, based on their velocity (prior or estimated) # Release planning is not a commitment to precise details
- #35 # Continues course correction #Features, architectural choices, design choices, or framework or technology choices might prove to be too risky or simply unworkable. The user interface might require revision. Staff might be lost or added. Feature priorities might change. All of these factors will help us revise and refine the release plan continuously.
- #36 # goal is to be on common page collectively
- #37 # use data driven conversation
- #38 # usually teams go into details in their iteration planning meetings
- #39 # usually teams go into details in their iteration planning meetings
- #43 # This is a inclusive process # It will give you the sense of commonality
- #44 # Develop a common purpose # It will convert people from ‘yet another project’ to ‘our project’
- #45 # Let team make important decision
- #46 # Explain the motivation behind the project # Explain why, how and what?