The Product Backlog
The product backlog is a listing of features that will be the primary roadmap for the life of the project. The product owner is responsible for creating, communicating and refining the backlog. Value is demonstrated in the prioritization of features to ensure that the items with maximum market impact are delivered first. Features included will focus on new delivery as well as items required to make a product sustainable and scalable. Just enough information in terms of descriptions is included to avoid wasting time and money on features that may not make it to an executable sprint. The product owner will re-order and re-scope the backlog throughout the project to meet the needs of all stakeholders.
Product Market
The product owner will have immense knowledge of the business that the product supports. Equally important is having an understanding of the market and the needs of the end-users or customers who will purchase and use the product. Market knowledge of competitor products, economic implications and product trends will be foremost in the mind of the product owner. As sprints are delivered to the market, the product owner will need to stay abreast of the acceptance and any modifications required.
Agile’s inspect and adapt model embraces changes and transparency. It is the responsibility of the product owner to communicate changes in the market and potential challenges to the scrum master and team for faster adoption. A strong product owner will create business models that define where the value is for delivery of a product vision and backlog. The product owner must also be able to communicate with various levels of authority to translate market changes that will impact design and delivery.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course:
Course Contents
Section 1: Agile Project Management
Section 2: Using the Agile Manifesto to Deliver Change
Section 3: The 12 Agile Principles
Section 4: The Agile Fundamentals
Section 5: The Declaration of Interdependence
Section 6: Agile Development Frameworks
Section 7: Introduction to Scrum
Section 8: Scrum Projects
Section 9: Scrum Project Roles
Section 10: Meet the Scrum Team
Section 11: Building the Scrum Team
Section 12: Scrum in Projects, Programs & Portfolios
Section 13: How to Manage an Agile Project
Section 14: Leadership Styles
Section 15: The Agile Project Life-cycle
Section 16: Business Justification with Agile
Section 17: Calculating the Benefits With Agile
Section 18: Quality in Agile
Section 19: Acceptance Criteria and the Prioritised Product Backlog
Section 20: Quality Management in Scrum
Section 21: Change in Scrum
Section 22: Integrating Change in Scrum
Section 23: Managing Change in Scrum
Section 24: Risk in Scrum
Section 25: Risk Assessment Techniques
Section 26: Initiating an Agile Project
Section 27: Forming the Scrum Team
Section 28: Epics and Personas
Section 29: Creating the Prioritised Product Backlog
Section 30: Conduct Release Planning
Section 31: The Project Business Case
Section 32: Planning in Scrum
Section 33: Scrum Boards
Section 34: Sprint Planning
Section 35: User Stories
Section 36: User Stories and Tasks
Section 37: The Sprint Backlog
Section 38: Implementation of Scrum
Section 39: The Daily Scrum
Section 40: The Product Backlog
Section 41: Scrum Charts
Section 42: Review and Retrospective
Section 43: Scrum of Scrums
Section 44: Validating a Sprint
Section 45: Retrospective Sprint
Section 46: Releasing the Product
Section 47: Project Retrospective
Section 48: The Communication Plan
Section 49: Formal Business Sign-off
Section 50: Scaling Scrum
Section 51: Stakeholders
Section 52: Programs and Portfolios