​​

Gear Stream

  • The Big Pivot
  • Our Approach to
    Transformation
  • Our Book
    SURGE
  • SurgeMaker
    Platform
  • Executive Briefs On
    Agility & Digital Innovation
BLOG COMPANY CONTACT
MEMBER LOGIN
Home / Agile Product Management / More on Responsibility Two: Roadmaps and release planning

More on Responsibility Two: Roadmaps and release planning

By Brad Murphy

Posted in Agile Product Management Tagged as Agile, release planning, roadmap

In my last post, I talked about the elements of an Agile roadmap. Agile roadmaps are never conclusively finished. They change according to regular review by the core team, in addition to the product manager. This flexibility means that every team member for each core function can be held accountable and responsible for helping to keep the map updated. Agile teams anticipate and are prepared for their roadmaps to change. Roadmaps are a reference guide for any decisions about release planning, backlog, and outbound marketing efforts. They provide a visual breakdown of product strategy and maintain focus. As such, they are an essential addition to any executive wall or conference room.

When the most appropriate release window has been set and the overall plan has been given the go-ahead by all stakeholders, teams can start release planning. Release planning takes place over a concentrated two- to three- day collaborative working session among the entire team, the end result being more accurate estimates as to the amount of effort needed to tackle the whole backlog of work for a given release. This can seem difficult as the team has to highlight high-level goals, features, and the value proposition for a release and then break down these requirements into use cases and features, with the eventual aim of producing user stories that a development team can realistically estimate. Agile teams rapidly adjust to this specialized means of accurate release planning.

During the release cycle, the roadmap will be adjusted and updated according to a variety of different factors. Should overall company strategy or development status change, based on voice-of-the-customer programs or information from other sources, these changes can be integrated into the roadmap. This makes the roadmap a handy measure of the non-stop planning in an Agile development environment, able to take on new information from all quarters (top-down, bottom-up, or even outside-in) and adjust accordingly.

Search

Recent Blog Posts

  • Why OKRs – And Why Now?
  • Why Google is an Epic Digital Company (and why you want to be just like them)
  • When Agile becomes (Fr)Agile, or Why You Need to Think of Agile Like Pants
  • Stop Trying to Check the ‘Agile’ Box
  • How to become invaluable to your organization

Categories

  • Agile Industry Trends
  • Agile Management
  • Agile Product Management
  • Agile UX
  • Corporate Culture
  • Gear Stream News
  • Implementing Agile & Scrum
  • Uncategorized

Post Tags

Agile agility Build Management business executive business management capabilities cloud cloud factory cloudsourcing collaboration command and control communication culture customers DevOps disciplines ecosystem enterprise innovation IT Kanban Lean Lean IT management market requirements measurement micro management networks Nokia ona organization organizational outsource outsourcing product release planning Risk roadmap scope Scrum software stakeholders statistics surge Transformation
The Big Pivot - Surge - The Surge App Platform - Surge Services - Research Notes Agility & Innovation

© Copyright 2009-2023 Gear Stream, Inc. All Rights Reserved.

Twitter/Facebook/Linkedin/Google+/RSS