The document discusses release planning using feature point estimation. It describes estimating stories in points and using velocity to determine how many points a team can complete in a release. It recommends planning releases based on important features and team capacity, and involving product owners, leads, architects and QA. Feature points use a higher Fibonacci series like 20, 40, 60, 100 to estimate story size, and a release plan can track scope progress and velocity over the course of the release.

1. Release Planning
Using
Feature Point Estimation
~ Savita Pahuja

2. Product Releases
Product
Version 3.0
Product
version 2.0
MVP
Minimum
Viable
Product
Version 1.0
R1 R2 R3 R4 R5 R6
Product Enhancement

3. Release Planning

5. Release Plan - Estimation Techniques & Challenges
Story points
Velocity
Dog Points T-Shirt Sizing

6. Product Increment
Plan a Release based upon:
1) Most Important features to be
delivered
2) Capacity of the delivery teams
Who all are involved?
- Product Owners, Tech Leads, Senior
Architects, Senior QA etc.
Based On:
1) By Scope
2) By Date

7. Feature Point Estimation
Higher Fibonacci Series Numbers:
20, 40, 60, 100, 160 ...

8. Techniques
60
40

9. Scope Progress

10. Scope Progress

11. Release Velocity
10%
Number of Feature Points completed in a release.

12. Let‘s Create a Release Plan
Product Release