Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Excerpt
hiddentrue

MoSCoW is a 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.

  • Must have

  • Should have

  • Could have

  • Won’t have

Contributed by Thomas Krause.

Image Added
Image Removed


Expand
titleA version of the "MoSCoW Method" board is also available in Comala Boards for Confluence Cloud
Canvas
board{"name":"MoSCoW Items","row":[{"column":[{"container":[{"key":"must","caption":"Must have","style":"s026","description":"Describes a requirement that must be satisfied in the final solution for the solution to be considered a success.","iconClass":"icon-smile"}]},{"container":[{"key":"should","caption":"Should have","style":"s025","description":"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.","iconClass":"icon-meh"}]},{"container":[{"key":"could","caption":"Could have","style":"s030","description":"Describes a requirement which is considered desirable but not necessary. This will be included if time and resources permit.","iconClass":"icon-pushpin"}]},{"container":[{"key":"wont","caption":"Won't have","style":"s029","description":"Represents a requirement that stakeholders have agreed will not be implemented in a given release, but may be considered for the future.","iconClass":"icon-frown"}]}]}]}
Info

For details of the Cloud app version of this board see