Formulating the product vision
The results from analyzing and prototyping will prepare the product owner, the team, and the stakeholders for the product vision workshop. This is a collaborative session that focuses on formulating the product vision while formulating some of the features to be included in the product backlog.
Coming up with the Product Vision
When the coming up with the product vision, it must ultimately answer the following questions:
1. Who are the target customers and users? Are the two different?
2. What problems will the product solve?
3. What attributes of the product will satisfy the customer needs?
4. Who are the internal and external competitors, and how do they perform?
5. What are the timeframe and budget for the project?
Product Vision Template
This Product Vision template briefly captures the answers to the questions above in this simple statement:
● For [target customer],
● Who [statement of need or opportunity]
● The [product name] is a [product category]
● That [key benefit or reason to buy]
● Unlike [primary competitive alternative]
● Our product [statement of primary differentiation]
The purpose of the product vision is to be the overarching theme of the entire product backlog that gives an understanding of what value the product will deliver as a whole. By doing research, analysis, and validation of ideas, your product vision will give the team a clear direction as to what you are building together.
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