Release Planning. For Agile Teams. A Quick Overview
-
Upload
michael-benning -
Category
Software
-
view
326 -
download
3
description
Transcript of Release Planning. For Agile Teams. A Quick Overview
![Page 1: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/1.jpg)
{Release Planning
For Agile teams. A quick overview.
![Page 2: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/2.jpg)
Defines the scope a team intends to deliver by a given deadline
A Release Plan
![Page 3: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/3.jpg)
About the Planning Determined by the Product Owner, Team,
& Scrum Coach Constructed from a preliminary feature
list Identified Prioritized Estimated (optional)
Initially rough and constantly evolving
A Release Plan is
![Page 4: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/4.jpg)
About The Plan Defined by 1 person Inflexible Refined
A Release Plan isn’t
![Page 5: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/5.jpg)
{ {Date Driven
Determine the features that can be delivered by a proposed date
Scope Driven
Determine a rough date to deliver a set of features
2 Main Approaches
![Page 6: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/6.jpg)
Dependency Driven
Determine the delivery sequence based on dependency releases
3rd Approach
![Page 7: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/7.jpg)
Shorter than a year (3-6 months, usually)*
Made up of iterations
Agile Release Cycles*Some Agile institutions can release up to multiple times daily
![Page 8: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/8.jpg)
{Story Points/Velocity X Iterations = Timeline
Sample Release Plan
![Page 9: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/9.jpg)
{Story Points/Velocity X Iterations = Timeline
Sample Release Plan
![Page 10: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/10.jpg)
{Story Points/Velocity X Iterations = Timeline
Sample Release Plan
![Page 11: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/11.jpg)
{Story Points/Velocity X Iterations = Timeline
Sample Release Plan
![Page 12: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/12.jpg)
Team velocity changes Much Faster Much Slower
After several iterations When interference arises Every iteration (ideally)
Update the release plan when…
![Page 13: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/13.jpg)
Management desires transparency Team desires a timeline for product
release ROI should be predicted Multi-team releases of an integrated
product When a project requires long term
planning
When is a Release Plan most valuable?
![Page 14: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/14.jpg)
Costs & Benefits
Benefits Reduces Risk Reduces Uncertainty Supports Better
Decision Making Establishes Trust Conveys Information ROI predicted
Costs Administrative
overhead Release planning
meetings Artifacts to maintain
Overhead For Product Owner
Potential for Interference
![Page 15: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/15.jpg)
Is not about the plan but about the planning
Is driven by scope, date, or dependency Evolves over the course of the project Is developed by the entire team Can help identify ROI and reduce risk or
uncertainty
To summarize, Release Planning
![Page 16: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/16.jpg)
Helpful references for release planning:• http://www.extremeprogramming.org/• http
://www.versionone.com/Agile101/Agile-Development-Release-Planning/
• http://www.mountaingoatsoftware.com/books/agile-estimating-and-planning
![Page 17: Release Planning. For Agile Teams. A Quick Overview](https://reader035.fdocuments.in/reader035/viewer/2022062513/554fb2afb4c90586258b5256/html5/thumbnails/17.jpg)
Thank you!
Michael R. Benning, CSMwww.linkedin.com/in/michaelbenning/