poker party

MoSCoW poker party is term used in software development and comes from the Dynamic Systems Development Method. Using MoSCoW Requirements analysis for a software delivery can be prioritized by the customer. MoSCoW stands for:

• M poker party - MUST have this.
• S - SHOULD have this if at all possible.
• C - COULD have this if it does not effect anything else.
• W - WONT have this time but WOULD like in the future.

The os in MoSCoW are added to make the word pronounceable, and are often left lower case to indicate that they dont stand for anything.The plain English meaning of

the MoSCoW words has value poker party in getting customers to understand what they are doing during prioritisation in a way that other ways of attaching priority, like high, medium and low, do not.Anything labeled as "MUST" has to be included poker party 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.While not critical to the success of the project delivery, "SHOULD"

items are nearly as important and should be included if it poker party is at all possible. "SHOULD" items are often as important as MUST items, however "SHOULD" items have workarounds allowing another way of satisfying the requirement."COULD" poker party items are less critical and often seen poker party as "nice to have". A few easily built Coulds in a delivery can increase customer satisfaction for little development cost "WONT" items are the least critical and poker party are not planned into the schedule for the current project. "WONT" items are either dropped or reconsidered for reprioritization

in later project increments. This, however doesnt make them any less important. All requirements poker party are important, but they are prioritized to deliver the greatest and most immediate business benefits early. Developers will try to deliver in all the M, S and C categories but the S and Cs will be the first to go if the delivey timescale looks threatened.CriticismSome poker party feel that by classifying a requirement as "nice to have" it make it no longer poker party a requirement, but more of a nicety. Therefore it no longer fits the scope of the requirements document.Sources poker party Coley Consulting on MoSCoWDSDMnl:MoSCoW-methode