1.
Build & Keep a healthy backlog
A well defined and prioritized product backlog exposes all the important things your teams need to focus on to
deliver business value. It makes release and iteration planning easier and helps setting expectations with
stakeholders and other teams.
Building a product backlog is not done in a vacuum, but in collaboration with different stakeholders and customers.
A well defined and prioritized product backlog exposes all the important things your teams need to focus on to
deliver business value. It makes release and iteration planning easier and helps setting expectations with
stakeholders and other teams.
Building a product backlog is not done in a vacuum, but in collaboration with different stakeholders and customers.
April. 2020
hussam.ahmad@gmail.comhttps://www.linkedin.com/in/hussamahmad/

2.
page
02
We deliver iteratively and in increments
https://www.linkedin.com/in/hussamahmad/ hussam.ahmad@gmail.com
SprintBacklog

3.
page
03
Product Backlog
• Product Backlog
• List of requirements and issues
• Owned by the Product Owner
• Anybody can add to it
• One Product Owner prioritized
• Sprint Backlog
• A short list for the sprint, can be one-liner
• “make the application available on MySQL in addition to SQL Server”
• Declared by the Product Owner
• Accepted by the Team
• Broken down into tasks by the team
https://www.linkedin.com/in/hussamahmad/ hussam.ahmad@gmail.com
Product Management + Architects
decides the backlog
Managed by the Product Owner

4.
page
04
Levels of planning
• Strategy  Done by Strategic Themes(Corportate executives, Portfolio
Management & Architects)
• Portfolio  Done by Portfolio Management
• Product  Done by Product Management
• Product Increment  Done by the teams
• Sprint  Done by a Team
• Day  On daily basis
https://www.linkedin.com/in/hussamahmad/ hussam.ahmad@gmail.com

5.
page
05
The overall picture
https://www.linkedin.com/in/hussamahmad/ hussam.ahmad@gmail.com

6.
page
06
Not everything needs to be ready from the beginning
https://www.linkedin.com/in/hussamahmad/ hussam.ahmad@gmail.com
1 2 3 4 5 6 7
Detailed short term plan
Uncertain longer term plan
1 2 3 4 5 6 7
Backlog refinement (PO + BA) Backlog Management (Product Manager +PO + Architect)

7.
page
07
Product Manager Vs. Product Owner
• Product Manager
• Has Marked focus
• Owns the Vision and strategic
backlog
• Works with Architects on Non
functional requirements
• Defines Features and Product
Increments
• Resposible for Roadmaps
• ROI
https://www.linkedin.com/in/hussamahmad/ hussam.ahmad@gmail.com
• Product Owner
• Has Team focus
• Owns team backlog
• Defines iteration
backlogs and stories
• Feeds back to the
vision, roadmaps
and ROI

8.
page
08
Bringing order from chaos
https://www.linkedin.com/in/hussamahmad/ hussam.ahmad@gmail.com

9.
page
09
Sprint Preparation – PO responsibility
• When allocating stories to the sprint backlog, PO needs to:
• Ensure capacity allocation is respected
• There is enough time to do NFRS while adding new features
• Ensures that customer priority and product roadmap drives work planning
• Challenges team innovation in deciding competitive, demonstrable objective
• Gives product management early warning of potential obstacles
• Balances near term and long term objectives
• Promotes entrepreneurial spirit and full team contribution
https://www.linkedin.com/in/hussamahmad/ hussam.ahmad@gmail.com

10.
Experiences by Rafal
Jakobsen
rafal.jakobsen@protonmail.comhttps://www.linkedin.com/in/rafal-jakobsen/

11.
page
011
Our Backlog Process - Fjordkraft
https://www.linkedin.com/in/rafal-jakobsen/ rafal.jakobsen@protonmail.com
1. Whats needs to be done? «Title»
2. Select Issue Type «Task, Bug, ETC...»
3. Select Parent «If the task have a parent, we normally start there»
4. Description «Our goal is to deliever high quality descriptions, to make our future easier»
5. Defenition of Done
6. Priority «How important is this task/user storie?»
7. Responsible «Who is the best fit for this task?»
The journey starts with making high quality task/user stories. This is essential for a healthy backlog.
Next... Task/User Storie get added to the backlog

12.
page
012
Our Backlog Process - Fjordkraft
https://www.linkedin.com/in/rafal-jakobsen/ rafal.jakobsen@protonmail.com
Ongoing process
Once every sprint Feedback becomes new task/user stories
The best POs are continuously reviewing and
grooming the backlog

13.
Experiences by Nikolas Kallas
An example of the flow and structure from roadmap to product backlog
to product development backlog
nikolas.kallas@gmail.comhttps://www.linkedin.com/in/nikolaskallas/

14.
page
014
Feeding the backlogs
https://www.linkedin.com/in/nikolaskallas/ nikolas.kallas@gmail.com
Product Vision
Product Strategy
Identify Initiatives to meet the
strategy
Scoring Initiatives
Product Roadmap
Product
Management
Product Planning Board
STRATEGY
Product Development Board
EXECUTION
Scrum Team
Product Backlog Sprint Backlog

15.
page
015
Product Planning Board
https://www.linkedin.com/in/nikolaskallas/ nikolas.kallas@gmail.com

16.
page
016
Product Development Board
https://www.linkedin.com/in/nikolaskallas/ nikolas.kallas@gmail.com

17.
page
017
Product Development Sprint
https://www.linkedin.com/in/nikolaskallas/ nikolas.kallas@gmail.com