08. Prioritisation and Timeboxing

Question 1

What is MoSCoW?

Answer 1

Helps to prioritise requirements and needs into four simple categories so that everyone understands where their needs sit in the priority list.

Question 2

MoSCoW: Must have

Answer 2

= Minimum Usable SubseT (guaranteed)

Without this requirement there’s no point on this date / not legal / unsafe / not a viable solution

Question 3

MoSCoW: Should have

Answer 3

Important but not vital

May be painful to leave out but solution still viable

May need workaround which may be temporary

Question 4

MoSCoW: Coud have

Answer 4

Wanted or desirable but less important

Less impact if left out (compared with a Should)

Question 5

MoSCoW: Won’t have this time

Answer 5

Will not be delivered in this timeframe

Question 6

What does a DSDM structured timebox look like?

Answer 6

1. Kick off
2. Investigation (10-20% of effort)
3. Refinement (60-80% of effort)
4. Consolidation (10-20% of effort)
5. Close-out

Question 7

What does a free format timebox look like?

Answer 7

1. Kick off
2. Iterative development
3. Close-out

Question 8

When and where does the Daily Stand-up take place?

Answer 8

Same time, same place every day

Question 9

What format does the Daily Stand-up follow?

Answer 9

1. What have I done since the last stand-up to help achieve the Timebox objectives?
2. What will I be doing until the next stand-up to help achieve the Timebox objectives?
3. What problems/risks/issues do I have that will prevent me/the team achieving the Timebox objectives?

Question 10

The project lifecycle is split up into _________(1)________. These are broken up into ________(2)_________.

Answer 10

(1) increments

(2) timeboxes