Re: [scrumdevelopment] Re: More newbie questions...
- On Saturday, August 2, 2003, at 08:26 PM, Ron Jeffries wrote:
> Isn't it the client's job to know what's important? If not, why is s/heYes. I have found though, with some of the companies and individuals I
> designated as the client?
> Of course we should all advice -- but why have a decision maker if not
> make decisions, bad or good?
have dealt with, that the individual in charge of promoting the
businesses perspective does not always full understand the business
perspective, or their point of view is based on a complete product
versus which elements of the product are more important than others -
in this circumstances, the administrative component versus the end-user
I also agree that our perspective is to advise, let them decide, and
ensure that the decision is noted in our log somewhere for the future.
> 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.