Skip to main content

PEZ -or- Why one shouldn't track Scrum Tasks in Hours

I've been called to task - asked why I teach teams to distinguish between Task Hours and some non-denominational non-specific non-absolute unit.  The latest team I guided used PEZ!  As in the daily stand up a person might be heard to say:
"Yesterday I was working on the code to DisCombobulate the GUID so that we could distinguish customers from guest and the task to peek into the hashed session state was harder than I anticipated - I will need 2 more PEZ to get that done today."

Benefits of "Task Points"

Because it works and is more fun.  Not a sufficient and rational reason.

Because it's a fractal of the concept of Story Points.  Not a practical enough reason.

Because it encourages transparency and acknowledges that we are really bad at estimates.  Not sure we wish to propagate that notion.

Because Scrum has a value of Openness and in that sprit - can we admit that a team of 7 people doing 50 "hours" of tasks a week is really a poor metric.   Is the metric - wrong - or is it being perceived poorly - or do we just not know what we have measured?


Have we truly measured the sprint progress in the units of HOURS? You know that aggregate of 60 minutes.  That man-made concept of time.  That universal unit that all societies agree upon, even the Imperial Unit based USA.

Burndown in Hours
Burndown in PEZ
Let's take a look at a team's burndown, using traditional hours.  It shows that in the first week of the sprint they accomplished 50 hours of work.  But there is 7 people working for the week.  Generally speaking that's 7 X 40 hr/week = 280 hrs.  Now many people like to point out that there is not 8 hrs of work in a typical work day.  Many people believe that every day contains a few hours of non-productive hours.  Many believe there are 6 hrs of productive time in a typical day (7 X (6hr X 5days) = 210 hrs).  What can we deduce from our burndown?  Maybe what we've been estimating and burning down are not this well know unit of time called an hour.

We have been estimating in hours - so it must be hours.  This is a myth. The analysis at RescueTime have show this myth to be busted by looking at the habits of user of their tracking tools. Their tools calculate a productivity rating in additions to hours on tasks.  To spoil the read... "And with an average productivity pulse of 53% for the year, that means we only have 12.5 hours a week to do productive work."






So maybe that study puts an end to the concept of Ideal Engineering Hours.  I've been involved in these dialogues and the general consensus is 5 - 6 ideal engineering hours per day.  It does not quite jive with what a real study finds (12.5 / 5 approx. 2 - 3 hr/day).

If a team of 7 should be doing something like 200 hrs of productive work a week - then what do we think of a team of 7 only completing 50 hrs in a week?  Well is that rational?  No.  So what's wrong with this irrational logic?  One could blame the individuals on the team and try to improve their ability to estimate tasks.  Yet if they are off by a factor of 4 - how much work will go into improving their poor estimation technique?  And what about this empirical measurement technique?  If we believe in the empirical technique then does the accuracy of our estimates matter?

My belief in transparency (openness) has me concerned that if we hang a chart on the wall that professes that the team completes 50 hours in a week - that someone is not telling the truth.  It is obvious if one observes the team, as a Team Agility Guide, might do and see that the team members are working on the sprint stories for the greatest part of every day and working diligently then these units might just be the problem.  When the estimate is made in good faith, but doesn't equate to what the wall clock tells.  Something is telling a fib, a lie.  Let's quit lying and make our burndown truthful.

One technique is to realize the empirical measurement does not require hours to work, choose any unit you wish - try PEZ.  And then one can correlate the PEZ to work hours.  And stop talking about hours that require half a day of work to complete.


Mike Cohn's critique of "Task Points"

I've read and reread Mike's critique and advice, but I don't get his point.  He finds tremendous value in Story Points, and notes that Task Points have similar disadvantages:
  • A foreign concept to many team members
  • The need to establish baseline values against which relative estimating can begin
  • A concern that estimates drift over time in comparison to the original relative values
I will share my observation - that the many teams that already understand relative points concepts and why they are beneficial do not have a new or foreign concept to learn.  No baseline values are required to begin.  Just simply change the unit one labels the task estimate from "hour" to "PEZ"; there no baseline mombojumbo.  I'm to ignorant to understand the 3rd disadvantage; seems to me this is possibly a great thing, a result of people learning.

Perceived Benefits of Task points

