Skip to main content

A Burndown chart that radiates progress

Here is a visual example of a team learning the value of a Scrum Sprint Burndown chart.  To give some context to the images below - the team did a 3 day workshop on Scrum between sprint 1 & sprint 2.  In this workshop we laid down some working agreements, one of which was they would use a physical Scrum task board with several major items.  One item was the burndown chart derived from task hours estimated remaining each day.  This team knew they were under committed for the sprint but wished to get started sprinting (a good choice rather than spend more time in sprint planning with so much uncertainty).  They felt they could get to working on about 5 high priority stories and plan to replan (pull into the sprint more stories) later in the week.  They assumed that learning about the uncertainty was better than crystal ball gazing.

The team started with 64 units (estimated task hours) of work.  On the fourth day they decided to bring in more stories with estimated 24 units of work.  Then on the fifth day they agreed to pull in an additional 34 units of work.  This is their original burndown for the sprint.



 What does this burndown tell us?  It tells us that the team is not going to finish the sprint.  It is only when one stops to read the fine print (the annotations) that one may gleam that there is more to the picture than is being visualized.  Asking the team what they could do to make this chart "tell the whole truth", they decided to redraw the burndown.



Now this 2nd generation chart is telling a more complete story.  It shows that on day four the team recognized it was finishing the committed work very early (as assumed - and then proven by tracking).  So they pulled in some work on that day from the prioritized backlog.  They were dealing with stories that had dependencies (not quite at the INVEST model standard - yet).  But by doing work on the dependent stories the understanding of the team was growing.  They pulled in 24 units of work (drawn below the zero datum on day 4).  The very next day the team was in a similar position and pulled in an additional 34 units of work (units were derived from task estimates - not story points).  The additional 34 units are drawn below the 24 datum line (at -58).

Will we get to DONE?

On day 8 the very quick progress slowed.  This was not evident in the low fidelity charts and some team members were debating about the proper location of the top of day 8s bar on the graph.  The solution to this "impediment" is to use graph paper.  This allows for a more precise view and projection.  Projecting the trend is the purpose of the burndown chart.  We want to answer the question:  Will we get to DONE?


At sprint 2 - I am much less concerned with the team getting all the work pulled in to the sprint Done, and much more concerned that they learn to use the tools and techniques that allow them to become self-managing.  Next sprint they will have a better idea of the amount of work they can accomplish in a sprint (velocity).  And if they have taken time to groom their backlog this sprint, next sprint's planning meeting will go much more smoothly.  They may be able to fully plan the sprint and not need to pull in stories ad-hoc.

It is all part of learning to use the Scrum tools and techniques.  Learning is exciting!

See Also:  We have the best tools - why do we not use them?
Post a Comment

Most Popular on Agile Complexification Inverter

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…

Innovation in the Automobile Industry

In the 1900s the automobile industry was the most important and innovation industry in the USA.  But one could question if this was good for our society in the long run.  And one could question if they actually innovated.

In the early 1900s there were few automobiles, very little infrastructure created to support the industry.  For example the road system was still designed for horse drawn wagons and the wagon wheel (remember a steal rim and wooden compression spoke wheel).  The future US Highways, or the 1950s Interstate Highway System at the cost of $425 billion were decades and many innovations away. There was no gas service station, there were however horse stables, farriers, and blacksmiths in each town along the roads.  There was no real "road map", there was no road naming system, like was created in 1926 - the United States Numbered Highway System.

The industry employees millions of people, and was a large factor in the economy of the USA.  It created or was created b…

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

Timeline of Social Networks -or- the Long Haul

I was listening to KERA's Think and they mentioned the concept of social networks.  It got me think...

But the book Long Haul, is its own interesting story - A Million Miles and Counting - A Trucker's Tale.

“The Long Haul: A Trucker’s Tales of Life on the Road”
Did you know 41 million people move in the US a year?  Having moved a few times in my life, sometime with the Bed-Bugger's help, this book is a great insight into that life.
Author: Finn Murphy's CB handle - "U-Turn" The radio interview noted the concept of social networks in the 21st century.  What is a highway - but a manifestation of a social network - a trail across the land.

a timeline using the Knight Lab Timeline JS tool kit.

See Also:

Social Media - Tracking its Exponential Growth video
Social media has overtaken porn as the #1 activity on the Web
List of social networking websites - Wikipedia

The World's 21 Most Important Social Media Sites and Apps in 2015



The Growth of Social Media - infog…

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…