Requirements Management

Question 1

Requirements need to satisfy the ?

Answer 1

Objectives of the project and should be quantitative or qualitative

Question 2

Requirements need to link very clearly with the ?

Answer 2

Benefits of the project

Question 3

The APM Defined requirement management as :

Answer 3

The process of capturing, assessing and justifying stakeholders wants and needs.

Question 4

For the project manager and their team to be able to establish the scope of the project there must first be

Answer 4

A set of requirements to work from

Question 5

Before we can begin to understand our requirements we initially need to establish the

Answer 5

Projects objectives which must be quantitative or qualitative and achieved by our project alone

Question 6

Once we’ve determined what our project is aiming to achieve with its objective, we will need to engage with our ________ to understand what they _____from the project. This will help us to start developing our high-level _________. These stakeholder _______ are known as requirements.

Answer 6

Stakeholders
Need
Scope
Needs

Question 7

Requirement should be _________ meaning they are free from providing a solution to the problem and are focused on what is needed rather than how it’s achieved.

Answer 7

Solution agnostic

Question 8

A high-level version of our requirements is usually presented in the business case during the ________ phase , that set of requirements is likely going to be developed further with more detail added as the the _________ progresses , this means our ________ will also need to develop alongside our requirements as well

Answer 8

Concept
Lifecycle
Acceptance criteria

Question 9

Is it incredibly important that requirements are ________ and ______ but expressed _________ as we can and as completely as we can.

Answer 9

Mature and robust
Simply as we can and completely as we can

Question 10

The acceptance criteria we use to prove to our stakeholders that we have achieved our requirements must be …

Answer 10

Clearly defined and documented

Question 11

The first in a requirements management process is to gather the requirements:

Answer 11

Requirements should be gathered from a wide range of stakeholder internal and external.

They can come from users , managers , sponsors but externally could be things like legislative or regulatory requirements.

Question 12

The approaches used to gather requirements:

Answer 12

• brainstorming
• interviews
• surveys and questionnaires
• workshops
• focus groups
• reviewing legislations
• simulations

Question 13

The second step is analyse the requirements gathered :

Answer 13

Each individual requirements should only address one core need , this should be relevant and current to best reflect the business needs.

Question 14

Analysing requirements: we need to ensure that when looking at the gathered requirements they do not ;

Answer 14

Contradict on another and are consistent. As the requirements are gathered from a range of stakeholders they needs may not be compatible with one another so we need to identify and resolve any of these ‘conflicting requirements’

Question 15

Analysing requirements: should there be any conflicting requirements that the project manager cannot resolve then the ?

Answer 15

Sponsor will need to provide direction

Question 16

Analysing requirements : whilst analysing requirements we should begin collecting them tighter to form a

Answer 16

Database that will support a comparison of each requirement to understand the ‘whole set’ and to facilitate the detailed analysis we should be doing for each requirement .

Question 17

The third step is to justify the requirement :

Answer 17

In order to help demonstrate the value of the identified requirements, it is important to identify what they benefits it satisfying the requirement will be to the business and to the stakeholders.

Part of this will be to try and understand the porky cost ( this may be challenging as requirements provide the needs to be fulfilled, not the solution)

Question 18

The purpose of justifying the requirement is to demonstrate what value they will bring to the project and to ________ what we have done already in the gather and analyse step so that we can that any conflicting requirements have been ________ and similar requirements are grouped together and that they are relevant and align to the business _______

Answer 18

Consolidate
Strategy

Question 19

The fourth and final step is to baseline the requirements :

Answer 19

Once we are satirised that we have gathered our requirements, analysed them in detail and justified why they are needed to our stakeholders we can baseline them.

Question 20

Baseline requirements : to baseline requirements will mean that they are now ______ and can be tracked and monitored throughout the project without them randomly changing or altering.

Answer 20

Fixed

Question 21

Baseline requirements: typically the _____ will be the one responsible for authorising the requirements so that they can be baselined.

Answer 21

Sponsor

Question 22

Baseline the requirements : to amend or alter any requirements we need to get those changes _____ and _____ at the appropriate level. This will help give space for our requirements to be _______ as we progress through the lifecycle but we will help to avoid unnecessary changes to them as any change will be assessed and recorded before a decision is made.

Answer 22

Assessed and approved.
Refined

Question 23

Baseline the requirements: part of baselining the requirements will also ensure that we understand how we will prove that the requirement has been ______ and what will our method of testing be. This will potentially require time and resources to do effectively so will need to be considered as early as possible , as further into the lifecycle our stakeholders will want proof that their requirements are being achieved.

Answer 23

Achieved

Question 24

MoSCoW - ideally want it to be possible to delivery every requirement that is wanted without the constraints of _____ or ____. However this is unlikely to be realistic and it is likely we are going to need to understand which requirements are a priority for our stakeholders and rank then in some order of importance

Answer 24

Budget or time

Question 25

Must have: without these being satisfied the business case will not be achieved these are requirements that if not delivered would mean the project would be considered a _________ and therefore should be met. They could me requirements legally required of us as well.

Answer 25

Failure

Question 26

Should haves: without these being satisfied, the business case will be weakened. Should haves are requirements that are considered important to a project success and not achieving them would mean the outputs, or benefits of the project are diminished to some extent although if push comes to shove we could ;

Answer 26

Scrape by without achieving these and still deliver (albeit weakened) the project

Question 27

Could haves: can include these if constraints allow as they may generate additional benefits. Could haves are requirements that the users _____ but the project could still be delivered satisfactorily without them. Could haves will potentially allow us to :

Answer 27

‘Want’

See additional benefits or opportunities that enhance the project in some way, provided we have the capacity to deliver them.

Question 28

Won’t haves: are not be included in the project scope (for the time being). If we understand what we won’t gave, this will help to define a much clearer _______ by telling us what is outside of scope. Knowing these won’t haves will help to minimise or avoid scope creep although if something changes we also know …

Answer 28

Scope

What is outside of scope that could be brought into scope

Question 29

Lifecycles: depending on the lifecycles we use there will be a different approach to how the requirements documents will develop. How mature the requirements are will typically differ between …

Answer 29

Projects that use a linear approach versus projects that use an iterative approach

Question 30

Requirements - lifecycle: linear lifecycle

Answer 30

For a linear lifecycle , the requirements as usually set and approved at the start of the project being gathers and refined during concept and definition before being baselined.

These requirements tend to be mature and detailed though the value gained from the requirements being achieved isn’t usually seen until the end of the project.

Question 31

Requirements - lifecycle: iterative lifecycle

Answer 31

Iterative approaches on the other hand will set some must have requirements at the beginning of the project that will need to be met but will then allow each iteration to develop or add to these requirements.

Because each iteration might provide an output, value is often gained throughout the lifecycle rather than at the very end.