Senex Rex
  • Team
  • Blog
  • Resources
  • Contact

Forecast Horizon: Does Your Team Communicate?

Posted on February 4, 2014 by Dan Greening Posted in Metrics, Scrum

Good communication between product manager and team, between value appraisal and product development, leads to success. It helps you build the right thing at the right time. When the Product Owner and Development Team communicate well, the Product Owner can forecast feature delivery dates with a statistical likelihood. It promotes great architectures. The Development Team can build, but not over-build, a resilient architecture suitable for likely future needs.

I developed the Forecast Horizon metric to measure team communication. Forecast Horizon is the sum of work estimates from the top of the backlog through the first unestimated Product Backlog Item. Since many Product Owner put unestimated Backlog Items at the top of a Backlog, you may choose to skip unestimated backlog items that have been modified since the last Sprint Planning or Grooming meeting. Forecast Horizon can be expressed in team-time, by dividing by a recent average velocity and multiplying by sprint duration. In my work, I usually talk about Forecast Horizon in weeks.

A Forecast Horizon of zero is the worst. This means the topmost item in a team’s work backlog is unestimated. Why is this a problem?

  • The developers doing the work have not estimated the top-most item, so the Product Manager can’t responsibly forecast when the next item will be delivered.
  • The top-most Backlog Item has likely not been considered in forming the architecture.
  • The team never thinks at a bigger scale than the next dinky piece of work.

I realized that a zero-horizon backlog means Product Owners had to have made their own work estimates to responsibly order the backlog, and this dis-empowers the team. Watching team-after-team slog through Product Owners saying, “Surprise, here’s your next Sprint, let’s estimate it,” They might as well hire developer body-shops. There was no creativity left in engineering; and, honestly, how can you hold development teams accountable for estimates in these situations?

Yet, Forecast Horizon is zero for many teams, particularly those teams who advocate “no estimates.” To operate with no estimates in the Product Backlog, there are two possible approaches:

  1. Don’t estimate user stories until the Sprint approaches, then only estimate stories the team feels it can complete. This eliminates the ability of the Product Owner to make thoughtful, profit-driven tradeoffs in ordering the Product Backlog.
  2. Split and refactor all user stories until they are approximately the same size. You can then assign “1” to all the stories and measure the Forecast Horizon as I described. In practical terms, this allows for forecasting one or two Sprints forward. However, when attempting to forecast further into the future, you end up with so many stories that no one can thoughtfully assess market value, risks or architectural implications at the larger scale that long-term planning demands. In other words, you can’t see the forest for the trees.

Because of the forest-tree paradox, No Estimates advocates set up developers to be robot workers who serve the Product Owner. Big thinking developers—including architects and product innovators—become slaves to a endless, micromanaged backlog of little stuff. I think the Product Owner could get a lot more value from the team, by encouraging their long-term thinking to be big.

Left: Chunky items everywhere = bad. Center: Bite size items everywhere = bad. Right: bite-size items first, chunky items 2 sprints away = good

Make backlog item granularity increase with time

In my experience, Forecast Horizons of 2–6 months are associated with higher value creation and better architectures. This sounds daunting for many teams, because they have dysfunctional Sprint Planning and Grooming meetings, where estimation is stupefying and slow.

Estimation can be interesting and fast, if the Product Owner and ScrumMaster work together. For near-term backlog items, you can use bulk estimation to rapidly estimate lots of similar sized stories (see Bulk Estimation).  For long-term backlog items, just “go big.” Product Owners can work top-down to express their product goals from a 1-year vision, using story-splitting to first create multi-month Epics and then get acceptable Sprint Backlog Items. At each stage, including at the 1-year vision stage, I counsel Product Owners to get team estimates in “decimal Fibonacci” numbers (1, 2, 3, 5, 8, 10, 20, 30, 50, 80, 100, 200, etc.) from teams.

Forcing teams to estimate extremely large Backlog Items provides important value that few coaches or trainers appreciate:

  1. Teams engage very early in architectural discussions. Forcing a team to “estimate large” makes them consider architectural tradeoffs well before they are “baked in”, and discuss them with the Product Owner. Obviously, most architectural issues have impact on what the Product Owner might do in the future, so these discussions then create a virtuous cycle where the Product Owner can then explore market needs better to help guide the team’s architectural choices.
  2. The Product Owner can make significant, well-informed tradeoffs early, and then pursue deeper market or risk exploration with high-ranked Epics, using Lean Entrepreneurship methods or alternatives.
  3. The Product Owner can get estimates on alternative Product Backlog Items, which solve stakeholder problems in different ways, to make better decisions on a profitable solution.

The result is a fractally structured Product Backlog, with mostly small backlog items at the top, and larger Epics and Visions at the bottom. Is there an optimal number of PBIs in a Product Backlog for a project due at a particular time? You should be able to think about the implications of the whole thing, while being able to make tradeoffs in short and long time scales. Like other fractal structures, a fractal backlog grows by the log of the Forecast Horizon.

As an agile coach in large companies, I have found great value in measuring and increasing Forecast Horizon. Teams start operating better, address and eliminate dependencies much earlier, and innovate more deeply.

Can we help you improve your ability to forecast, make thoughtful product and architecture tradeoffs, or get your Product Owners and teams conversing on a deeper level? Contact us.

Share this:

  • Click to print (Opens in new window)
  • Click to share on Twitter (Opens in new window)
  • Click to share on Facebook (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • Click to share on Reddit (Opens in new window)
  • Click to email a link to a friend (Opens in new window)
  • More
  • Click to share on Tumblr (Opens in new window)
  • Click to share on Pinterest (Opens in new window)
  • Click to share on Pocket (Opens in new window)
« Four-part User Stories: Functionality that Matters
The Goal Revisited »

Leave a comment Cancel reply

You must be logged in to post a comment.

Continue with Facebook
Continue with LinkedIn

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Pages

  • 5 Points
  • Account
  • Agile Capitalization
  • Agile Capitalization Video: Greening and Rudd
  • Agile Training
  • Agility Language
  • Call for Papers: Agile/Lean at HICSS (Kauai, January 5-8, 2016)
  • Call for Papers: Agile/Lean at HICSS
    (due June 15, 2016)
  • Certified Enterprise Coaching
  • Clients
  • Contact Us
  • Courses: Agile Capitalization Workshop
  • Courses: Agile Development
  • Courses: Agile Product Management
  • Courses: Executive Introduction to Agile
  • Courses: Scrum@Scale Practitioner
  • Dan R. Greening
  • Enterprise Scrum: Scaling Scrum to the Executive Level
  • Glossary
  • Home
  • Jeff McKenna
  • John Horton
  • Kay Lynn Gabaldon
  • Login
  • Logout
  • Members
  • Password Reset
  • Premium Content
  • Premium Content 2
  • Privacy Policy
  • Register
  • Release Duration and Enterprise Agility
  • Resources
  • Rob Myers
  • Senex Rex Team
  • Short Course: Agile Manager
  • Sign up for Premium Content
  • Software Moneyball
  • Subscribe
  • The First of Five Challenges to Large Organizations that Force Agility
  • Troy Magennis
  • User
  • Vincent T. Mills
  • Senex Rex Blog Posts
  • Rapid Agile Forecasting

Archives

  • August 2018
  • February 2018
  • February 2017
  • March 2016
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • February 2015
  • August 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • April 2012
  • March 2012
  • December 2011
  • July 2011
  • March 2011
  • February 2011
  • September 2010
  • August 2010
  • May 2010
  • April 2010
  • March 2010
  • January 2010
  • May 2009
  • March 2009

Categories

  • Advocacy (11)
  • Agility (10)
    • Agile Base Patterns (7)
  • Calls for Papers (4)
  • Enterprise (23)
  • Events (5)
  • Job Search (1)
  • Marketing (2)
  • Metrics (12)
  • Personal (7)
  • Personal Improvement (2)
  • Portfolio Management (11)
  • Product Management (9)
  • Quality (6)
  • Scrum (31)
  • Software (4)
  • Training (2)
  • Uncategorized (5)

WordPress

  • Log in
  • WordPress

Subscribe

  • Entries (RSS)
  • Comments (RSS)

Pages

  • 5 Points
  • Account
  • Agile Capitalization
  • Agile Capitalization Video: Greening and Rudd
  • Agile Training
  • Agility Language
  • Call for Papers: Agile/Lean at HICSS (Kauai, January 5-8, 2016)
  • Call for Papers: Agile/Lean at HICSS
    (due June 15, 2016)
  • Certified Enterprise Coaching
  • Clients
  • Contact Us
  • Courses: Agile Capitalization Workshop
  • Courses: Agile Development
  • Courses: Agile Product Management
  • Courses: Executive Introduction to Agile
  • Courses: Scrum@Scale Practitioner
  • Dan R. Greening
  • Enterprise Scrum: Scaling Scrum to the Executive Level
  • Glossary
  • Home
  • Jeff McKenna
  • John Horton
  • Kay Lynn Gabaldon
  • Login
  • Logout
  • Members
  • Password Reset
  • Premium Content
  • Premium Content 2
  • Privacy Policy
  • Register
  • Release Duration and Enterprise Agility
  • Resources
  • Rob Myers
  • Senex Rex Team
  • Short Course: Agile Manager
  • Sign up for Premium Content
  • Software Moneyball
  • Subscribe
  • The First of Five Challenges to Large Organizations that Force Agility
  • Troy Magennis
  • User
  • Vincent T. Mills
  • Senex Rex Blog Posts
  • Rapid Agile Forecasting

Archives

  • August 2018
  • February 2018
  • February 2017
  • March 2016
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • February 2015
  • August 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • April 2012
  • March 2012
  • December 2011
  • July 2011
  • March 2011
  • February 2011
  • September 2010
  • August 2010
  • May 2010
  • April 2010
  • March 2010
  • January 2010
  • May 2009
  • March 2009

Categories

  • Advocacy (11)
  • Agility (10)
    • Agile Base Patterns (7)
  • Calls for Papers (4)
  • Enterprise (23)
  • Events (5)
  • Job Search (1)
  • Marketing (2)
  • Metrics (12)
  • Personal (7)
  • Personal Improvement (2)
  • Portfolio Management (11)
  • Product Management (9)
  • Quality (6)
  • Scrum (31)
  • Software (4)
  • Training (2)
  • Uncategorized (5)

WordPress

  • Log in
  • WordPress
Copyright ©2013-2015 Senex Rex LLC. All Rights Reserved.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
Do not sell my personal information.
Cookie SettingsAccept
Manage consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
SAVE & ACCEPT