At work (and by my mum), I’m constantly being asked to explain the mysterious art of requirements management and why it’s so important. It seems like there’s a lot of confusion about this topic, so I’ve decided to write an article to help shed some light on the matter.

Requirements management (RM) is like the dark hidden magic that helps to ensure the success of a project by identifying and tracking the specific needs, wants, or expectations that must be met to achieve its goals. Just like a magician must know their spells and incantations to perform magic, a requirements manager must know and understand the requirements of a project to keep it on track and moving forward. Without effective requirements management, a project can flounder, just like a magic show without a skilled magician.

First things first: What are “Requirements”?

In project management, requirements are the things that a project needs to do or have in order to be successful. More specifically, there are two main types of requirements: functional and non-functional. Functional requirements are the features or actions that a project needs to have or do to achieve its goals. Non-functional requirements are the limits or rules that a project has to follow to be successful, like how well it works or how secure it is. Both types of requirements are important for making sure a project is a success.

Functional requirements tell us what a product or system should be able to do, but not how it should do it. For example, if we’re talking about a website, a functional requirement might be the ability for users to sign up, log in, and see their account info. Or, if we’re talking about a toaster, a functional requirement might be the ability to change the temperature and time settings to get the toast just right. These requirements help make sure that a project has all the necessary pieces to be successful.

Non-functional requirements instead describe how a product or system should work, rather than what it should do. For example, if we’re talking about a website, a non-functional requirement might be that it has to work for people with disabilities or be able to handle a certain number of users at the same time. Or, if we’re talking about a toaster, a non-functional requirement might be that it has to be able to withstand some wear and tear or not make too much smoke or noise. Non-functional requirements help make sure that a project works well and meets certain standards.

Functional and non-functional requirements are both important for the success of a project because functional requirements provide the necessary capabilities and features that allow a project to achieve its goals and non-functional requirements help ensure that the project meets certain standards and works well.

How does a Requirement Manager bring value to a project?

A requirements manager is a crucial part of making sure a project goes well. They make sure that all the necessary things the project needs are identified, written down, and tracked throughout the project. The requirements manager is in charge of telling the project team and other people involved what the project needs and making sure those things are understood and taken care of.

In addition to identifying and tracking requirements, the requirements manager also helps keep the project on track by figuring out which requirements are essential for the project to be successful and which ones are optional or not possible to include. They also make sure any changes to the requirements are carefully evaluated and managed to avoid any delays or extra costs.

Overall, hiring a great requirements manager can boost the chances of a project being a success by helping to make sure all the necessary requirements are identified and met, and that the project stays on track.

Tools and Software, an overview

The tools and software that a requirements manager uses most often will depend on the specific needs and goals of the project, as well as the preferences and experience of the requirements manager. Some popular tools and software that requirements managers may use include:

  1. Project management software: This type of software helps managers plan, organize, and track the progress of a project. Examples include JIRA, Asana, and Trello. 2. Requirements management software: This type of software helps teams capture, trace, analyze, and manage requirements. Examples include DOORS, CaliberRM, and ReqView. 3. Collaboration and communication tools: These tools help team members stay connected and communicate effectively, even when working remotely. Examples include Slack, Microsoft Teams, and Zoom. 4. Document management software: This type of software helps teams create, edit, and share documents and other files related to the project. Examples include Confluence, Google Docs, Microsoft Word, Microsoft Excel, and Adobe Acrobat. 5. Version control software: This type of software helps teams track changes to their code or other project assets and collaborate on code development. Examples include Git and Subversion.

  2. Scripting and automation tools: These tools help automate tasks and processes, such as testing or deployment, to save time and improve efficiency. Examples include Python, Bash, and Jenkins.

Clear signs that it’s time to think about RM

Here are a few clear signs that it might be time to hire a requirements manager for your project:

1. The project scope is unclear or constantly changing

If the requirements of your project are not well-defined or are constantly changing, it may be time to hire a requirements manager to help clarify and manage the scope of the project.

2. Requirements are not being properly documented or tracked

If you are having trouble keeping track of the requirements of your project, or if they are not being properly documented, it may be time to hire a requirements manager to help manage and track the requirements.

3. The project is experiencing delays or cost overruns

If your project is experiencing delays or unexpected cost overruns, it may be due to scope creep or other issues with the requirements. In this case, a requirements manager can help identify and resolve these issues to get the project back on track.

4. The project team is overwhelmed

If the project team is struggling to keep up with the demands of the project, it may be time to hire a requirements manager to help manage the workload and ensure that all the necessary requirements are being met.

5. The project is not meeting its goals

If the project is not meeting its goals or delivering the expected results, it may be due to issues with the requirements. A requirements manager can help identify and resolve these issues to help the project achieve its objectives.

In conclusion, requirements management is a crucial aspect of any project, but just as magic can be used for both good and evil, requirements management can be used to drive a project forward or hold it back. Ultimately, the key to successful requirements management is to approach it with discipline, clarity, and a focus on the end goal. By following a structured process, a requirement manager can ensure that all relevant requirements are captured and that the project delivers value to its stakeholders and users.