2. STICKINESS STAGE
1. Requirements Elicitation (E1)
-
Potential user and customer interviews
-
Surveys
-
Problem solution canvas
-
User observation or shadowing of users
-
Workshops or focus groups
-
User testing or usability testing
-
Brainstorming
-
Stakeholder analysis
-
Goal modelling
-
Context modelling
-
Storytelling and scenario modelling
-
Identifying risks and threats
-
Describing rationales
-
Customer or stakeholder feedback
-
Online reviews
-
Jobs To Be Done
-
Design Thinking
-
Customer development
-
Idea gathering from team members
-
Sprint
-
Customer Journey maps or user flows
-
Process maps
-
Model driven engineering
-
Goal oriented requirements engineering
-
Ishikawa Fishbone Diagram or Cause and Effect diagram
-
Seven stage model
-
Business process modelling
-
e3 value modelling (Value Network Analysis)
-
Market analysis (data from marketing campaigns)
-
Feedback from support and sales staff
-
Heatmaps
-
Competitive analysis
-
Customer change request systems
-
Defect logs - e.g. bug reports
-
Activity diagrams (flowcharts)
-
Message sequence diagrams
-
Entity relationship diagrams
-
5 why’s
-
LightCDD
2. Requirements Analysis (A1)
-
Potential user and customer interviews
-
Problem solution canvas
-
Role playing
-
Design Thinking
-
Sprint
-
Customer Journey maps or user flows
-
Process maps
-
Model driven engineering
-
Goal oriented requirements engineering
-
Seven stage model
-
Enterprise Knowledge Development (EKD) framework
-
Market analysis (data from marketing campaigns)
-
Heatmaps
-
Competitive analysis
-
Activity diagrams (flowcharts)
-
Message sequence diagrams
-
Entity relationship diagrams
-
5 why’s
-
LightCDD
3. Requirements Specification (S1)
-
User stories
-
Constraints
-
Sprint
-
Goal oriented requirements engineering
-
Seven stage model
4. Requirements Prioritization (P1)
-
Numerical Assignment or planning poker or assigning relative value points
-
Table-top relative estimation
-
Top ten Requirements
-
Simple rating system
-
Product council
-
Prioritisation by Cost of Delay
-
Dot Voting method
5. Requirements Validation (V1)
-
Potential user and customer interviews
-
Surveys
-
User observation or shadowing of users
-
Workshops or focus groups
-
User testing or usability testing
-
Role playing
-
User Experience mock-ups or Prototypes
-
Customer or stakeholder feedback
-
Online reviews
-
Jobs To Be Done
-
Design Thinking
-
Customer development
-
Sprint
-
Customer Journey maps or user flows
-
Process maps
-
Model driven engineering
-
Goal oriented requirements engineering
-
Seven stage model
-
Enterprise Knowledge Development (EKD) framework
-
Business process modelling
-
Modelling Strategic Actor Relationships and Rationales
-
e3 value modelling (Value Network Analysis)
-
Market analysis (data from marketing campaigns)
-
Heatmaps
-
Just-In-Time story elaboration
-
Competitive analysis
-
Customer change request systems
-
Activity diagrams (flowcharts)
-
Message sequence diagrams
-
Entity relationship diagrams
-
Scenarios or acceptance test
-
5 why’s
-
LightCDD
​
6. Requirements Management (M1)
-
Flagging and tagging the product backlog items with corresponding KPIs
-
Product vision board
-
Kanban
-
Scrum
-
Defect logs - e.g. bug reports