How does having a team track remaining effort on work (story or task) benefit the deliver of value? Great question. Will a list of reasons do?

  1. It moves the focus from how much effort - to how much effort is remaining - imagine the sunk cost fallacy;
  2. when an item takes longer that your typical inspection cadence (sprint for a story; day for a task) it requires a explicit reestimation and recommitment to the item getting to done;
  3. when the list of estimates on an item grows long (say past 2 or 3) it is a wonderful indicator of an impediment / when a task (should be much less than a day) last in-process for a week it is a great indicator that help is needed - training a team to hold members accountable is easier with a visual signal
  4. when the item is done-but... and a person wants to mark a zero, but ... it's a great indication of a newly discovered task
  5. I suppose the metric (burndown) is more accurate to reality than an ALL or Nothing assessment of tasks/stories effort.
  6. the practice reinforces the inspect/adapt micro cycle; and someone once told me - if it's hard to do; do it more frequently.
  7. ... there may be others ...


Is it useful to track remaining effort at a task level? Yes and No; it's situational. 

Let's first define the No situation, when the team is performant, gets stories done easily, has a known velocity, no problem planning and achieving a sprint commitment.

Now the alternative situation... is it useful... I think so.


See Also:

Don’t Estimate the Sprint Backlog Using Task Points by Mike Cohn
Post a Comment

Most Popular on Agile Complexification Inverter

Where is Shakespeare When We Need Him?

We are desperately searching for a term for people that connotes the best of human kind.  The creative, sensing, combinatorial synergistic, empathic solutioning persons that have yet to been labeled with a role name that works.

Some of the old terms:
Staff, Workforce, Human Resource, My Team, Army, Company

Shakespeare created 1700 words in his time.  He mutated verbs to nouns, and vice-a-versa, transformed verbs into adjectives, and formed words from whole cloth never before heard.  This skill is rare, but there is a poet that can create the term we need in the twenty-first century.

What should this term define?

21st Century Human Resource; the generalizing specialist.

Yes, but what more?  What less?

Suggest your poetry in the comments, let us see if we cannot do 1/1700 as well as The Bard.

By-the-way; who create the phrase "coin a word"?



A TED Play List - How do you create new words
6:52
Erin McKeanGo ahead, make up new words! In this fun, short talk from TEDYouth, lexicographer Er…

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

Situational Leadership II Model & Theory

Have you ever been in a situation where you thought the technique needed to move forward was one thing, yet the person leading (your leader) assumed something else was what was needed?  Did you feel misaligned, unheard, marginalized?  Would you believe that 54% of all leaders only use ONE style of leadership - regardless of the situation?  Does that one style of leading work well for the many levels of development we see on a team?

Perhaps your team should investigate one of the most widely used leadership models in the world ("used to train over 5 million managers in the world’s most respected organizations").  And it's not just for the leaders.  The training is most effective when everyone receives the training and uses the model.  The use of a ubiquitous language on your team is a collaboration accelerator.  When everyone is using the same mental model, speaking the same vernacular hours of frustration and discussion may be curtailed, and alignment achieved, outcomes …

One Dark and Stormy during a Hurricane

I'm from the Carolina's where legend has it that our family commonly just hunkered down in the home on the coast and waterways than to head for inland shelter. Now that's from the old school days of barely improved (read paved) roads. They counted a storms severity by how high on the back porch steps (about 15 - top to ground) the water reached.  I don't recommend this action in todays world of long range forecast and transportation options.

I do recommend a drink or two in a hotel bar, far far away.

This is the week that Harvey came ashore in Texas.  I live on a hill in the little old town of Grapevine outside Dallas and Fort Worth.  And thank you all for letting me know that a storm is coming... I didn't get out and walk Malibu before the rain hit, so I grabbed a hat and we went anyway.  Much nicer walk with the drizzle, I'd say.

I'll raise a glass to you - if you were not smart enough to do the responsible thing, at the last responsible moment.

I do re…

Software Development terms applied to Home Construction

Let's Invert the typically wrong headed view of Software Development project management as a construction project.  We can map it the other way just to see if it works... to have some fun, to explore the meaning of phrases we toss around quite frequently.


Normally Project Management terms come from a construction domain.  We are going to apply the lexicon of modern software to the construction of a home.  We will follow the construction project and meet some of the people doing the work.

This is a very small (8 homes from $600,000 skyward) program in my 30-40 year old neighborhood.

About 6 months ago I saw the programs landing page go up.  It gives casual observers and some of the stakeholders a general idea of the intent of the program.  And most importantly who to contact for additional information if you happen to be interested in their products.

The Refuge program has 8 product projects and has them running independently.  Yet much of their DevOps infrastructure has already b…