Main Takeaways:
- Set realistic and achievable product goals
- Be open to ideas but don’t get overwhelmed & Prioritization techniques to achieve a healthy mix
- Feedback and Feed forward
7. Key takeaways
• Difference between Product Strategy,
Roadmap and Backlog
• Build an effective backlog
• Prioritization techniques to achieve a
healthy mix
• Feedback and Feed forward
8. Product Strategy, Product Roadmap and Product Backlog
• Derived from product Roadmap
• Short term goals & deliverables
• Task level work-items
Backlog
• Visualization of Product strategy
• Broken down by Functions
• Medium term
• Timeframes and high-level themes
Roadmap
• Aspirational Business Goals
• Long term vision for Product
• Value Proposition
• Cross functional
Strategy
Strategy, Roadmaps and Backlog are built upon one another — you need all three to create winning plans and realize your goals.
9. What is Product
Backlog?
• Product Backlog is an ordered list of desired product
functionality.
• Items that typically go into a product backlog can
include new features, feature enhancements, bug fixes,
platform enhancements (POCs, technical debts etc).
• Ideally, it should be the single source of requirements
for any changes to be made to the product.
• While the owner is Product Manager, the main
audience is Product, UX, Business and Development
teams.
10. Why is Product
Backlog so important?
• Product backlog is the key deliverable of a Product
Manager.
• It provides a centralized and shared understanding
of what to build and the order in which to build it.
• The success of a product and executing team
depends greatly on what goes in the Product
Backlog.
11. What are the
qualities of an
effective
backlog?
Well groomed
Emergent
Prioritized
Well categorized
ClearalignmenttoProductRoadmap
12. Building Product Backlog: How and Where to
start?
Collaborative approach works best
Leverages knowledge and creativity of team.
Builds a strong buy-in.
Reduces risk in understanding why we are doing
what we ae doing.
Gather ideas
Review the product performance against KPIs.
Look for new market trends.
Keep an eye on competition.
Follow developments to your product strategy.
Involve stakeholders
Business teams, Analytics, UX research,
Content, Engineering etc.
Helps look beyond functional requirements-
user interaction, user interface, non-functional
requirements.
14. Prioritize
•Keep Focus on your product goals
•Think Short term and long term
Prioritization techniques:
https://businessanalystlearnings.com/blog/2016/8/18/a-list-of-requirements-prioritization-tec
hniques-you-should-know-about
15. Start writing
User stories
Who is the target
customer
Persona
What is the problem Observations
What are the benefits Hypothesis
Definition of Done
Acceptance Criteria
Success Metrics
16. Organize and
Iterate
• Regularly groom and refine the backlog
• Remove and add new items and update
existing ones.
• Break larger items into smaller ones.
• Maximize your product value by
• Building an effective feedback
mechanism.
• Analyzing feedback and data collected
from exposing the latest product
increment to users and apply the new
insights to the backlog.