Monday, May 12, 2008


I've given myself an aim of learning something new everyday. Today I'm posting about MoSCoW

MoSCoW is a method that is used in business and particularly in software development to get an understanding with the customer on the importance they place on the delivery of each functional requirement. It originated as part of the Dynamic Systems Development Method. Sometimes called a MoSCoW list or a MOSCOW Analysis. MoSCoW stands for:
M - MUST have this.
S - SHOULD have this if at all possible.
C - COULD have this if it does not affect anything else.
W - WON'T have this time but WOULD like in the future.

(Source wikipedia)

Just to confirm, a must priority is a showstopper, a project failure if not executed.

Anything labelled as “MUST” has to be included in the project delivery timebox in order for it to be a success. If even one “MUST” item is not included, the project delivery is considered a failure. “MUST” is also an acronym for the Minimum Usable SubseT” from wikipedia.

To put this in context if we take one of the items, RSS feeds, its reading if BCC cannot offer RSS feeds of community users’ blogs, you view the project will have failed.

The MoSCoW prioritisation process is to weight the requirments to assist in executing the project. It would be great if we could have a chat and go through these. Mainly need to get a bit more balance across the prioritisation.

(source - wikipedia and someone I work with)

No comments: