Requirements Gathering (MOSCOW and T-shirts)

Requirements gathering is a core activity in project management, ensuring that projects deliver outcomes that meet stakeholder needs and expectations. It provides the foundation for defining scope, planning work and maintaining control during delivery. Without clear requirements, projects risk confusion, delays and delivering outputs that do not meet these expectations.

At its simplest, requirements gathering addresses a key question: What does the project need to achieve? Requirements describe the features, functions and outcomes that stakeholders expect. These form the basis of the project’s scope, clearly setting out what is included and what is not. This clarity is essential for avoiding scope creep, where additional work is introduced without proper evaluation. (Wiegers & Beatty 2013)

Requirements gathering is not a discrete task completed at the start of the project. It is an ongoing process that includes identifying requirements, refining them, confirming them with stakeholders, and managing any changes. As projects progress, new information may emerge, and requirements may need to be updated. This requires a structured approach to ensure consistency and control. (Robertson & Robertson 2012)

The process typically begins with engaging stakeholders. Techniques such as interviews, workshops, surveys, and observation are used to understand their needs, priorities, and concerns. These approaches help capture both clearly stated requirements and those that may not be immediately obvious. Taking the time to gather requirements thoroughly reduces the risk of misunderstandings later. (BABOK 2015)

Once requirements have been identified, they need to be organised and prioritised. Not all requirements can be delivered within the available time and resources, so it is important to focus on what matters most. The MoSCoW method is commonly used for this purpose. It groups requirements into four categories:

Must have: essential for the project to succeed.

Should have: important, but not critical.

Could have: useful additions if time allows.

Won’t have: agreed as out of scope for now.

This method supports decision-making by helping stakeholders agree on priorities and understand trade-offs. It is particularly useful when expectations are high, as it creates a clear structure for managing competing demands. (Cohn 2004)

Alongside prioritisation, it is important to understand the effort required to deliver each requirement. T-shirt sizing is a simple technique used to estimate relative effort or complexity. Requirements are grouped into sizes such as XS, S, M, L, and XL based on how much work they are likely to involve. This is not a precise estimate, but it helps teams compare tasks quickly and plan more effectively. (Leffingwell 2011)

Using both MoSCoW and T-shirt sizing together allows project managers to balance importance and effort. For example, a requirement may be high priority but also large and complex, which may influence how it is scheduled or resourced. These techniques support realistic planning and help ensure that delivery remains achievable.

Requirements also play a key role in defining quality. They establish acceptance criteria, which specify what must be achieved for a deliverable to be considered complete. Clear requirements make it easier to assess whether outputs meet expectations and support quality assurance and control throughout the project.

Another important aspect of requirements management is handling change. Once requirements are agreed, they should be formally documented and treated as a baseline. If changes are needed, they should be assessed for their impact on time, cost and delivery. Managing changes in a structured way prevents confusion and helps maintain control.

Requirements are closely linked to other aspects of project management. They influence scheduling by defining the work that needs to be completed, affect cost through the effort required, and reduce risk by removing uncertainty. Maintaining a clear link between requirements, deliverables and outcomes helps ensure that the project stays aligned with its objectives.

In many modern projects, particularly those using Agile or hybrid approaches, requirements are managed continuously. They may be written as user stories and prioritised in a backlog, with regular reviews and updates. While the techniques may vary, the underlying principles remain consistent: clear, prioritised and well-managed requirements are essential for successful delivery.

In summary, requirements gathering provides the foundation for effective project management. By understanding stakeholder needs, prioritising effectively and using techniques such as MoSCoW and T-shirt sizing, project managers can improve planning, maintain control and deliver outcomes that meet expectations.