1. Home
  2. Training Library
  3. Requirements Management - Overview | PMQ D4.1a

Requirements Management - Overview | PMQ D4.1a

Developed with
QA

Contents

keyboard_tab
QA | APM PMQ | Digital
play-arrow
Requirements Management - Overview | PMQ D4.1a
Overview
DifficultyBeginner
Duration5m
Students11

Description

This video explains what requirements are, and how to make the most out of your requirements management.

Transcript

- For projects to deliver the outputs and ultimately the benefits they aim to achieve, they need to have clearly defined requirements which in turn means requirements management. Requirements are the stakeholders' wants and needs clearly defined with acceptance criteria. And requirement management is the process of capturing assessing, and justifying stakeholders' wants and needs. In this video, we'll go through everything you need to know to get the most out of your own requirements management. The objectives and needs of a project often come from the strategic aims of a program or portfolio. In the case of a standalone project, the objective should relate directly to a strategic objective. Whatever kind of project you're working on, you always need to make sure that there's a clear link between benefits, success criteria, objectives, and requirements. And it's also your job to make sure that these requirements are clear and easy to understand. One way you can do this is to use the smart process which makes sure you can express requirements as specific, measurable, achievable, relevant and time based. Requirements should also be uniquely identifiable, current and up to date, consistent, understandable verifiable, traceable and prioritized. To prioritize requirements, you use the MoSCoW method. Must have, should have, could have, and won't have. Requirements can also be functional or nonfunctional. Functional requirements state exactly what the system should do in any kind of situation. These are things like inputs, outputs and behaviors. Nonfunctional requirements are about the attributes the system should have and tend to be things like usability or reliability. Whatever your requirements are, you need to be able to define them so that you can design and test your evaluation criteria to figure out if the outputs worked as intended. Great, now let's move on to the importance of requirements management itself. There are two things for you to remember when it comes to requirements management. Firstly, that it is fundamental for your project success. And secondly, that users are key stakeholders when it comes to laying out requirements. So you need to engage with them and manage them carefully. Requirements impact the scope, quality and change control of any project. The scope of the project is determined by the requirements. You'll also need to understand the business need to help you define the requirements as this will impact the quality expectations for the requirements. Finally, any change to the project scope will also impact the project requirements, and you'll need to prepare for this as much as possible during the change control and impact analysis. If you don't involve your users in specifying requirements, your project is probably going to deliver something that they don't want. Not engaging users when you start out can cause a few different problems for you further down the line. Firstly, it's expensive and time consuming to fix or re-implement requirements that weren't specified. Secondly, it could mean that your project doesn't realize its benefits. Last but not least, it could cause considerable damage to your organization's corporate image and reputation. You can avoid all of these issues by simply asking them exactly what they want before you start design and development. Finally, for this video let's go through what a typical four-step requirement's management process is. First, you need to gather information. This involves capturing and documenting requirements through things like interviews or focus groups. Next, you need to analyze each of the captured requirements to work out their value, ie the cost of achieving it versus the benefits you expect. Again, a process like MoSCoW is great for this. After this, you need to justify the requirements to all of your key stakeholders by presenting them in a clear and concise document and gaining their buy-in. Finally, you need to create a baseline for requirements so that they become subject to a formal change control process. And that's it for this video. Project start with requirements. So an understanding of how to create and manage them will be central to your role and your project finding success.