"3. The extension
conditions of each use case provide the requirements analysts a
framework for investigating all the little, niggling things that
somehow take up 80% of the development time and budget. It provides a
look ahead mechanism, so the customer / product owner / business
analyst can spot issues that are likely to take a long time to get
answers for. These issues can and should then be put ahead of the
schedule, so that the answers can be ready when the development team
gets around to working on them. The use case extension conditions are
the second part of the completeness question.
4. The use case extension scenario fragments provide answers to the
many detailed, often tricky business questions progammers ask: "What
are we supposed to do in this case?" (which is normally answered by, "I
don't know, I've never thought about that case.") In other words, it is
a thinking / documentation framework that matches the if...then...else
statement that helps the programmers think through issues. Except it is
done at investigation time, not programming time. "
These days, iteration/sprint lengths are so short that it is not
practical to implement an entire use case in just one of them. That
means additional work is needed, to create user stories or backlog
items for each use case, track that each one get developed, and ensure
that the complete set of user stories or backlog items do indeed
deliver the subset of the use cases needed for the particular release.
Subscribe to RSS headline updates from:
The opinions expressed herein are my own personal opinions and do not represent
my employer's view in any way.
© Copyright 2005-2013, Arnon Rotem-Gal-Oz
DirectionalRedux theme by John Forsythe and Jon Stovall