​​

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 / Responsibility Four: Customer input and collaboration

Responsibility Four: Customer input and collaboration

By Brad Murphy

Posted in Agile Product Management Tagged as Agile, customers

Throughout the development cycle, Agile product managers must keep customers informed to make certain that their products are progressing according to expectations. An Agile Product Manager uses a number of mechanisms in order to gather useful information, involving the whole team and using different communication vehicles to convey rich customer information.

Market research and voice-of-the- customer input are essential to getting a new product green-lighted and integrated into the overall product strategy. This kind of information can be gathered from departments within many organizations that are already working to the same end: marketing, sales, customer service, and field services all liaise with customers and conduct market research of their own on a regular basis. It is up to an Agile Product Manager to compile this information.

Aside from this wider gathering of organizational information, an Agile Product Manager must also collaborate directly with customers to make certain that their product stays on target over the course of the development cycle. An Agile Product Manager must forge and maintain links with the customer throughout the course of the release.

These links occur naturally in the opening stages of the project through customer gatherings that include user groups, training sessions, and technical briefings. Agile product managers can use these meetings to communicate with customers about the vision and goals for the upcoming release, or they may even schedule individual meetings with lead customers. In either scenario, certain artifacts are of particular importance in order to effectively communicate features. A Product Manager can use wireframes or storyboards of new features, offer descriptions of release goals, and prioritize a backlog of use cases, features, bug fixes, and enhancements.

My next post will discuss the benefits of customer input to Agile Product Managers.

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