D5 - Adaptive Planning Flashcards
Examples of interactive planning
daily, BL prioritization, retro, iteration planning
This is an elevator pitch that articulates the product end goal
product vision statement
This is a high level overview of functionality required to achieve product vision
product roadmap
This outlines the next set of functionality that will go into production
release planning
This is a list of tasks for the team to create a potentially shippable product
sprint/iteration backlog
This is a fully developed working product that is then outcome of a sprint
increment
Characteristics of adaptive planning
value driven, minimize non value add work, plan to re-plan, early plans are flawed, uncertainty requires re-planning
This will uncover true requiments
trial and demo
Characteristics of iterative planning
effort is distributed, agile projects are risky, and more planning is required
changes to plans in agile projects are
normal
knowledge work doesn’t follow a
predictive plan
we do this as more information becomes available
progressive elaboration
This is way of planning in chunks
rolling wave
This is then business benefit - the cost
value based analysis
Characteristics of value based decompistion
elicit requirements, group features, break down features, ranking and prioritization
Tool to imagine product features and elements expressed as a graphic
product box
this level of requirement identification is high level and delays decisions to that last responsible moment
course grained
timebox of the daily
15 min
timebox of the retro
2 hours
timebox of the iterations
1-4 weeks
timebox of the daily
ideal work items per sprint
12
work items not completed
go to backlog
Parkinson’s law
work expands to fill allotted time
This graph shows flaws of original estimates, and variance change as more information becomes available
estimate convergence graph
estimating should happen
at the last responsible moment
Who estimates?
the team
ideal time is
estimate if there were no interruptions and assumes all time in the estimate is for project work
User story formats
given when then or as a I need so I can
The three c’s
card conversation confirmation
invest
independent, negotiable, valuable estimate, small; and testable
This estimates size based on analgous,
relative
story points
overall effort and accounts for time, risk, complexity
fib seq
1, 2, 3,5, 8, 13, 21
Who decides when the product is released
the po
Question’s to ask for release planning
where is the po, do we have a pri backlog, how do we size, who is coming, plan logistics, multiple teams, do we need help
inputs for release planning
previous release, feedback from SH, action plan and smart goals, for prior release or retro, items and defects to consider, dev or arch info, velocity, org calendars, input from other teams
this groups items based on similar feature size or pri
affinity estimating
This is a visualization of releases of high level functionality and initial cut of backlog
product roadmap
Anonymous surveys to avoid group think
wide band delphi
This is an aggregate in increments
a release
first iteration with setup
iteration 0
this iteration focusses on code cleanup, documentation and compiling
Iteration H
This is a time boxed effort POC
architectural spike
This is a short effort to review risk
risk based spike
outputs of high level planning
updated backlog, course grained estimate, goals defined, release date
release planning
defines what stories are in which iteration to inform release
