SWOT Analysis
A product vision can be born out of a SWOT or Gap analysis. SWOT stands for strengths, weaknesses, opportunities, and threats and by breaking down a company’s current offering into these pieces, it can help identify areas or products worth pursuing. For example, maybe your company specializes in IT support but there is an opportunity for your company to develop a customer support system since one of your strengths is the friendliness of your staff.
SWOT Analysis
There may also be a threat your company is facing since another competitor began to offer a more robust suite of full IT support. By performing a SWOT analysis it can keep you one step ahead in coming up with new product ideas.
Gap Analysis
Additionally, Gap analysis is a great tool to identify where your company is not meeting performance expectations. Gap analysis looks at the gap between where the company is currently performing and its targeted performance. Maybe the goal was a certain number of users in your app, by looking at this gap you can then develop ideas and product visions on how to solve that problem. In this case, you may look at the Gap and determine you need to put more spending into ads to drive more people to the app or you may determine that you need to develop a new feature within the app that will ensure it is fully differentiated and marketable.
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