This is where you begin your journey once you have an idea for a new product.
Product Innovation Framework
InRhythm’s innovative product development framework covers both what we build and how we build it.
This workflow shows how we answer the question: "Which product do we build?" It shows the path from validating solution (Value Sprint) to designing the product with customer in mind (Design Sprint) and, finally, creating the technology platform by defining architecture, data modeling, and tooling for the proposed solution (Foundation Sprint.)
Once this is completed, the teams start sprinting (see InRhythm Scrum Framework.)
Hover over Tap any point below to view more information about our process.
Your target audience, the market segment you will serve by launching this product
Customer needs that the product will fulfill and the benefit from the project execution
A business or marketing statement that summarizes why a consumer should buy a product or use a service rather than use competition.
Includes positioning statement:
- For “Target Segment”
- Who “Need Statement”
- The “Product” is a “Product Category”
- That provides “Value Proposition”
- Unlike “Top Competitor”
- The “Product” “Differentiating features”
Problem statement that is being addressed by the product implementation.
Answering the question “Is this problem big enough to solve?” gives you a clear understanding of how “juicy” the project, i.e. the level of potential it has for making a difference in the customer’s life.
Project's “true north”, the direction that guides the delivery team. It is the overarching goal everyone must share – Product Owner, ScrumMaster, team, management, customers and other stakeholders.
A product backlog modeling technique that helps understand the functionality of the system, identify holes and omissions in the backlog, and effectively plan holistic releases that delivery value to users and business with each release.
MVP (minimum viable product) prototypes are used in Lean product development for testing MVP with customers to gain faster learning with fewer resources.
MVP principle is based on shipping the essential feature set to make the product production ready get it in front of customer, study their behavior and pivot as needed.
"Problem-solution fit" is a measure how well the product satisfies the needs of your core customers.
- Validating value proposition with customer proxies
- Designing an experiment to test value proposition with customers (revealed preference)
- Establishing validation criteria
- Validating with real-world customers (get out of building)
The complete set of people who are involved, in any manner, in the development of a product.
High Level structure or structures of the product developer architecture, which comprise software elements, data elements, the externally visible properties of those elements, and the relationships among them.
The room where the entire Scrum team sits and works throughout the development process. Setting up the Rhythm Room is important, as it must contain all the apparatus required for good product development.
A team playbook is a single source of reference that helps improve business results, achieve synergies and economies of scale, address cultural issues, and implement best practices consistently.
A thin architecture slice validated at theme level used to verify overall architecture.
A system of signs, information displays, layouts, tools, color-coding, and other information radiators.
The subsequent workflow helps answer the question: "How do we build the product defined above?"
It shows the path from validating solution to product delivery including readiness, planning, delivery and validation rhythms.
It also covers scrum ceremonies: sprint planning, stand-up, review and retrospective, and provides checklists.
Click "Build" tap here to view our subsequent product development process: The Scrum Framework.