Re: SCRUM & Change / Defect Management
- Agreed. For many of us, time reporting is mandated - usually not for
the functioning of the team itself, but for management.
I'm of two minds as to whether it's a bad thing to record time spent
and time remaining in the same tool...
In Scrum, I work hard to convince developers that I REALLY REALLY
mean it, when I say "upate your estimates to reflect *real* time
remaining". They have trouble believing that I DO want them to
increase estimates when needed. One thing I'm always saying (to get
them to lose the old habit of under-estimating) is "I don't care
about your actuals". I never come back to them about actuals, and
eventually they believe me...
If I ask them to put "time spent" into the same tool as "time
remaining", it /looks/ like I might be tracking their actuals vs
estimates... will this make them hedge on the "time remaining"
And on the other hand, it's more convenient than having to open 2
--- In email@example.com, "Mike Beedle" <beedlem@e...>
> Sometimes keeping actuals is not a "choice", is a mandatory:
- Tuesday, May 04, 2004, 10:54:17 AM, Mike Beedle wrote:
> Sometimes keeping actuals is not a "choice", is a mandatory:Of course, you're right, sometimes actuals are necessary.
I think the point that Tom is making is that it makes more
sense to most developers (myself, anyway) to estimate a new
Estimated Time to Completion than to update ETC by attempting
to re-estimate the total task.
- --- In firstname.lastname@example.org, Steve Bate <steve@x> wrote:
> Joe and Brad,Steve,
> Eventually I'd like to extend XPlanner so that the planning and
> tracking can be configured to handle a wide range of XP process
> variants. This (and a Scrum-specific web skin) should also make
> it an even better fit for Scrum teams.
I've appreciated your interacting on this.
I see now, why you might want to track the
original estimate for planning purposes at
the next sprint meeting.
It turns out that it won't matter for me
for a while. My head IT guy doens't want to
install Apache on any of our servers.
I'm not sure what that's about, and he has
somewhat avoided the question. But I don't
want to irk him over such a small thing.
So look like we'll go a different direction.
We've got Deb's spreadsheet and I think that
will do us for a while anyway.
BTW, while I'm wrapping up this subject,
isn't there a way to provide a compiled version
of the app for common OSs for those who don't
want to set up a develpment environment to
recompile it? Might widen your market a bit.
Lastly, your required list only shows Ant,
but my understanding is that Ant requires Apache.
If so, you might want to list that up front
as a requirement. My IT people were a bit
put out after getting all the pieces on the
(IIS) web server to find that it needed
apache. They wished they had known that up front.