Producing a Prioritised Requirements List

When starting out on a new Umbraco Project it’s really important to know and communicate your requirements and your desired features.

There are many ways of communicating these, but here at Carbon Six Digital, we use a spreadsheet called the Prioritised Requirements and Traceability Matrix. Long name, but easy idea.

First the requirements list. This is a methodical list of all the features the new system must incorporate alongside other factors, known as non-functional requirements, such as security and performance requirements. The functional requirements are often best articulated as a “User Story”.

The list should be Prioritised so that the developers focus attention on those features and requirements that are most important. For Agile Projects where the feature list flexes but the budget is fixed - prioritisation is critical to ensure that the budget is spent only on those features that really matter. We tend to use the MoSCoW prioritisation mnemonic (Must have, Should have, Could have, and Won’t have) to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement.

It’s also useful to capture those requirements which are subsequently agreed as out of scope, so we record the conversation and rationale behind de-scoping the feature.

Once the Prioritised Requirements part of the document is complete you’re ready to commission the work to be built. This is where the Traceability Matrix becomes useful as a means of demonstrating control over the project and will be the subject of our next blog post.

Our Umbraco Design Review makes use of the Prioritised Requirements List and Traceability Matrix to ensure that your Umbraco solution is fit for business purpose.  So if you plan to deliver your next site in-house, then we can provide support during the design and build of the project for a low-fixed price.