Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Framework For Agile Product Management


Published on

A useful framework for those who are practicing agile product management and working closing with engineering/development teams as the product owner.

Published in: Business, Technology, Education
  • Really good stuff, thanks for sharing! Two questions - (1) Could you show some timeline-perspective that shows the same info in slide 2, but relative to the cadence of the implementation team. (2) I've found keeping an evergreen 'view of the market' as a separate repository the reflects my incrementally improving view of the market to be a particularly useful artifact. It helps with communication about the 'why', both with execs and implementation team members. How would you add that into this framework?
    Are you sure you want to  Yes  No
    Your message goes here

Framework For Agile Product Management

  1. 1. Agile Product Management <br />By <br />Derek Morrison <br />Lead Product Manager <br />Author of the blog: <br />All About Product Management <br />
  2. 2. Product Management Framework <br />Product Road-mapping<br />Sprint<br />X + 10<br />Communication<br />Theme Identification <br />Translating strategy<br />Brain storming<br />Roadmap<br />Backlog<br />Requirements Management<br />Sprint<br />X + 8<br />Release Plan<br />Requirements gathering<br />Shaping-up backlog items<br />Release notes<br />Release Planning<br />Sprint<br />X + 5<br />SOA Engagement<br />Sizing backlog<br />Defining Sprint Goals<br />Collaboration <br />Analysis <br />Scrum<br />Sprint<br />X<br />Pre- Planning<br />Planning<br />Daily Stand-ups<br />Direction<br />
  3. 3. Product Road-mapping<br />Theme Identification <br />Translating strategy<br />Brain storming<br />Translating business strategy into roadmap items <br />Aim to have a defined roadmap at least 6 months ahead of the current sprint.<br />Product discovery and Innovation: constantly be on alert for new ways of doing things - enhancements to current features, new features, keeping abreast of what’s happening on the web sphere. <br />Positive value added contributions at executive meetings and lead out on strategy days and brain storming sessions<br />Identify broad themes<br />
  4. 4. Taking in requirements from across the business either formal or ad hoc.<br />Ensuring there is a level of clarity to each backlog item i.e. would a 3rd person be able to understand what is being requested. <br />Firming up on the requirements<br />Requirements Management<br />Requirements gathering<br />Shaping-up backlog items<br />
  5. 5. Working with the technical team to estimate backlog items.<br />Prioritise themes and goals for the next quarter – updated at the end of every sprint.<br />Create and distribute release plan – keep highly visible. <br />Release Planning<br />Sizing backlog<br />Defining Sprint Goals<br />
  6. 6. Teams velocity determines how many backlog item are scheduled into the coming sprints<br />Creation of user stories from backlog items – user-stories signed off by commercial stakeholders and Product Owner.<br />Test cases/confirmation part of the user story drives development<br /> UAT sign-off by domain experts & Product Owner<br />Release notes circulated to all stakeholders. <br />Scrum<br />Pre- Planning<br />Planning<br />Daily Stand-ups<br />
  7. 7. Compare product road maps in order to avoid duplication of development. <br />Collaborate with product management from across the enterprise.<br />Review and analyse roadmaps & project plans – comparing with 3rd party platform vendor roadmap and backlog – identify possible synergies. <br />Advise on best path to proceed. <br />Update backlog and release plans if need be. <br />SOA Engagement<br />Collaboration <br />Analysis <br />Direction<br />
  8. 8. Communication<br />Roadmap<br />Hierarchy of documents used for product communication.<br />Roadmap reviewed & re-published monthly.<br />Backlog constantly evolves<br />Frequency of publication for release plan and release notes are fixed (every sprint). <br />Backlog<br />Release Plan<br />Release notes<br />