N
Normanator
I'm new to Microsoft Project, coming from an Agile/Scrum approach.
Project's mapping of Duration to Calendar time utterly and totally confuses
me.
Scrum teams estimate tasks in "ideal days" (work-units of ~8 totally
focused, uniterrupted, in-the-flow hours). However reality brings meetings,
e-mail, legacy issues, and other assaults on our optimism, so that our
"velocity" on task is < 8 hrs/day. E.g. if we practically achieve 4hrs/day
our 3 ideal-day task should take 6 calendar days. Nothing I try in Project
allows me to express this.
I tell Tools | Options | Calendar to use 4hr days, starts 8am, ends 12p.
I enter task "Carry Ring":Frodo:2d and expect it to run M-Th in the
calendar. Instead it starts and ends on M! Setting it to 16h yields M-Tu,
still not M-Th!
I enter task "Fight Balrog":Gandalf(50%):2d, again it starts and ends M! A
50% resource should mean it takes twice as long on the calendar as a 100%
resource! I would like it to show M-F+M-W ((2d / 0.5 vel) / 0.5 avail) =
8ed. But I guess I have to do that math myself.
But when I assign "Fight Balrog" to Frodo(100%), the calendar time doesn't
shrink!
What does availability, Fixed Work/Fixed Effort, etc. mean? How do I map it
to what I'm used to?
Scrum also expects velocity to get refined in flight. If I adjust velocity
from 0.5 to 0.75, then all pending tasks should shrink automatically: 3id was
6ed now becomes 4ed. How do I achieve this re-estimation?
Thanks.
Project's mapping of Duration to Calendar time utterly and totally confuses
me.
Scrum teams estimate tasks in "ideal days" (work-units of ~8 totally
focused, uniterrupted, in-the-flow hours). However reality brings meetings,
e-mail, legacy issues, and other assaults on our optimism, so that our
"velocity" on task is < 8 hrs/day. E.g. if we practically achieve 4hrs/day
our 3 ideal-day task should take 6 calendar days. Nothing I try in Project
allows me to express this.
I tell Tools | Options | Calendar to use 4hr days, starts 8am, ends 12p.
I enter task "Carry Ring":Frodo:2d and expect it to run M-Th in the
calendar. Instead it starts and ends on M! Setting it to 16h yields M-Tu,
still not M-Th!
I enter task "Fight Balrog":Gandalf(50%):2d, again it starts and ends M! A
50% resource should mean it takes twice as long on the calendar as a 100%
resource! I would like it to show M-F+M-W ((2d / 0.5 vel) / 0.5 avail) =
8ed. But I guess I have to do that math myself.
But when I assign "Fight Balrog" to Frodo(100%), the calendar time doesn't
shrink!
What does availability, Fixed Work/Fixed Effort, etc. mean? How do I map it
to what I'm used to?
Scrum also expects velocity to get refined in flight. If I adjust velocity
from 0.5 to 0.75, then all pending tasks should shrink automatically: 3id was
6ed now becomes 4ed. How do I achieve this re-estimation?
Thanks.