​​

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 Six: Communicating to all stakeholders, all the time

More on Responsibility Six: Communicating to all stakeholders, all the time

By Brad Murphy

Posted in Agile Product Management Tagged as Agile, communication, stakeholders

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

In my last post, I addressed the need to continuously inform stakeholders of development status. Sooner or later, a team will have to decide on a precise date and set of features, capabilities, and architectural elements. At a realistic point in the release cycle, a team should hold a commitment meeting to ensure that every member is committed to getting the software shipped – and that the work being shipped is suitable for the market.

At this meeting, the rest of the company can also commit to their plans and finish off whatever remaining work needs to be done before the product can go to market. Moreover, sales teams and executives will need to be positive about communicating upcoming products and their final release dates in their own presentations and external roadmaps, gathering interested customers to participate in early trials and getting the word out in publicizing the product overall.

Agile product managers improve their ability to incorporate this information into higher-level planning artifacts, such as release plans and roadmaps. This means they become more able to pass on precise and decisive communications concerning the product, market, customers, and team in their portfolio planning sessions. Gradually, portfolio managers will come to appreciate just how clued-in an Agile Product Manager really is, perhaps even recognizing him or her as the most capable person at helping the company make sound financial decisions.

As an organization transfers all of their teams to Agile, each with its own veteran Agile Product Management team, a company can re-balance their portfolios more often based on the new factual information available to them through the Agile process. This portfolio re-balancing, in addition

to assuring a higher quality of incoming information, means that a technology company can better allocate scant resources by sinking them into the highest value opportunities.

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