Post on 04-Jul-2020
|
IIBA-session Requirements Engineering and Agile Artefacts Peter Nobels – Sogeti – Management Consultant Martijn van Domselaar – ABN AMRO - Sr. Business Analist 11 april 2017
|
Requirements Engineering and Agile Artefacts
2
1. Intro 2. System developement: two worlds and three perspectives 3. (Agile) Artefacts positioned 4. Requirements Engineering & Agile Artefacts 5 Recap
RQ’s engineering & Agile Artefacts
|
Requirements Engineering and Agile Artefacts
Business requirements
Stakeholder requirements
Solution requirements
Transition requirements
Functional requirement
Non-Functional
requirement
Interfaces
Use Cases
Decision Tables
Organisation Model
Requirements types
Specification & Modeling Techniques Perspectives
Business Intelligence
Business Process Management
RQ’s engineering & Agile Artefacts 3
Development Approach
Requirements Cookbook
Structured Requirements
set
3. Requirement attributes
4. Requirement category
1. Owner
8. Acceptance criterion
7. BAAS structure
6. Organising requirements
2. Elicitation
5. Requirement description
|
Requirements Engineering and Agile Artefacts
4
Objectives for the Requirements Cookbook
1. Guidelines, on a practioner level, for modeling and specifying requirements within an Agile way of working
2. Requirements for re-use (stay Agile)
3. Connect to artefacts of the enterprise & information model
RQ’s engineering & Agile Artefacts
|
Requirements Engineering and Agile Artefacts
5
1. Intro 2. System developement: two worlds and three perspectives 3. (Agile) Artefacts positioned 4. Requirements Engineering & Agile Artefacts
o Stakeholder Statement & Initial User Story o Value Streams o Epics & Business Objectives o Product Increments o Stakeholder Requirements & Acceptance criteria; Clusters o Solution Requirements o User Stories, Acceptance criteria & tasks
5 Recap
|
Business layer
Stakeholder &
Solution layer
Implementation independent System documentation
System & implementation dependent System documentation
Connect to the world of accountable parties
Connect to the world of stakeholders & developers
Change documentation
Accountable person Domain-x
Mandated Product Owner Domain-x
Stakeholders RQ’s engineering & Agile Artefacts
|
Change documentation
Business layer
Stakeholder &
Solution layer
Implementation independent System documentation
System & implementation dependent System documentation
Change perspective
Lifecycle perspective
Solution perspective
Enterprise model
Information model
RQ’s engineering & Agile Artefacts
|
To Be
As is
Change documentation Implementation independent System documentation
System & implementation dependent System documentation
Business Epic
User Story
User Story User Story
User Story User Story
User Story User Story
User Story User Story
User Story
User Story User Story
User Story User Story
User Story User Story
User Story User Story
User Story
User Story User Story
User Story User Story
User Story User Story
User Story User Story
User Story
System
Current State Insight
Overview Knowledge base
Consistency Re-use
RQ’s engineering & Agile Artefacts
|
Requirements Engineering and Agile Artefacts
9
1. Intro 2. System developement: two worlds and three perspectives 3. (Agile) Artefacts positioned 4. Requirements Engineering & Agile Artefacts
o Stakeholder Statement & Initial User Story o Value Streams o Business Epics & Business Objectives o Product Increments o Stakeholder Requirements & Acceptance criteria; Clusters o Solution Requirements o User Stories, Acceptance criteria & tasks
5. Recap
|
Business Objective
Solution RQ (specification
document)
Stakeholder requirement
System
Design Cluster (feature, object, output,
function, …)
Business Capability
Business Epic; Product
Increments
User Story
Stakeholder Statement
Value Stream
Change documentation
Business layer
Stakeholder &
Solution layer
Implementation independent System documentation
System & implementation dependent System documentation
= Agile Artefacts RQ’s engineering & Agile Artefacts
|
Requirements Engineering and Agile Artefacts
11
1. Intro 2. System developement: two worlds and three perspectives 3. (Agile) Artefacts positioned 4. Requirements Engineering & Agile Artefacts
o Stakeholder Statement & Initial User Story o Value Streams o Business Epics & Business Objectives o Product Increments o Stakeholder Requirements & Acceptance criteria; Clusters o Solution Requirements o User Stories, Acceptance criteria & tasks
5 Recap
| Sogeti PowerPoint Referentie 2014
User Story-3
User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
User Story-2 Scrum team-1
Mandated Product Owner Domain-A
User Story As responsible person for the DNB reporting
I want less incidents during reporting to the DNB
So we can better fulfil our compliancy obligations
User Story Clusters
Stakeholder & solution RQ
Business Epic; Product
Increments
Bus Objective Value Stream Bus Capability
Design
Stakeholder Statement
User Story-1
RQ’s engineering & Agile Artefacts
|
Requirements Engineering and Agile Artefacts
13
1. Intro 2. System developement: two worlds and three perspectives 3. (Agile) Artefacts positioned 4. Requirements Engineering & Agile Artefacts
o Initial User Story & Stakeholder Statement o Value Streams o Epics & Business Objectives o Product Increments o Stakeholder Requirements & Acceptance criteria; Clusters o Solution Requirements o User Stories, Acceptance criteria & tasks
5. Recap RQ’s engineering & Agile Artefacts
|
Value stream ‘X’ Value stream ‘Reporting to DNB’
Receive Dataset-B on request
Dataset-B
Domain-R (Business
Capability)
Receive Dataset-A on request
Dataset-A
Domain-M (Business
Capability)
Domain-A (Business
Capability)
Mandated Product Owner Domain-A
Receive Report
DNB
Report
Customer info-N
Domain-O (Business
Capability) Business Process-n
Customer
As responsible person for the DNB reporting
I want less incidents during reporting to the DNB
So we can better fulfil our compliancy obligations
Reporting to the DNB: value stream(s) User Story
Clusters Stakeholder &
solution RQ
Business Epic; Product
Increments
Bus Objective Value Stream Bus Capability
Design
|
Receive Dataset-A on request
Dataset-A
Receive Dataset-B on request
Dataset-B
Domain-A
Mandated Product Owner Domain-A
Receive Report
DNB
Report
Domain-M
Domain-R Domain-O
Customer info-N
Business Process-n
Customer
Within 24 hours
Data Quality
Up to date
Comple- teness
As responsible person for the DNB reporting
I want less incidents during reporting to the DNB
So we can better fulfil our compliancy obligations
Reporting to the DNB: problems in value streams
RQ’s engineering & Agile Artefacts
|
Receive Dataset-A on request
Dataset-A
Receive Dataset-B on request
Domain-A
Accountable person Domain-A
Receive Report
DNB
Report
Domain-M
Dataset-B
Domain-R Domain-O
Customer info-N
Business Process-n
Customer
Accountable person Domain-O
Within 24 hours
Data Quality
Up to date
Comple- teness
Accountable person Domain-R
Accountable person Domain-M
As responsible person for the DNB reporting
I want less incidents during reporting to the DNB
So we can better fulfil our compliancy obligations
Reporting to the DNB: accountabilities in value streams
RQ’s engineering & Agile Artefacts
| 17
User Story-3
User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
User Story-1 User Story-2 Scrum
team-1 User Story-3
User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
User Story-1 User Story-2 Scrum
team-2
Mandated Product Owner Domain-A
User Story-3
User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
User Story-1 User Story-2 Scrum
team-n Scrum team-3
User Story-3
User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
User Story-1 User Story-2
Mandated Product Owner Domain-M
Mandated Product Owner Domain-R
Mandated Product Owner Domain-O
Within 24 hours
Data Quality
Up to date
Comple- teness
|
Requirements Engineering and Agile Artefacts
18
1. Intro 2. System developement: two worlds and three perspectives 3. (Agile) Artefacts positioned 4. Requirements Engineering & Agile Artefacts
o Initial User Story & Stakeholder Statement o Value Streams o Buiness Epics & Business Objectives o Product Increments o Stakeholder Requirements & Acceptance criteria; Clusters o Solution Requirements o User Stories, Acceptance criteria & tasks
5. Recap
| Sogeti PowerPoint Referentie 2014 19
User Story Clusters;
Stakeholder & solution RQ
Business Epic; Product
Increments
Bus Objective Value Stream Bus Capability
Design
Business Epic-x As accountable person for the DNB reporting
I want to comply better to the (new) DNB-regulations
So we can keep our banking licence
Accountable person Domain-A
Business Objective
Mandated Product Owner Domain-A
User Story As responsible person for the DNB reporting
I want less incidents during reporting to the DNB
So we can better fulfil our compliancy obligations
Business Epic-3
Business Epic-6
Business Epic-4 Business Epic-5
Business Epic-7 Business Epic-8 Business Epic-9
Business Epic-2 Business Epic-x
RQ’s engineering & Agile Artefacts
|
Requirements Engineering and Agile Artefacts
20
1. Intro 2. System developement: two worlds and three perspectives 3. (Agile) Artefacts positioned 4. Requirements Engineering & Agile Artefacts
o Initial User Story & Stakeholder Statement o Value Streams o Buiness Epics & Business Objectives o Product Increments o Stakeholder Requirements & Acceptance criteria; Clusters o Solution Requirements o User Stories, & tasks
5. Recap
|
Program layer
Team Layer
21
User Story-3
User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
User Story-1 User Story-2 Scrum
team-1
Mandated Product Owner Domain-A
Value Stream ‘Reporting to DNB’
Within 24 hours
Value Stream ‘X’
Recieve Dataset-A on request
Recieve Dataset-B on request
Domain-A
Recieve Report
DNB Domain-M
Domain-R
Customer info-N
Domain-O
Customer info-N
Business Process-n
Customer
Product Increment-3 …
Product Increment-x …
User Story-3
User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
User Story-1 User Story-2 Scrum
team-2
Mandated Product Owner Domain-M
Scrum team-3
User Story-3
User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
User Story-1 User Story-2
Mandated Product Owner Domain-R
User Story-3
User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
User Story-1 User Story-2 Scrum
team-4
Mandated Product Owner Domain-O
Product Increment-1 Improve reporting regarding to data (quality, completeness, up to date)
Data Quality
Up to date
Comple- teness
Product Increment-2 Improve reporting regarding to SLA
(within 24 hours)
|
Requirements Engineering and Agile Artefacts
22
1. Intro 2. System developement: two worlds and three perspectives 3. (Agile) Artefacts positioned 4. Requirements Engineering & Agile Artefacts
o Initial User Story & Stakeholder Statement o Value Streams o Buiness Epics & Business Objectives o Product Increments o Stakeholder Requirements & Acceptance Criteria; Clusters o Solution Requirements o User Stories, Acceptance criteria & tasks
5. Recap
|
Value stream ‘X’
23
User Story-3
User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
User Story-1 User Story-2 Scrum
team-n
Mandated Product Owner Domain-O
Comple- teness
User Story Clusters;
Stakeholder & solution RQ
Business Epic; Product
Increments
Bus Objective Value Stream Bus Capability
Design
Value stream ‘Reporting to DNB’
Receive Dataset-B on request
Dataset-B
Domain-R (Business
Capability)
Receive Dataset-A on request
Dataset-A
Domain-M (Business
Capability)
Domain-A (Business
Capability)
Mandated Product Owner Domain-A
Receive Report
DNB
Report
Customer info-N
As responsible person for the DNB reporting
I want less incidents during reporting to the DNB
So we can better fulfil our compliancy obligations
Customer info-N
Domain-O (Business
Capability) Business Process-n
Customer
Cluster (group of RQ’s related to subject) = ‘Register Customer Info’
|
Stakeholder Requirement As responsible person for Customer info
I want the system to store the [customer data] entered1) by the customer
So we have his/her up to date information available 1) changed or new
Stakeholder Requirement As responsible person for Customer info
I want the system to store the [customer data] entered1) by the customer
So we have his/her up to date information available 1) changed or new
User Story Clusters;
Stakeholder & solution RQ
Business Epic; Product
Increments
Bus Objective Value Stream Bus Capability
Design
Stakeholder Requirement As responsible person for Customer info
I want the system to show the customer the [customer data] we already know So we don’t annoy him with unnecessary questions and we
give him the possibility to update his/her data
24
User Story-3
User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
User Story-1 User Story-2 Scrum
team-n
Mandated Product Owner Domain-O
Value stream ‘X’ Domain-O (Business
Capability) Business Process-n
Customer
Customer info-N
‘Register Customer Info’
[customer data] Name* Adress*
ZIP-code*) & City* LEI*2) ( = Legal Entity Identifier)
*) = Mandatory 2) New RQ, needed for DNB-reporting
|
User Story Clusters;
Stakeholder & solution RQ
Business Epic; Product
Increments
Bus Objective Value Stream Bus Capability
Design
Stakeholder Requirement As responsible person for Customer info
I want the system to show the customer the [customer data] we already know So we don’t annoy him with unnecessary questions and we
give him the possibility to update his/her data
25
User Story-3
User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
User Story-1 User Story-2 Scrum
team-n
Mandated Product Owner Domain-O
Value stream ‘X’ Domain-O (Business
Capability) Business Process-n
Customer
Customer info-N
RQ’s Acceptance Criteria As responsible person for Customer info
I accept the solution regarding to this RQ when It’s clear to the customer which data is mandatory
RQ’s Acceptance Criteria As responsible person for Customer info
I accept the solution regarding to this RQ when It’s clear to the customer that (s)he has the
possibility to change the value of pre-filled fields
‘Register Customer Info’
|
Requirements Engineering and Agile Artefacts
26
1. Intro 2. System developement: two worlds and three perspectives 3. (Agile) Artefacts positioned 4. Requirements Engineering & Agile Artefacts
o Initial User Story & Stakeholder Statement o Value Streams o Buiness Epics & Business Objectives o Product Increments o Stakeholder Requirements & Acceptance criteria; Clusters o Solution Requirements o User Stories, Acceptance criteria & tasks
5. Recap
|
User Story Clusters;
Stakeholder & solution RQ
Business Epic; Product
Increments
Bus Objective Value Stream Bus Capability
Design
27
User Story-3
User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
User Story-1 User Story-2 Scrum
team-n
Mandated Product Owner Domain-O
Value stream ‘X’ Domain-O (Business
Capability) Business Process-n
Customer
Customer info-N
Solution Requirement (Specification document; type Use Case’)
Reset password
Activ ate accountComplete account
Create customeraccount
Register Customer
Customer Shop Worker
<<include>>
<<include>> <<include>>
<<include>>
‘Register Customer Info’
|
Requirements Engineering and Agile Artefacts
28
1. Intro 2. System developement: two worlds and three perspectives 3. (Agile) Artefacts positioned 4. Requirements Engineering & Agile Artefacts
o Initial User Story & Stakeholder Statement o Value Streams o Buiness Epics & Business Objectives o Product Increments o Stakeholder Requirements & Acceptance criteria; Clusters o Solution Requirements o User Stories, Acceptance criteria & tasks
5. Recap
|
User Story-2 As responsible person for Customer info
I want the system to show the customer the [customer data] we already know
conform the acceptance criteria (= mandatory/change prefilled) So we increase the change of capturing mandatory and
changed [customer data]
User Story-2
User Story-2 As responsible person for Customer info
I want the system to show the customer the [customer data] we already know
conform the acceptance criteria (= mandatory/change prefilled) So we increase the change of capturing mandatory and
changed [customer data]
User Story-2
User Story Clusters;
Stakeholder & solution RQ
Business Epic; Product
Increments
Bus Objective Value Stream Bus Capability
Design
29 User Story-6
User Story-4 User Story-5
User Story-7 User Story-8 User Story-9
Scrum team-n
Mandated Product Owner Domain-O
Value stream ‘X’ Domain-O (Business
Capability) Business Process-n
Customer
Customer info-N
User Story-1 As responsible person for Customer info
I want the system to show the customer the [customer data] we already know
So we don’t annoy him with unnecessary questions and we give him the possibility to update his/her data
User Story-1 User Story-3 As responsible person for Customer info
I want the system to store the [customer data] entered1) by the customer
So we have his/her up to date information available 1) changed or new
User Story-3
‘Register Customer Info’
|
Requirements Engineering and Agile Artefacts
30
1. Intro 2. System developement: two worlds and three perspectives 3. (Agile) Artefacts positioned 5. Requirements Engineering & Agile Artefacts
o Initial User Story & Stakeholder Statement o Value Streams o Buiness Epics & Business Objectives o Product Increments o Stakeholder Rrequirements & Acceptance criteria; Clusters o Solution Requirements o User Stories, Acceptance criteria & tasks
5. Recap
|
Cluster (feature, object, output,
function, …)
Stakeholder requirement
System
Design
Solution RQ (specification
document)
Business Epic; Product
Increments
Change documentation
Business layer
Stakeholder &
Solution layer
Implementation independent System documentation
System & implementation dependent System documentation
Initial User Story User Story
Business Objective
Business Capability Value Stream
Stakeholder Statement
JIRA
JIRA
RMSIS
Confluence
|
How does this help – Your team?
Doing the right Thing, and doing things right.
Enabling the PO to prioritise on backlog items
Be Agile & stay agile, by managing your information
Enabling focus on the change, not on reverse engineering
Relate changes to their value streams
Defining Product Increments
RQ’s engineering & Agile Artefacts 32
|
How does this help – You?
Quick turnaround on impact analysis
Enable quick time to market
Supports refinement & estimation
RQ’s engineering & Agile Artefacts 33
|
How does this help – Your organisation?
By using the same language, increase effectiveness of team cooperation
Enabling compliancy on Audit points & control objectives
Support quick onboarding of new team members, employability
Pave the way for future developments (DevOps)
RQ’s engineering & Agile Artefacts 34
|
Implementation independent System documentation
Agile artefacts & RQ’s - perpetually linked
35
Specs & designs
Current state / Enterprise & information model
Change/Sprint
Check out
Check in New & updated
Change documentation