​​

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 / Creating a Good MRD/BRD

Creating a Good MRD/BRD

By Brad Murphy

Posted in Agile Product Management Tagged as Agile, communication, market requirements, scope

This post is a part of a series discussing Agile Product Management responsibilities. Click here to start from the beginning.

My prior post talked about the barriers to creating a good MRD/BRD; now I want to get into how to actually create one. There are three principles that guide an Agile product manager’s description of a market, its requirements, and various solutions:

  1. Setting out information in terms of the time horizon it influences in as clear and comprehensive a manner as possible suited precisely to the audience meant to consume it;
  2. Observing and including information at the level of detail needed to effect change and take action and working with other sources when information more detailed than currently available is required;
  3. Managing and recognizing the difference between handling more and less stable information (keeping market requirements and detailed feature specifications in step).

Think of how these concepts overlap in the diagram above. Higher levels are directed towards larger issues, whereas lower levels correspond and collaborate more intensely with core/extended product teams. Considering all the possible problems that we have identified, the solution is actually rather simple. Instead of using one document to satisfy all of these demands, Agile product managers employ five key artifacts:

1. The Business Plan

This document is a summary of product vision, product goals, and how a product factors into overall strategy. The business plan includes market research results, financial summaries, and go-to-market and operational issues, as appropriate.

2. The Financial Model

This model explains how the product should perform financially over time, given the variables of sales performance, pricing, and costs.

3. The Roadmap

This document is a visual representation of how the product is intended to progress in order to meet the demands of the target markets described in the business plan.

4. The Release Plans

These are designed to communicate which capabilities and features will be delivered and when.

5. The Backlog

The backlog is made up of a product’s total set of big ideas, use cases, features, user stories, architectural work, etc. that may affect the product or be approached by the product over the course of its entire lifecycle. The backlog may list all of the work that needs to be accomplished, but these items will probably need more thorough communication during release and sprint planning. The development team should be prepared to ask any detailed questions needed to address backlog requests.

Agile product managers should be able to offer enough detail about the requirements of user stories scheduled for upcoming sprints. This means that they must work with the development team to determine the acceptance criteria for each user story. Agile product managers have a comprehensive set of artifacts and communication tools that they can employ to match every audience, taking into account various product uses and longevity of planning. This will lead to the creation of lo-fi prototypes and sketches, flowcharts and customer journey maps, wikis, and even sticky notes on whiteboards.

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