Guidelines for discovering and managing requirements.

1. © Capiro 2014 Slide 1
8 Steps
to requirements success

2. © Capiro 2014 Slide 2
Introduction
The way you elicit and manage your
requirements gives them their credibility
Base your approach on your risks and context

3. © Capiro 2014 Slide 3
The Steps
Management
Context
Stakeholders
Discovery
Specification
Validation
Verification
Benefits

4. © Capiro 2014 Slide 4
Step 1 - Requirements Management
As simple as
possible
But no simpler
Identifiers – Version
control - Baselines
Establish an approach

5. © Capiro 2014 Slide 5
Step 2 – Establish Context
Requirements in Context

6. © Capiro 2014 Slide 6
Step 2 – Establish Context (more)
Understand the problem, …
before you create a “solution”

7. © Capiro 2014 Slide 7
Hands-on Users
Product
Work Domain
Client Managers and Supervisors
Interfacing
Product(s)
(Stakeholders?)
Interfacing work areas
(Stakeholders?)
Regulatory bodies
Standards bodies
Subject Matter Experts
Beneficiaries
Training
Sponsors
Project managers
Product managers
Governance bodies
Product
owner
Customers
Suppliers
Hands on Users
Security
Maintenance
Operators
Help Desk
Development
Team
Expert Users
Product Champion
Legal
Negative
Stakeholders
Step 3 – Stakeholders
Application Supplier
Management
Identify

8. © Capiro 2014 Slide 8
Step 3 - Stakeholders (more)
StakeholderPower
High
Watch Keep satisfied Active
management
Some
Keep onside
None
‘Ignore’ Keep informed
None Some High
Stakeholder Interest
Manage

9. © Capiro 2014 Slide 9
Business rules
Process
models
Data models
Goal models
Scribe
Facilitator
Projector,
screen and
whiteboard
Stationery,
Refreshments
Flip charts
Stakeholders
Step 4 – Requirements Discovery
Elicit, analyse, prioritise
Facilitated WorkshopContext
Subject matter experts
Requirements team
Developers
Testers

10. © Capiro 2014 Slide 10
Business Analyst + Product Owner + Project Manager
Developer / Designer / Architect / Tester
Can we build from requirements?
Are requirements testable?
Step 4 – Requirements Discovery (more)
Can we deliver a system from these requirements?

11. © Capiro 2014 Slide 11
Will it make the boat go faster ?
For each requirement, ask …
Will we need it?

12. © Capiro 2014 Slide 12
Read
the
book
Recommendation …

13. © Capiro 2014 Slide 13
Start simply
Evolve product
Reduce risks
Learn from
experience
Deliver value
Step 4 – Requirements Discovery (more)
Minimum Viable Product

14. © Capiro 2014 Slide 14
Step 5 - Select An Approach To Specification

15. © Capiro 2014 Slide 15
Step 5 - Select An Approach To Specification (more)
Understand
the business
and the
stakeholders
Understand
strategic
value and
associated
risks of
product
Keep
specification
approach as
lightweight
as possible
Select the
approach

16. © Capiro 2014 Slide 16
Step 6 – Requirements Validation
Is the customer happy?
Are we building the right system?

17. © Capiro 2014 Slide 17
Step 7 – Requirements Verification
Acceptance testing
Prove to this
guy that it
won’t break.

18. © Capiro 2014 Slide 18
• Test planning and design
Testing starts at
project outset
• Static testing
Involve testers
in peer reviews
Requirements
Discovery
Acceptance
Testing
Acceptance Criteria?
Testing
Step 7 – Requirements Verification (more)
Have we built the system right?

19. © Capiro 2014 Slide 19
Step 8 – Benefits Realisation
Did we deliver value?

20. © Capiro 2014 Slide 20
Capiro
www.capiro.co.uk
Business analysis – Business Architecture – Agile Requirements
For more information + 44 (0)1202 767 725
Consultancy
Team
Guidance
Team
Development
Team
Support
Training Interim Staff