Abstract: It’s easy to think of a roadmap as a fixed and detailed plan virtually etched in stone. They are often artfully crafted and designed… bosses love them and developers hate them. They leave us the job of tediously making updates to match the things we failed to deliver and let us down more often than not. Often, they don’t focus on real user needs and outcomes. Traditional approaches to roadmaps aren’t flexible enough for the agile methods most teams use today. We need a different approach.
Management often still want them because:
- They want to be sure we’re working on the highest-value things first
- They are trying to run a business, which means they need to be able to plan.
- They need to make date-based commitments.
- They need to coordinate efforts and dependencies with other parts of the organization.
For alternative approaches to be accepted, it must address these needs.
In Agile, we talk about creating a shared understanding of product goals. We recognize the value in getting everyone on the same page. A good roadmap is not so much a project plan as a strategic communication tool, a statement of intent and direction. It should capture the user’s goals and outcomes.
In this talk, hear how Chris is helping organizations take a pragmatic approach to roadmapping. You’ll learn how to address management’s core needs without frustrating your product delivery teams.
Learning Outcomes: - * Learn how to capture and communicate the user's goals and desires (outcomes), not just features (outputs).
- * Learn how to use the Opportunity Solution Tree to reframe the delivery goals.
- * Learn that avoiding date-based commitments when possible will enable great flexibility and creativity with your delivery teams.
- * Learn that a roadmap and release are different and serve different needs within the organization
- * Learn that an effective roadmap minimally consists of a product vision, business objectives timeframes (not hard dates), and themes which might reference features and solutions.
Attachments:
