Analyse, Prioritise and Assure the Quality of Requirements (20%)

Question 1

Relationship between requirements and solutions

Answer 1

Solutions define how the requirements will be met
Requirements should be solution agnostic

Question 2

Business rules categories

Answer 2

1. Constraints
   - Action Governance (internal/external)
   - Data Constraints
2. Operational Guidance
   - Decision Conditions
   - Calculations

Question 3

Example of Constraints

Answer 3

Action Governance:
Internal: only managers can improve invoices
External: we have to pay VAT on sales

Data Constraints:
You cannot place an order for a product that is out of stock

Question 4

Example of Operational Guidance

Answer 4

Decision Conditions:
Customers have 3 attempts to enter password

Calculations:
How to calculate overtime/tax/discount

Question 5

Example of Operational Guidance

Answer 5

Decision Conditions:
Customers have 3 attempts to enter password

Calculations:
How to calculate overtime/tax/discount

Question 6

What do constraints do?

Answer 6

Restrict how we perform

Question 7

What do operational guidance do?

Answer 7

Outline how we perform

Question 8

Quality Checklist

Answer 8

Clear
Concise
Consistent
Relevant
Unambiguous
Correct
Testable
Traceable

Question 9

Where should feasibility be considered?

Answer 9

Technical
Business
Financial

Question 10

When do testers get involved in the project?

Answer 10

Testing starts at project outset
Involve testers in reviews
Evaluates testability (or not) of requirements

Question 11

What should BA’s do if requirements overlap?

Answer 11

Overlapping requirements may mean they are not atomic
Separate out the individual, atomic requirements

Question 12

What should BA’s do if requirements are duplicated?

Answer 12

Remove any real duplication and/or establish how requirements are linked
Delete one of them or merge them where each has useful information
Confirm with stakeholders

Question 13

How can conflict be managed?

Answer 13

Understand the differing views (perspectives) of the stakeholders in conflict

Facilitate discussion to find a compromise position

Be prepared to escalate but understand the consequences (i.e. sponsor decided)

Question 14

How should requirements be structured?

Answer 14

User (or user role)
Verb phrase
Object or Noun phrase
For example:
The Receptionist shall be able to view all outstanding invoices by date

If using user stories: who/what/why

Question 15

Why is prioritisation important?

Answer 15

It allows the staging of requirement implementation
It enables the management of user expectations

Question 16

MoSCoW

Answer 16

MUST -Mandatory in the first increment; cannot meet objectives without it

SHOULD -Mandatory but may wait until second increment; the system will have short-term value without it

COULD - Beneficial if time or funds allow, but not central to project objectives

WANT - Will not be met in this delivery; may be included in a future delivery

Question 17

What does it mean to ‘slice’ requirements

Answer 17

Slice = sections of requirements to be completed

• Focus on those with highest priority (leave others until later)
• Slice requirements themselves (happy path may take priority)