As a group, we were given a project prioritisation proposal document to fill out and complete. This documents purpose is to define the project deliverables for the given assignment, using the MoSCoW project prioritisation technique. Lawrence and myself filled in and completed this and then I myself forwarded the document on to our Course Director Simon Perkins.
Below is the filled in copy of our project prioritisation proposal:
Prior to completing this, I undertook key research on the MoSCoW method, to better understand its use, purpose and effectiveness.
What is the MoSCoW Method?
The MoSCoW method stands for Must, Could, Should & Would.
- M – Must have this requirement to meet the business needs.
- S – Should have this requirement if possible, but project success does not rely on it.
- C – Could have this requirement if it does not affect anything else in the project.
- W – Would like to have this requirement later, but it won’t be delivered this time.
The O’s in MoSCoW are added to make the acronym pronounceable, and are often left in lowercase to show they don’t stand for anything. MoSCoW as a prioritisation method is used to decide which requirements must be completed first and which must come later or will not be completed at all. The must requirements are non-negotiable and have to be delivered. Failure to deliver even one of the must requirements will likely mean the project has failed. The project team should aim to deliver as many of the should requirements as possible. Could and would requirements are ‘nice to have’ and do not affect the overall success of the project. Could requirements are the first to go if the project timeline or budget comes under pressure.
In relation to the proposed assignment, the set deliverables raised by our group will be utilised in the prioritisation of tasks for the project, allowing for efficiency and effective time management.
Haughey, D., 2014. MoSCoW Method. Project Smart. Available from: http://projectsmart.co.uk/moscow-method.php [Accessed 19 March 2015].