Scope

Question 1

What Techniques are used to Define Scope?

Answer 1

We define scope by analyzing the requirements.
1. Product Analysis: Analyze Product Requirements to convert them into Project Requirements aka Scope Statement(project work)
* examining and understanding the features, characteristics, and requirements of the product or deliverable that the project aims to create. It involves a detailed analysis of the product’s functionality, performance, design, components, and any other relevant attributes.

2. Product Breakdown Structure(PBS): Breaking down product/deliverables to get an idea of our scope.
   - Lv 1: Website
   - Lv 2: A. Sales Form, B. Front Page, C. Sales Backend
   - Lv 3: A1. Name/Details, A.2 Link to Paypal

3.User Story Mapping: Visualize Users Journey through product and breakdown the journey into actionable User Stories. Created by entire team(PO, SM, Agile team, SHs) To get shared understanding.
- Starts w/ a Backbone(top) w/ high level activities(or steps user takes)
- Beneath backbone are specific user stories/tasks arranged according to prioritiy and complexity.

Question 2

What are differences btw Kano and Moscow Techniques for Requirements Prioritization

Answer 2

MoSCoW: Used to reach common understanding w/ Shs on the importance of each requirement or feature. Useful for managing scope and making distinctions between critical and non critical requirements, especially in time constrained projects.

Prtz into categories: Must Have, SHould Have, Could Have, and Won’t Have.
Helps focus on the most critical features.

Kano Model: Approach to prioritizing features on product roadmap, based on degree they will satisfy custumer.
Categorize requirements into Delighters, Exciters, Satisfiers, Dissatisfiers, Indifferent.
Agile: Prtz features on Prod Roadmap

Benefit Cost Analysis: Evaluate benefit of implementing req/feature against the cost involved.
Prioritize reqs w/ highest benefit to cost ratio.

Kano vs Moscow Diff
Kano Model: Goal to understand and optimize customer satisfaction/happiness through feature selection.

MoSCoW Prioritization: Best for planning and managing project scope and ensuring that key deliverables are completed on time.
Colder: What must we have, not have, should have, could have.

E.2.Q.87: Need to prioritize feature list. If each SH wants their feature to be delivered first. How will you prioritize them?

-Not MOSCOW, because they will all say their features are Must have
-Need objective way to prioritize: Cost/Benefit analysis- Cost and benefit gained by each feature. And Payback Period: time to recover investment.

Question 3

What are techs to prioritize requirements

Answer 3

As you collect requirements or risks, and brainstorm solutions w/ your Sh, you may not have enough time or money to complete them all so we must prioritize them with techs like:

• MoSCoW: Must have, Should Have, Could have, Will not have. Can use voting w/ sh to decide prtz.
• Benefit/Cost Ratio: Item w/ highest Bnft, lowest cost
  
  • Benefit= Revenue not CF.
  • B/C X 100(Don’t forget x100)
• Cost of Delay (CD3): Use Value of the item vs time it will take to deliver.
  
  • Calculate expected weekly profit(or bnft) of an item once it is delivered.
  • Form: Feat X= ExptPrft/WksDlv
  • Feat1:WksDlv=4; Expctd Prft= $4k; CD3=4k/4= 1000