UNITED WAY STL ACADEMY
  • Courses
  • Log In
  • Join Free
  • Home
  • Courses
  • Scrum Essentials

Scrum Product Development

Curriculum

  • 5 Sections
  • 25 Lessons
  • Lifetime
Expand all sectionsCollapse all sections
  • Planning Your Work
    4
    • 1.1
      The Product Roadmap
      10 mins
    • 1.2
      Breaking Down Requirements
      10 mins
    • 1.3
      Your Product Backlog
      10 mins
    • 1.4
      Product Backlog Common Practices
      10 mins
  • The Talent and the Timing
    4
    • 2.1
      The Developers
      10 mins
    • 2.2
      Getting the Edge on Backlog Estimation
      10 mins
    • 2.3
      Your Definition of Done
      10 mins
    • 2.4
      Common Practices for Estimating
      10 mins
  • Release and Sprint Planning
    5
    • 3.1
      Lean Startup
      10 mins
    • 3.2
      Release Plan Basics
      10 mins
    • 3.3
      Sprinting to Your Goals
      10 mins
    • 3.4
      Planning Your Sprints
      10 mins
    • 3.5
      Your Sprint Backlog
      10 mins
  • Getting the Most Out of Sprints
    4
    • 4.1
      The Daily Scrum
      10 mins
    • 4.2
      Team Task Board
      10 mins
    • 4.3
      The Sprint Review
      10 mins
    • 4.4
      The Sprint Retrospective
      10 mins
  • Inspect and Adapt: How to Correct Your Course
    8
    • 5.1
      Need for Certainty
      10 mins
    • 5.2
      The Feedback Loop
      10 mins
    • 5.3
      Transparency
      10 mins
    • 5.4
      Antipatterns
      10 mins
    • 5.5
      External Forces
      10 mins
    • 5.6
      In-Flight Course Correction
      10 mins
    • 5.7
      Testing in the Feedback Loop
      10 mins
    • 5.8
      Culture of Innovation
      10 mins

The Product Roadmap

Scrum Product Development

The Product Roadmap

🕐 12 min read
The Big Question

How can a well-crafted product roadmap align your team and stakeholders to achieve lasting value?

Before you set off on any ambitious journey—whether it’s launching a new product or exploring uncharted territory—you need to know where you’re headed and how you’ll get there. In product development, this guiding path is called the product roadmap.

💡 Did You Know?

Even though the product roadmap isn’t required by Scrum, most successful Scrum teams use one to increase transparency and unity of purpose.

In the seven roadmap to value elements, you begin with the end in mind by creating your product goal. The next step is creating a map to help you achieve that goal.

Schematic illustration of the product roadmap in the roadmap to value.
The product roadmap visualizes the journey from goal-setting to value delivery for your team.

Although the product roadmap is not a formal aspect of Scrum, it is commonly used by Scrum teams.

Why do you think teams and stakeholders find it helpful to visualize the journey to their product goal?

Product (Scrum definition)

A vehicle to deliver value with a clear boundary, known stakeholders, and well-defined users or customers. This could be a service, physical product, or something more abstract.

The word product is meant to describe a much broader spectrum of value than simply software, hardware, or physical products. It’s also broader than a project as it is long-term.

Imagine setting sail on a voyage with a crew and passengers. Would you cast off without knowing your destination or route? Of course not! The same logic applies to building products: a roadmap outlines the journey, aligning everyone before the journey begins.

  1. Decide where you want to go (define the product goal).
  2. Figure out how to get there (visualize the product roadmap).
  3. Socialize the goal (communicate the plan).

“Socializing” the product roadmap means sharing it widely with all influencers and stakeholders to build understanding and commitment to the direction and path.

The product roadmap can change, but it gives you something tangible to start with, thereby increasing effectiveness. By socializing the roadmap as an artifact of planning or replanning, you can make sure that influencers and stakeholders understand the direction and path. Adjustments to the plan are less costly, and a shared vision contributes to team unification.

Key Takeaway

A product roadmap provides a high-level, dynamic guide that aligns teams and stakeholders around a shared vision and evolving plan for delivering value.

Take the Long View

The product roadmap is a holistic, high-level view of the features or capabilities necessary to achieve the product goal. Natural affinities are established (“If we do this, we should logically do that”), and gaps are made readily visible (“Hey, where is …?”).

Product Backlog

The evolving, prioritized list of features, epics, and user stories that make up all the work to realize the product goal.

The product roadmap is the initial product backlog—your master to-do list. As the likelihood of product backlog items being developed increases, items are increasingly broken down (progressive elaboration). The product backlog expands to include items that are:

  • Small (imminently realized; often referred to as user stories)
  • Midsize (midrange realized; often referred to as epics)
  • Conceptual (clear but lacking details; often referred to as features)
Tip icon
TIP

See the sidebar, “Roadmap and Backlog Terminology,” later in this module for more information about features, epics, and user stories.

Remember icon
REMEMBER

