Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How to Improve Your Portfolio Planning and Forecasting Process

86 views

Published on

Are you struggling with long term planning for your agile teams? Is it getting to the point where tensions exists between Leadership (who are asking for firm commitments on delivery dates) and the teams (claiming that “this is not how agile works”)?

Clearly, a good balance is required: A balance between the flexibility in scope and delivery schedule that we need to afford our development teams to maintain their agility and the expectation of the business to receive reasonably accurate forecast of the awaited business capabilities.

It is therefore important for delivery teams to demonstrate continuous improvement in their ability to forecast the delivery of business capabilities within a reasonable level of accuracy without forcing them into unnatural practices

In this webinar, you'll:
*Learn how normalized story points can help support improving long term planning at all levels of the organization.
*Explore the trade-offs of different approaches and address the perception that this approach violates some tried-and-true practices, such as not comparing points across teams.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

How to Improve Your Portfolio Planning and Forecasting Process

  1. 1. OUR SPEAKERS • • • • •
  2. 2. OUR SPEAKERS • • • •
  3. 3. THE CHALLENGE • • • • Daily plan Multi-year vision, milestones, events, and Epics Short-term (3-4 PI) estimate of Features and Milestones Epic Epic Epic Epic Epic Epic Epic Epic Epic Epic Epic Epic Epic Epic EpicEpic Q1 Q3Q2 Q4 H1 H2 Y3 Y4 Feature Enabler Committed Features and Enabler for current PI
  4. 4. NORMALIZED STORY POINTS Sprint Ready Stories To Team EPIC EPIC EPICPortfolio Backlog CAPABILITY CAPABILITYCAPABILITYLarge Solution Backlog FEATURE FEATUREFEATUREProgram Backlog Team Backlog STORY STORYSTORY 815 5 3 1 21 3 5 1 2 ... X 30X 50 X 10 X 200X 100 X 300 X 1000 X 2000X 5000 ½ day to code and ½ day to test = 1 ”normalized” pointNormalized Points + Stable Velocities = Ability to forecast
  5. 5. BUILDING THE ROADMAP 4600
  6. 6. LET’S DIG DEEPER Obey speed limits Ultrasonic sensorsForward collision Make turnsFollow route Stay in lane Avoid obstacles Validate GPS Forward radar Cameras Self-park Perform Delivery Spike Perform delivery tests Navigate intersection Navigation Traffic indicators Collision/vehicle control
  7. 7. ALTERNATE APPROACH: A CASE STUDY
  8. 8. CASE STUDY: CONTEXT • • • • • EXTEND TO THE PORTFOLIO
  9. 9. CASE STUDY: SET THE ESTIMATION BASELINE
  10. 10. CASE STUDY: ROADMAP COLLABORATION
  11. 11. TAKEAWAYS • • • • • •
  12. 12. KEEP THE CONVERSATION GOING… • • • • • • • • • • •

×