Timeline for What metrics to keep through out the life of the project?
Current License: CC BY-SA 2.5
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 23, 2011 at 13:03 | vote | accept | Geo | ||
| Feb 12, 2011 at 13:11 | comment | added | Pawel Brodzinski | Assume I have 20 tasks and I plan that team completes a single task every 4 days (that's the case from my last Kanban team). After 40 days the team should have completed 7-8 tasks. I can compare number of completed tasks with that and learn how screwed we are ;) Of course this is huge oversimplification but you see the pattern. | |
| Feb 11, 2011 at 22:38 | comment | added | Geo | Thanks for this response. I use a 50/100 model for all tasks in the project plan. If the person started the task is 50% done, if is completed is 100, this keeps it simple and consistent across all my projects. I will like to understand more how you accomplish the first part of your plan. Where you said "know how are you going against the plan" | |
| Feb 11, 2011 at 7:16 | history | answered | Pawel Brodzinski | CC BY-SA 2.5 |