Download - Framework For Agile Product Management
![Page 1: Framework For Agile Product Management](https://reader035.vdocument.in/reader035/viewer/2022081816/5484a6c1b4af9fe1258b4734/html5/thumbnails/1.jpg)
Agile Product Management
By Derek Morrison
Lead Product Manager Author of the blog:
All About Product Management
![Page 2: Framework For Agile Product Management](https://reader035.vdocument.in/reader035/viewer/2022081816/5484a6c1b4af9fe1258b4734/html5/thumbnails/2.jpg)
Product Management Framework
Product Road-mapping
Requirements Management
Release Planning
Scrum
Theme Identification
Pre- Planning Planning Daily Stand-ups
Sizing backlog Defining Sprint Goals
Shaping-up backlog itemsRequirements gathering
Brain stormingTranslating strategy
Communication
Release notes
Release Plan
Backlog
Roadmap
SprintX + 8
SprintX + 5
SprintX
SprintX + 10
SOA Engagement
Analysis
Direction
Collaboration
![Page 3: Framework For Agile Product Management](https://reader035.vdocument.in/reader035/viewer/2022081816/5484a6c1b4af9fe1258b4734/html5/thumbnails/3.jpg)
• Translating business strategy into roadmap items • Aim to have a defined roadmap at least 6 months ahead of
the current sprint.• 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.
• Positive value added contributions at executive meetings and lead out on strategy days and brain storming sessions
• Identify broad themes
Product Road-mapping
Theme Identification
Brain stormingTranslating strategy
![Page 4: Framework For Agile Product Management](https://reader035.vdocument.in/reader035/viewer/2022081816/5484a6c1b4af9fe1258b4734/html5/thumbnails/4.jpg)
• Taking in requirements from across the business either formal or ad hoc.
• 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.
• Firming up on the requirements
Requirements Management
Shaping-up backlog itemsRequirements gathering
![Page 5: Framework For Agile Product Management](https://reader035.vdocument.in/reader035/viewer/2022081816/5484a6c1b4af9fe1258b4734/html5/thumbnails/5.jpg)
• Working with the technical team to estimate backlog items.
• Prioritise themes and goals for the next quarter – updated at the end of every sprint.
• Create and distribute release plan – keep highly visible.
Release Planning
Sizing backlog Defining Sprint Goals
![Page 6: Framework For Agile Product Management](https://reader035.vdocument.in/reader035/viewer/2022081816/5484a6c1b4af9fe1258b4734/html5/thumbnails/6.jpg)
• Teams velocity determines how many backlog item are scheduled into the coming sprints
• Creation of user stories from backlog items – user-stories signed off by commercial stakeholders and Product Owner.
• Test cases/confirmation part of the user story drives development
• UAT sign-off by domain experts & Product Owner• Release notes circulated to all stakeholders.
Scrum
Pre- Planning Planning Daily Stand-ups
![Page 7: Framework For Agile Product Management](https://reader035.vdocument.in/reader035/viewer/2022081816/5484a6c1b4af9fe1258b4734/html5/thumbnails/7.jpg)
• Compare product road maps in order to avoid duplication of development.
• Collaborate with product management from across the enterprise.
• Review and analyse roadmaps & project plans – comparing with 3rd party platform vendor roadmap and backlog – identify possible synergies.
• Advise on best path to proceed. • Update backlog and release plans if need
be.
SOA Engagement
Analysis
Direction
Collaboration
![Page 8: Framework For Agile Product Management](https://reader035.vdocument.in/reader035/viewer/2022081816/5484a6c1b4af9fe1258b4734/html5/thumbnails/8.jpg)
• Hierarchy of documents used for product communication.
• Roadmap reviewed & re-published monthly.
• Backlog constantly evolves• Frequency of publication for
release plan and release notes are fixed (every sprint).
Communication
Release notes
Release Plan
Backlog
Roadmap