6584081905

MoSCoW Method From Wikipedia, the free encyclopedia Jump to: navigation, search For other uses, see Moscow (disambiguation). Contents 1 Background 2 Prioritisation of MoSCoW requirements 3 Sources 4 References 5 See also MoSCoW is a prioritisation technique used in business analysis and software development to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement - also known as MoSCoW prioritisation or MoSCoW analysis.

According to A Guide to the Business Analysis Body of Knowledge, version 2.0[1],facts about lion, section 6.1.5.2,lion.com, the MoSCoW categories are as follows: M - MUST: Describes a requirement that must be satisfied in the final solution hogan 92 for the solution to be considered a success. S - SHOULD: Represents a high-priority item that should be included in the solution if it is possible. This is often a critical requirement but one which can be satisfied in other ways if strictly necessary. C - COULD: Describes a requirement which is considered desirable but not necessary. This will be included if time and resources permit. W - WON'T: Represents a requirement that stakeholders have agreed will not be implemented in a given release, but may be considered for the future. The o's in MoSCoW are added simply to make the word pronounceable, and are often left lower case to indicate that they don't stand for anything. MOSCOW is an acceptable variant,old world monkeys, with the 'o's in upper case.

[edit] Background

This use of MoSCoW was first developed by Dai Clegg of Oracle UK Consulting; in CASE Method Fast-Track: A RAD Approach [2][3]; although he subsequently donated the Intellectual Property Rights to the Dynamic Systems Development Method (DSDM) Consortium.

MoSCoW is often used with timeboxing, where a deadline is fixed so that the focus can be on the most important requirements, and as such is seen as a core aspect of rapid application development (RAD) software development processes, such as Dynamic Systems Development Method (DSDM) and agile software development techniques.

[edit] Prioritisation of MoSCoW requirements

All requirements are important,monkey gems, but they are prioritised to deliver the greatest and most immediate business benefits early. Developers will initially try to deliver all the M, S and C requirements but the S and C requirements will be the first to go if the delivery timescale looks threatened.

The plain English meaning of the MoSCoW words has value 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. Must have requirements labeled as MUST are critical to project success and have to be included in the current delivery timebox in order for it to be a success. If even one MUST requirement is not included, the project delivery should be considered a failure (note: requirements can be downgraded from MUST, by agreement with all relevant stakeholders; for example, when new requirements are deemed more important). MUST can also be considered a backronym for the Minimum Usable louis vuitton 2013 SubseT. Should have SHOULD requirements are important to project success,speak dictionary, but are not necessary for delivery in the current delivery timebox. SHOULD requirements are as important as MUST, although SHOULD requirements are often not as time-critical or have workarounds, allowing another way of satisfying the requirement, so can be held back until a future delivery timebox. Could have requirements labeled as COULD are less critical and often seen as nice to have. A few easily satisfied COULD requirements in a delivery can ralph lauren 183 increase customer satisfaction for little development cost. Won't have (but Would like) WON'T requirements are ralph lauren 178 either the least-critical,lion cub wallpaper, lowest-payback items,types of monkeys, or not appropriate at that time. As a result, WON'T requirements are not planned into the ralph lauren 27 schedule for the delivery timebox. WON'T requirements are either dropped or reconsidered for inclusion in later timeboxes. This, however doesn't make them any less important. Sometimes this is described as "Would have", as this is less definitive and leaves the option open to add these requirements to the scope of the delivery if the scope, budget or time (known as the project triangle) changes. [edit] Sources Coley Consulting on MoSCoW [edit] References ^ A Guide to the Business Analysis Body of Knowledge. International Institute of Business Analysis. 2009. ISBN?978-0-9811292-1-1.? ^ Clegg,facts on lions, Dai; Barker, Richard (2004-11-09). Case Method Fast-Track: A RAD Approach. Addison-Wesley. ISBN?978-0-201-62432-8.? ^ Tierstein,tiger games, L.M. (1997). "Managing a Designer/2000 Project" (PDF). Fall '97. New York Oracle User Group. http://www.wrsystems.com/whitepapers/managedes2k.pdf. Retrieved 2008-05-31.? [edit] See also RFC 2119 (Requirement Levels) louis vuitton 1991 This RFC defines requirement levels to be used in formal documentation. It is commonly used in contracts hogan 125 and other legal documentation. Noted here as the wording is similar but not necessarily the meaning. Retrieved from "http://en.wikipedia.org/w/index.php?title=MoSCoW_Method&oldid=494907605" Categories: Software project managementDynamic systems development methodComputer jargon Personal tools Create account Log in Namespaces Article Talk Variants Views Read Edit View history Actions Search Navigation Main page Contents Featured content Current events Random article Donate to Wikipedia Interaction Help About Wikipedia Community portal Recent changes Contact Wikipedia Toolbox What links here Related changes Upload file Special pages Permanent link Cite this page Print/export Create a bookDownload as PDFPrintable version Languages Deutsch Fran?ais Nederlands ������ܧڧ� This page was last modified on 29 May ralph lauren 167 2012 at 06:42. Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. See Terms of use for details.

Wikipedia is a registered trademark of the Wikimedia Foundation,monkey go happy2, Inc., a non-profit organization. Contact us Privacy policy About Wikipedia Disclaimers Mobile view Related articles��

speak with|learn english speaking|habitat of lion

monkey games|ecards for christmas|crazy monkey

lion habitat|lion habitat|creative christmas gifts