What Is Agile?
Agile principles support the work of motivated individuals who are committed to delivering the highest value product. The Agile Scrum framework has three key roles: product owner, scrum master, and the scrum team members. The product owner is the true representative of the business vision and the voice of the customer. The role has the responsibility as the primary communicator of the goals and objectives to be realized in the delivery of a product. The product owner must be business savvy; having a clear understanding of the value to be delivered with the product, the product market and the business’ tolerance level for risk.
Product Value
Agile product owners work with stakeholders and scrum teams to deliver several scrum artifacts. The first in importance for a project is the vision statement. The vision statement should clearly articulate why the business is undertaking the time and cost of delivering a product. The vision statement is the baseline for the product features. The project’s business owner, product owner and scrum master will participate in visioning sessions to create the statement. All of the impacted stakeholders should review and approve the statement before the project moves forward.
The statement is a baseline in that Agile principles focus on being able to accept and adapt to change in the market, in the product or in the business assumptions. Therefore, the vision statement should clearly articulate why the product is being developed and the assumed value. It should not be so specific as to make it difficult to update during the life of the project. The vision statement will be used as an input to the backlog throughout the life of the project and be an output when modifications to the vision are required.
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