MoSCoW Prioritisation (Chapter 10) Flashcards

1
Q

What is prioritisation applied to in DSDM?

Why?

A

Requirements/user stories, i.e. features

Because time, cost and quality are fixed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What does MoSCoW stand for?

A

Must Haves
Should Haves
Could Haves
Won’t Have This Time

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is another name for the Must Haves?

A

Minimum Useable Subset

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are the Must Haves?

A

The requirements the project GUARANTEES to deliver.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

How much of the total effort should be dedicated to delivering the Must Haves?

A

No more than 60%

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

The Must Haves are…

A

Vital

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

The Should Haves are…

A

Important

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Give 3 points about the Should Haves.

A

1) Important but not vital
2) May be painful to leave out but solution still viable
3) May need some kind of workaround

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Could Haves are more painful to leave out than Should Haves. True or false?

A

False - Should Haves are important Could Haves are desirable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Give 2 points about Could Haves.

A

1) Desirable but not important

2) Less impact if left out

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Which features provide contigency in a DSDM project?

Why?

When might they be left out?

A

Could Haves

They are desirable but not important

The deadline is at risk

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What percentage of effort should be spent delivering the Could Haves?

A

20%

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the Won’t Haves?

A

Requirements the project team have agreed won’t be delivered IN THIS TIMEFRAME

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Why bother including the Won’t Haves in the PRL? (2)

A
  1. They help to clarify the scope of the project

2. They help to manage expectations

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is confirmed by the end of Foundations? (2)

A
  1. The end dates for the project

2. Dates for the first Project Increment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the three LEVELS of priority that requirements have?

A
  1. MoSCoW for the project
  2. MoSCoW for the Project Increment (lifecycle phase)
  3. MoSCoW for the timebox
17
Q

If the effort required for the Must Haves exceeds 60%, then…

Why?

A

The guarantee to deliver the MUST is put at risk.

It is likely the task has been misunderstood.

18
Q

What is delivered in the worst case?

But what is the aim?

A

Must Haves

Must and Should Haves