Re: [scrumdevelopment] More newbie questions...
- At 1:28 PM -0400 8/1/03, Ron Jeffries wrote:
>That's how we got where we are. Each of six sprints, just one simple taskNicely put, Ron!
>per sprint. And on the seventh sprint, He shipped it. If breaking it down
>was good enough for Him, it's good enough for me.
OTOH I'm in the middle of a government paper on precisely central
planning vs distributed market-based development for military
You quoted the central central planning myth, but of course nobody
thinks it happened that way (creationists aside; any here?).
What frustrates me is that it seems to be just as controversial to
suggest that any other way than central planning (extreme or not)
could even apply to software. Such myths die hard.
Brad J. Cox, PhD, 703 361 4751, http://virtualschool.edu
http://virtualschool.edu/mybank Digital Rights Management System
http://virtualschool.edu/jwaa Java Web Application Architecture
http://virtualschool.edu/java+ Java Preprocessor
http://virtualschool.edu/mideast Support Israel and Palestine
> From: "Christian Knott" <chrisknott@...>Christian:
> With Scrum, we get to show what's been done every 30 days. That means
> that the "alignment smell" gets to be put on view once a month
> instead of, well, never in many other cases.
But in Scrum we also show what is done every day. Remember,
"Daily Build" and "Daily Scrum" are basic Scrum patterns.
A while ago Jeff Sutherland pointed to an article written by
Martin Fowler about continuous integration. All good and dandy.
It is great to have things like Anthill produce automatic builds
and run batches of unit tests. But it is also important for
the Customer to interact with stable versions of the application
and give feedback from hands-on experience on a daily basis.
Also, there are things like Fit and Fitnesse that attempt to
Automate "acceptance testing". Our style is to do this
through "human interaction" -- there are some things that
we feel are best leaving non-automated i.e. where we want humans
In our development we have perhaps hundreds if not thousands
of builds every day, and thousands of check ins and updates,
but we advertise at least one stable build daily for the customers
to play with.
> For the specific problem of fuzzily defined requirements for reports,done.
> I'm with Ron, pretty much. My difference: do something. Anything.
> Guestimate what the report should be, do it quickly, then mark it
Well, "mark it done" might be pushing your luck.
Some customers take it very offensively to "mark things done"
if they are not done. But certainly, getting a report out
for someone to see will start the feedback loops. (Don't forget
to update your daily estimate to completion after some work
and feedback are produced :-)
> The donors/owners will soon start griping, and you can convertTrue.
> their gripes into requirements that go on the product backlog.