Enforcing Story Points/Tasks and Estimates - Micromanaging or let the tool do it?
All,
We are starting Release 2 of an "agile-like" project using the scrum template. I am seeing: Stories with no tasks Stories with no points Tasks with no estimates How are you all pushing your team to put these in? Are you micromanaging your workers, or are you putting in precondition statements to solve this? Should it be a story can't start without points? Should it be a story can't start without tasks? Should it be a task cannot start without estimates? Is there a preconfig that makes sure that a story has tasks? thanks |
One answer
Ralph Schoon (63.6k●3●36●47)
| answered Feb 13 '15, 5:44 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Mahari,
there are no built in preconditions for the cases you mention. You would have to create them, which would be not too complex. I think it is up to the organization, how heavy you want to get on the process. E.g. if you want to enforce tasks. Some teams might decide not to require a task for a small story. One thing that I have seen people do is using dashboards to show inconsistent data (e.g. stories started with no story points). The plans show some information e.g. tasks with no estimation are shown as low quality in the load bars. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.