A product vision is a statement that describes the desired outcome and value proposition of a solution. It helps guide the development of the solution by providing a clear and compelling direction. A product vision also helps drive a solution roadmap, which shows the planned features and milestones for the solution over a timeline. A product vision is part of the solution intent, which is the repository of the current and intended solution behavior and design.

References :

Solution Intent

Solution Vision

Roadmap

Solution Management

The most important planning question for primary research is what will be asked, because this determines the type, quality, and relevance of the data that will be collected. The research question or hypothesis should be specific, narrow, and discoverable through primary research methods, and it should align with the research purpose and objectives. The research question or hypothesis guides the choice of the research medium, the sample size and selection, and the data analysis and interpretation.

References :

What is Primary Research? : This article from Purdue OWL defines primary research and explains the steps and considerations involved in planning and conducting primary research.

10.3: Planning Your Primary Research Project : This article from Humanities LibreTexts provides some tips and examples on how to plan a primary research project, including defining the research question or hypothesis, choosing the research method, and designing the research instrument.

A story map is a visual tool that helps product teams organize and prioritize user stories based on the user journey and the value they deliver. A story map shows the main activities or steps of the user journey as the backbone of the feature, and the stories that support each activity as the slices of the feature. A team would create a story map when stories work together to support a workflow, because it helps them to understand and communicate the big picture of the user goals and needs, and to identify the minimum viable product (MVP) scope.

References :

Story Mapping : This article from the Scaled Agile Framework explains the purpose, process, and benefits of story mapping, and provides an example of how it can be used in a SAFe context.

User Story Mapping: Discover the Whole Story, Build the Right Product : This book by Jeff Patton, the creator of story mapping, provides a comprehensive guide on how to use story mapping to create better products and services that delight customers.

How to Create a User Story Map: Step by Step Guide with Examples : This article from Miro provides a detailed guide on how to create a user story map, with examples and templates for different types of products and services.

One of the strengths of qualitative research is that it can be applied to a large number of people, as it does not require a fixed sample size or a predefined set of questions. Qualitative research can use various methods, such as interviews, focus groups, observations, or document analysis, to collect data from different sources and contexts. This allows researchers to explore a wide range of perspectives, experiences, and meanings, and to generate rich and diverse insights.

References :

23 Advantages and Disadvantages of Qualitative Research

5 Strengths and 5 Limitations of Qualitative Research

According to the SAFe® Agile Product Management APM (6.0) documents and learning resources, innovation context type refers to the level of uncertainty and risk associated with the innovation. There are four types of innovation context: portfolio, solution, feature, and business agility. Solution context type is the most complex and uncertain type, as it involves creating integrated, end-to-end products and service offerings that solve complex market problems across trains. Solution context type requires a high degree of collaboration and alignment among multiple teams and stakeholders, as well as frequent experimentation and validation of assumptions.

References :

SAFe Innovation Framework for Lean Enterprises: What to Know

Solution Context - Scaled Agile Framework

Gemba is a Japanese term that means “the real place” or “the place where value is created”. In the context of the CDP, Gemba refers to the practice of going to the source of customer needs and feedback, and observing and learning from them. Gemba is an integral part of Continuous Exploration (CE), which is the first aspect of the CDP that drives innovation and fosters alignment on what should be built. CE involves applying Customer Centricity and Design Thinking to understand and create alignment on new development opportunities, and validating them with customers using hypothesis-driven experiments.

References :

Continuous Exploration : This article from the Scaled Agile Framework explains the purpose, process, and benefits of CE, and how it uses Gemba, design thinking, and lean startup methods to explore the market and customer needs, and define a vision, roadmap, and set of features for a solution.

Gemba Walk: How to Drive Continuous Improvement in Manufacturing with Connected Work : This article from Parsable describes how Gemba walks can help manufacturing leaders and teams identify and solve problems, improve processes, and increase customer value. It also provides some tips and best practices for conducting effective Gemba walks using connected worker technology.

According to the SAFe® Agile Product Management APM (6.0) documents and learning resources, market segment value is the total value of a specific market segment for a given solution. It is calculated by multiplying the number of potential customers in the segment by the average revenue per customer and the expected market share. The expected market share depends on several factors, such as the value proposition, the competitive advantage, and the number of existing competitors. Therefore, the number of existing competitors is a factor that must be included when building a model of market segment value.

References :

Agile Product Management - Scaled Agile Framework

Customer Centricity - Scaled Agile Framework

5.4 Essential Factors in Effective Market Segmentation