CHAP. 18 RELEASE PLANNING
Product Backlog Ready for Release Planning
Item and Size; Required stories associated with must have themes; other stories that would be nice to have in release; themes and epics for future releases
Determine the Range of Features on Fixed-Date Release
Item and Size; Will have; Might have; Won't have
Location of Must-Have Features Relative to Range of Deliverable Features
Must have features has to be located in either Will Have or Might Have!
Determine Release Features
combine results of multiple sprints into one release
Outputs - Release Plan
communicates, level of accuracy that is reasonable to where in development area, when will we finish, what features will we get, what is the cost
Grooming the Product Backlog
conduct user story writing workshop; separate story writing workshop; more detailed product backlog items; estimate and prioritize
Release Planning - Balance
customer value and overall quality against constraints of scope, schedule, and budget.
Fixed Date
fix both the date and date, but the scope must be flexible; MRF are very small
Timing
frequent; every-sprint activity; follows envisioning/product level planning; determine next step toward achieving the product goal
5 Steps for Performing Fixed-Date Releasing Plannng
how many sprints are in release; groom product backlog; measure/estimate team's velocity as a range; multiply slower velocity by number of sprints; multiply the faster velocity by number of sprints
Release Planning - THREE Questions
longer term planning; answers When will we be done? Which features can I get done by the end of the year? How much will it cost?
Inputs
product backlog planning, product vision, high level product backlog, product roadmap, velocity/known velocity
Refine Minimum Releasable Features
product owner is ultimately responsible for defining the MRF
Sprint Mapping (PBI Slotting)
quick early mapping of near-term product backlog items into sprints is helpful
Updating Constraints
rebalance; define smaller set of features included in MRFs; add resources; skip launch event
Participants
stakeholders and full scrum team; make business and technical trade offs to achieve balance of value and quality
Release Planning - Goal
the most valuable next release and what the desired level of quality is
Fixed Scope
when we run out of time and haven't completed all of the features, we extend the date to ensure that we get everything required to meet MRF
