GROUP OR INDIVIDUAL TASK
The MoSCoW Method is a technique from business analysis and project management used in video games production to prioritise what features will be and won't be included in the final game build.
- M - MUST HAVES: Describes a requirement that must be satisfied so that the final project can be considered a success.
- S - SHOULD HAVES: 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 HAVES: Describes a requirement which is considered desirable but not necessary. This will be included if time and resources permit.
- W - WOULD HAVES: Represents a requirement that you have agreed will not be implemented in the current release, but may be considered for the future.
Create a MoSCoW Method sheet outlining all the possible and potential functionality you will need to implement to make your game work:
e.g., parallax scrolling background, double jump mechanic, original soundtrack, menu buttons, timer, power up icons, etc.
Each function needs to be prioritised into one of the four categories, Must Haves, Should Haves, Could Haves, and Would Haves depending on how crucial it is to the success of the final game. For example, in a platformer, a working jump mechanic is a Must Have while movable platforms might be considered a Should Have.