Prioritising and Organisational Techniques

Qiao Ma (2009) explains that prioritising is based on the requirements needed in a project, but most of the time projects do not have unlimited resources, so “stakeholders need to decide which requirements should be implemented. Requirements prioritisation helps the project developers to select the final candidate requirements within resource constraints”. Therefore, for my project I am implementing the MoSCoW method to prioritise the requirements that are a necessity to the outcome, over the requirements that are not necessary. From this, I have then created a Gantt Chart to organise my time throughout the project, which not only prioritises requirements but also has a logical structure to make sure everything is done in the time.

MoSCoW Method:

The MOSCOW method is a prioritisation technique, used to display in a project what it MUST have, SHOULD have, COULD have and what it WON’T have. This is used to clearly understand the main elements that the project MUST have to succeed, as well as elements that will help it to succeed but not entirely necessary, and to explain things that the project definitely will not have. It helps a team or individual to “view of what is essential for launch and what is not” (Waters. K, 2009)

For my project, my prioritisation will be as follows:

MUST have:

  • Audience/user immersion
  • Music visualisation
  • Cylindrical projection
  • Music through headphones

SHOULD have:

  • Different music genres
  • Different visuals to suit different genres of music
  • Music edited to play in 360˚ around the listener

COULD have:

  • A way of users choosing their own song/genre
  • Option for complete 360˚ projection, rather than nearly 360˚ – leaving space for user to enter

WON’T have:

  • Space for multiple people – it will be for individual use at this stage
  • A screen interface for music choice

Gantt Chart:

I have created a Gantt Chart to help me organise my time for the project. It is divided into a week-by-week timetable, with various different sections that I will need to work on throughout the project, such as learning software and audio gathering.


As explained in my Iteration Process post, there will be various iterations to my work, which have been taken account for in the gantt chart – I will create a prototype that I will then test and gain feedback on; I will then work on my outcomes from this testing and feedback cycle until I am completely happy with the final project.


Ma, Q. (2010) The Effectiveness of Requirements Prioritization Techniques for a Medium to Large Number of Requirements: A Systematic Literature Review. Dissertation thesis. Auckland University of Technology. Available at: (Accessed: 3 December 2016).

Waters, K. (2009) Prioritization using MoSCoW AllAboutAgile. Available at: (Accessed: 30 November 2016).

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s