The Product Owner role in Agile testing and deployment
Agile projects are based on providing feature value faster to the customer. This requires that the product owner be an integral part of the design, development, and testing that takes place during sprint execution. As features are ready to review the product owner will jointly test deliverables with the rest of the scrum team. Test cases are developed as part of the creation of the user stories in the form of Acceptance Criteria. This enables the development team to clearly understand the expectations of the story and aides in final validation that features are ready for review by key stakeholders.
The product owner holds considerable responsibility during the deployment of features. As the voice of the customer, the product owner will work with key stakeholders to review features for approval. The product owner will also keep an eye on the performance of features delivered to validate if changes are needed to the backlog for future releases.
The Evolution of the Product Owner
As Agile principles became widely valued in project delivery, the role of the product owner has evolved from being a scribe to fully participating as an owner of the end product. The product owner will champion the iterative approach with the scrum team to ensure that the right features and user stories are delivered. Feature definition will align and change as required to focus on a minimally viable product that meets the vision of the key stakeholders.
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