top of page

3. VIRALITY STAGE

lean-analytics-process-v7_orig.png

1. Requirements Elicitation (E1)

  1. Interviews with employees

  2. Surveys

  3. Problem solution canvas

  4. User observation or shadowing of users

  5. Workshops or focus groups

  6. User testing or usability testing

  7. Brainstorming

  8. Stakeholder analysis

  9. Goal modelling

  10. Context modelling

  11. Storytelling and scenario modelling

  12. Identifying risks and threats

  13. Describing rationales

  14. Online reviews

  15. Jobs To Be Done

  16. Design Thinking

  17. Acquisition or viral pattern and viral loop mapping

  18. Idea gathering from team members

  19. Sprint

  20. Customer Journey maps or user flows

  21. Process maps

  22. Model driven engineering

  23. Goal oriented requirements engineering

  24. Ishikawa Fishbone Diagram or Cause and Effect diagram

  25. Business process modelling

  26. Market analysis (data from marketing campaigns)

  27. Heatmaps

  28. Competitive analysis

  29. Defect logs - e.g. bug reports

  30. Activity diagrams (flowcharts)

  31. Message sequence diagrams

  32. Entity relationship diagrams

  33. 5 why’s

2. Requirements Analysis (A1)

  1. Problem solution canvas

  2. Growth hacking

  3. Use cases

  4. Role playing

  5. Design Thinking

  6. Acquisition or viral pattern and viral loop mapping

  7. Sprint

  8. Customer Journey maps or user flows

  9. Process maps

  10. Model driven engineering

  11. Goal oriented requirements engineering

  12. Market analysis (data from marketing campaigns)

  13. Heatmaps

  14. Competitive analysis

  15. Activity diagrams (flowcharts)

  16. Finite state machines

  17. Message sequence diagrams

  18. Entity relationship diagrams

  19. 5 why’s


3. Requirements Specification (S1)

  1. User stories

  2. Constraints

  3. Sprint

  4. Goal oriented requirements engineering

​
4. Requirements Prioritization (P1)

  1. Numerical Assignment or planning poker or assigning relative value points

  2. Table-top relative estimation

  3. Top ten Requirements

  4. Prioritization based on set of weighted criteria

  5. Simple rating system

  6. Product council

  7. Prioritisation by Cost of Delay

  8. Prioritizing features for differential value (Kano Model of customer satisfaction)

  9. Dot Voting method

5. Requirements Validation (V1)

  1. Interviews with employees

  2. Surveys

  3. Growth hacking

  4. User observation or shadowing of users

  5. Workshops or focus groups

  6. User testing or usability testing

  7. Role playing

  8. User Experience mock-ups or Prototypes

  9. Online reviews

  10. Jobs To Be Done

  11. Design Thinking

  12. Acquisition or viral pattern and viral loop mapping

  13. Sprint

  14. Customer Journey maps or user flows

  15. Process maps

  16. Model driven engineering

  17. Goal oriented requirements engineering

  18. Business process modelling

  19. Modelling Strategic Actor Relationships and Rationales

  20. Market analysis (data from marketing campaigns)

  21. Heatmaps

  22. Just-In-Time story elaboration

  23. Competitive analysis

  24. Activity diagrams (flowcharts)

  25. Finite state machines

  26. Message sequence diagrams

  27. Entity relationship diagrams

  28. Scenarios or acceptance test

  29. 5 why’s

​
6. Requirements Management (M1)

  1. Flagging and tagging the product backlog items with corresponding KPIs

  2. Product vision board

  3. Kanban

  4. Scrum

  5. Defect logs - e.g. bug reports

bottom of page