The product roadmap isn’t fixed in stone and fully paved; it’s a living, dynamic artifact. Review and update your roadmap regularly to keep pace with reality.

Although the product owner fully owns the goal, the entire Scrum team needs to be part of the roadmap-building process. Developers are the technical experts who will be doing the work and must provide constraints and effort estimates. If the developers haven’t been chosen yet, include the functional managers after you create the initial product roadmap to help identify the necessary skills.

When working with clients, teams often create both the product goal and product roadmap on day one—so development can begin as soon as day two. This accelerates alignment and delivery.

How might involving the entire Scrum team in creating the roadmap impact the project’s success?

Use Simple Tools

When creating your product roadmap, use the simplest tools possible. Sticky notes and a whiteboard—physical or digital—work wonders, even for distributed teams. Each product feature or capability fits onto a sticky note.

Human brains weren’t created in the digital age. Studies have proved that electronics have a dulling effect. In fact, it takes less brain-wave function to watch TV than to watch paint dry. Yet, using a simple system like sticky notes is physically and mentally engaging, and using it fosters an environment of change and creativity.

Teams we’ve worked with have built product roadmaps for large-scale products in just a few hours, starting with the highest-priority items and moving stickies around as the roadmap takes shape.

Want to go deeper? The science behind sticky-note collaboration

Research shows that tactile and visual methods like sticky notes increase engagement, creative thinking, and group problem solving. When people physically move notes, they’re more likely to spot connections and gaps than when using digital-only tools.

⏱ 5 minutes
Activity: Start Your Own Roadmap

Gather your team (physically or virtually) and try building a simple product roadmap together.

  1. Choose one product or service you want to plan.
  2. Write one requirement or feature per sticky note (physical or digital).
  3. Arrange stickies on a whiteboard into logical groups or sequences.
  4. Discuss and adjust until your roadmap tells a coherent story from goal to value.

What did you notice about team dynamics when using sticky notes for the roadmap? Did it change the energy or participation compared to digital tools?

Create Your Product Roadmap

You can use seven easy, common-sense steps to build your product roadmap. Perform these steps on day one as part of your product planning; they should take no longer than a few hours. For smaller efforts, you’ll get the job done over morning coffee. The product owner completes the steps with the rest of the product team (the entire Scrum team and the stakeholders).

Using sticky notes, several colors of flags, and a whiteboard, follow these steps to build your product roadmap:

  1. Write down one product requirement per sticky note.

    Think of as many product requirements as you can.

    Technical stuff icon
    TECHNICAL STUFF

    You’ll know you’re on the right track if you can read each sticky note as a completion of the sentence, “My customer can …<sticky note text>.” For example, “My customer can now <Adjust the Temperature>” makes more sense than “Design the Temperature Touchscreen.” Product roadmaps lay out the requirement journey to value, not the tasks. Tasks come later in sprint planning.

  2. If appropriate and synergistic, arrange some requirements in related categories or groups.

The product roadmap isn’t fixed in stone and fully paved; it’s a living, dynamic artifact.

Flashcard

What is a product roadmap in Scrum?

Tap to reveal
Answer

A high-level, dynamic artifact that visualizes the plan for delivering the product goal and aligns teams and stakeholders.

Flashcard

What does “progressive elaboration” mean in the context of the product backlog?

Tap to reveal
Answer

It means breaking down larger items into smaller, more detailed pieces as their likelihood of development increases.

Flashcard

Why is socializing the product roadmap important?

Tap to reveal
Answer

It builds shared understanding and buy-in among stakeholders, making adjustments less costly and increasing team unity.

Think about a time when you worked on a project (in any context) without a clear roadmap. How did that affect your team’s alignment, progress, or results? What could a roadmap have changed?

0 words Take your time — depth matters more than length
  • Identified the main purposes of a product roadmap in Scrum
  • Explored tools and techniques for collaborative roadmap creation
  • Reflected on the value of team involvement and communication
❌ Common Misconception

A product roadmap should remain unchanged once it’s created.

✅ The Reality

The product roadmap is a living artifact that should be reviewed and updated regularly to reflect evolving goals and realities.

+50 XP

What is the main benefit of socializing the product roadmap with stakeholders?

Review the “Take the Long View” section above to find the answer.
Key Takeaway

A simple, collaborative, and living roadmap empowers teams to adapt, innovate, and deliver value effectively.

How might you adapt the roadmap process for a team that is fully remote or distributed across time zones?

0 words
SHIFT

The Shift

  • A product roadmap is not a static document, but a living guide that aligns and energizes teams to pursue shared goals.
  • Simple, collaborative tools (like sticky notes and whiteboards) can make roadmap building more effective and engaging.
  • Socializing and regularly updating the roadmap ensures continued buy-in, adaptability, and clarity for all stakeholders.
End of lesson Ready for the next lesson?
Continue to next lesson  →

Leave a Reply Cancel reply

Breaking Down Requirements
Next

© 2026 United Way STL Academy | Powered by Sejal Learning Systems.

Modal title

Main Content