According to Mike Cohn in his book, Agile Estimating and Planning, Ideal Time is "...the amount of time that something takes when stripped of all peripheral activities," and Elapsed Time is "...the amount of time that passes on a clock..."
Is there a more simple way to explain this?
How have YOU explained it (or similar concepts such as Effort and Duration) to stakeholders and project team members?
What has their response been? Saving Changes...
Paul ParkerScrumMaster (CSM)| PricewaterhouseCoopers (formally BearingPoint)Tampa, Fl, United States
Aaron,
This is one area that I try to avoid. Instead of looking at Ideal Time and Duration look at it from a capacity view.
When I go over estimates I explain to the client that the average fulltime project team member is productive about 6 hours on the project each day. I explain that admin, training, email, etc. that is not directly tied to project task take up the remainder of the day. So in a given week each team member is allocated for 30 hours and for the sprint 120 hours. So if a task is 12 hours it will take 2 days (given that we determined that each member works 6 hours a day on the project.)
Saving Changes...
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons."
Community Champion
