R. Clayton (rclayton@clayton.cs.monmouth.edu)
(no date)
It seems to me that when we broke up the Stories 5, 6, 12, and 17 into tasks
last Thursday, We missed assigning/specifying a couple of important functions
that would unify the 4 Stories that were being implemented into a coherent
iteration.
True, there were lots of functions not specified in the task definitions, but
that's generally o.k. Task descriptions should be somewhere in detail between
stories and individual component descriptions. I chose to emphasize a task as
an individual component (function or class) descriptions to give people
something concrete to focus on for design and estimation.
Task descriptions should most likely be pitched towards an intermediate
functional decomposition, where "intermediate" means implementable by a
programming pair within the given iteration time. This helps focus the group
on the overall system design while leaving the design of the pieces up to the
implementors (it also helps avoid the "this bit needs to go there" arguments
that erupted last Thursday).
As for iteration coherence, that's my fault for starting over again. Tom
picked those stories with the expectation that they'd be added to the system as
it was at the end of project 2. We'll have to patch that up today with the
next set of stories.
This archive was generated by hypermail 2.0b3 on Thu Aug 02 2001 - 12:45:05 EDT