Moscow priority sorting method in Agile Development

Author: Chen Yong

Source: blog.csdn.net/cheny_com

 

Is there a situation where an important entry is missed every time?

When the sprint is over, do you find that a lot of entries have already started but are not completed?

Does the product owner want to use an important change to replace some entries in the original sprint backlog and find that these entries are "under development?

Is there a team dispute that all entries should be completed each time (which is really difficult) or only the most important items must be completed?

Is there a team dispute over whether to extend the sprint by one day to complete the last almost completed task?

 

These are related to the priority sorting method of Moscow.

 

Generally, the Moscow method is used for this sort in the iteration plan, which divides the entries in the sprint backlog into four levels (in fact, only the first three levels ):

Must: required;

Shoud: what should be done;

Cocould: something that can be done;

Wocould not: Do not do it.

We need to follow these steps to ensure that the must and shold required by the product owner can be completed, and strive to ensure that the cocould can be completed. In the case of important changes, we should sacrifice the cocould and even the shocould to ensure the change.

 

If you use the story wall for management, it is best to release the story to be developed based on three levels: M, S, and C (W won't actually appear), take M first, and finally change C. If you want to, you can use three colors of paper, to prevent M, s before the completion of C.

Moscow is just a sorting method for sprint backlog. For more information about "Priority sorting" in Agile, see: view the self-similarity of agile development based on priority sorting.

 

Click to download the free agile development textbook: Martian agile development manual