iiba-session requirements engineering and agile artefacts · iiba-session requirements engineering...

|

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

|


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

|


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


|


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

|


Business layer

Stakeholder &

Solution layer



Change perspective

Lifecycle perspective

Solution perspective

Enterprise model

Information model


|

To Be

As is

Change documentation Implementation independent System documentation


Business Epic

User Story

User Story User Story




User Story





User Story





User Story

System

Current State Insight

Overview Knowledge base

Consistency Re-use


|


9


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


Business layer

Stakeholder &

Solution layer



= Agile Artefacts RQ’s engineering & Agile Artefacts

|


11


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


Increments

Bus Objective Value Stream Bus Capability

Design


User Story-1


|


13


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)


Receive Report

DNB

Report

Customer info-N

Domain-O (Business

Capability) Business Process-n

Customer

As responsible person for the DNB reporting



Reporting to the DNB: value stream(s) User Story

Clusters Stakeholder &

solution RQ


Increments


Design

|


Dataset-A


Dataset-B

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




Reporting to the DNB: problems in value streams


|


Dataset-A


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




Reporting to the DNB: accountabilities in value streams


| 17

User Story-3

User Story-6



User Story-1 User Story-2 Scrum

team-1 User Story-3

User Story-6




team-2


User Story-3

User Story-6




team-n Scrum team-3

User Story-3

User Story-6




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

|


18


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;



Increments


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


User Story As responsible person for the DNB reporting



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


|


20


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




team-1


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




team-2

Mandated Product Owner Domain-M

Scrum team-3

User Story-3

User Story-6




Mandated Product Owner Domain-R

User Story-3

User Story-6




team-4


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)

|


22


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




team-n


Comple- teness




Increments


Design

Value stream ‘Reporting to DNB’


Dataset-B

Domain-R (Business

Capability)


Dataset-A

Domain-M (Business

Capability)

Domain-A (Business

Capability)


Receive Report

DNB

Report

Customer info-N




Customer info-N

Domain-O (Business


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







Increments


Design


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




team-n


Value stream ‘X’ Domain-O (Business


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

|




Increments


Design


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




team-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


|


26



5. Recap

|




Increments


Design

27

User Story-3

User Story-6




team-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>>


|


28



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



conform the acceptance criteria (= mandatory/change prefilled) So we increase the change of capturing mandatory and

changed [customer data]

User Story-2




Increments


Design

29 User Story-6



Scrum team-n




Customer

Customer info-N



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



User Story-3


|


30


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)


Increments


Business layer

Stakeholder &

Solution layer



Initial User Story User Story

Business Objective

Business Capability Value Stream


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


|

How does this help – You?

Quick turnaround on impact analysis

Enable quick time to market

Supports refinement & estimation


|

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)


|


Agile artefacts & RQ’s - perpetually linked

35

Specs & designs

Current state / Enterprise & information model

Change/Sprint

Check out

Check in New & updated


| RQ’s engineering & Agile Artefacts 36

Castles in the air or fit for future

iiba-session requirements engineering and agile artefacts · iiba-session requirements engineering...

Documents