Despite rumours to the contrary, there are planning activities in the agile model. In this class we’ll discuss how to plan releases, and present story mapping and impact mapping as effective tools for design, ideation and planning.
know strategies to mitigate these limitations
be able to do old-school agile release planning
understand the limitations of release planning
meet some well-known prioritization tools
understand tools for measuring progress
• What are they?
• Where do they come from?
Leaky abstractions: http://www.joelonsoftware.com/articles/LeakyAbstractions.html
stuﬀ you didn’t know about
stuﬀ you didn’t think about
doesn’t actually solve the problem
it wasn’t actually what we wanted
what could possibly go wrong?
mix of skills
architecture / non-functional requirements
Executives tend to “make decisions based on
delusional optimism rather than on a rational
weighing of gains, losses, and probabilities. They
overestimate beneﬁts and underestimate costs.
They spin scenarios of success while overlooking
the potential for mistakes and miscalculations. As
a result, they pursue initiatives that are unlikely to
come in on budget or on time or to deliver the
expected returns—or even to be completed.”
Kahneman, Thinking Fast and Slow, p252.
If everything went exactly to plan…
It would be extremely embarrassing if we didn’t hit…
“Even in projects with very uncertain
development costs, we haven't found that
those costs have a signiﬁcant information
value for the investment decision… The single
most important unknown is whether the
project will be canceled. The next most
important variable is utilization of the system,
including how quickly the system rolls out and
whether some people will use it at all.”
Douglas Hubbard | http://www.cio.com/article/119059/The_IT_Measurement_Inversion
minimize output, maximize outcome
Jeﬀ Patton, User Story Mapping p. xlii
Tom DeMarco & Tim Lister, Waltzing with Bears
Jeﬀ Patton, User Story Mapping
Douglas Hubbard, How to Measure Anything