IIBA-sessin Requirements Engineering and Agile Artefacts Peter Nbels Sgeti Management Cnsultant Martijn van Dmselaar ABN AMRO - Sr. Analist 11 april 2017
Requirements Engineering and Agile Artefacts 1. Intr 2. System develpement: tw wrlds and three perspectives 3. (Agile) Artefacts psitined 4. Requirements Engineering & Agile Artefacts 5 Recap RQ s engineering & Agile Artefacts 2
Requirements Engineering and Agile Artefacts Requirements Ckbk 3. Requirement attributes 2. Elicitatin 4. Requirement categry Requirements types requirements Stakehlder requirements 1. Owner Specificatin & Mdeling Techniques Perspectives Organisatin Mdel Decisin Tables Structured Requirements set 5. Requirement descriptin Develpment Apprach Slutin requirements Transitin requirements Interfaces Intelligence Functinal requirement Nn- Functinal requirement 8. Acceptance criterin Use Cases Prcess Management 6. Organising requirements 7. BAAS structure RQ s engineering & Agile Artefacts 3
Requirements Engineering and Agile Artefacts Objectives fr the Requirements Ckbk 1. Guidelines, n a practiner level, fr mdeling and specifying requirements within an Agile way f wrking 2. Requirements fr re-use (stay Agile) 3. Cnnect t artefacts f the enterprise & infrmatin mdel RQ s engineering & Agile Artefacts 4
Requirements Engineering and Agile Artefacts 1. Intr 2. System develpement: tw wrlds and three perspectives 3. (Agile) Artefacts psitined 4. Requirements Engineering & Agile Artefacts 5 Recap Stakehlder Statement & Initial User Stry Value Streams Epics & Objectives Prduct Increments Stakehlder Requirements & Acceptance criteria; Clusters Slutin Requirements User Stries, Acceptance criteria & tasks 5
Change dcumentatin Implementatin independent System dcumentatin System & implementatin dependent System dcumentatin layer Accuntable persn Dmain-x Cnnect t the wrld f accuntable parties Stakehlder & Slutin layer Mandated Prduct Owner Dmain-x Cnnect t the wrld f stakehlders & develpers Stakehlders RQ s engineering & Agile Artefacts
Change dcumentatin Implementatin independent System dcumentatin Enterprise mdel System & implementatin dependent System dcumentatin layer Stakehlder & Slutin layer Change perspective Lifecycle perspective Infrmatin mdel Slutin perspective RQ s engineering & Agile Artefacts
Change dcumentatin Implementatin independent System dcumentatin System & implementatin dependent System dcumentatin Epic T Be Current State Insight Overview Knwledge base Cnsistency Re-use System User Stry User Stry User User Stry Stry User User Stry Stry User User Stry User Stry Stry User User Stry User Stry Stry User User Stry User Stry Stry User User Stry User Stry Stry User User Stry User Stry Stry User User Stry Stry User User Stry Stry User Stry User Stry As is RQ s engineering & Agile Artefacts
Requirements Engineering and Agile Artefacts 1. Intr 2. System develpement: tw wrlds and three perspectives 3. (Agile) Artefacts psitined 4. Requirements Engineering & Agile Artefacts 5. Recap Stakehlder Statement & Initial User Stry Value Streams Epics & Objectives Prduct Increments Stakehlder Requirements & Acceptance criteria; Clusters Slutin Requirements User Stries, Acceptance criteria & tasks 9
Change dcumentatin Implementatin independent System dcumentatin System & implementatin dependent System dcumentatin Objective layer Epic; Prduct Increments Value Stream Capability System Stakehlder & Slutin layer Stakehlder Statement User Stry Stakehlder requirement Slutin RQ (specificatin dcument) Cluster (feature, bject, utput, functin, ) Design = Agile Artefacts RQ s engineering & Agile Artefacts
Requirements Engineering and Agile Artefacts 1. Intr 2. System develpement: tw wrlds and three perspectives 3. (Agile) Artefacts psitined 4. Requirements Engineering & Agile Artefacts 5 Recap Stakehlder Statement & Initial User Stry Value Streams Epics & Objectives Prduct Increments Stakehlder Requirements & Acceptance criteria; Clusters Slutin Requirements User Stries, Acceptance criteria & tasks 11
Epic; Prduct Increments User Stry Bus Objective Value Stream Bus Capability Clusters Stakehlder & slutin RQ Design User Stry As respnsible persn fr the DNB reprting I want less incidents during reprting t the DNB S we can better fulfil ur cmpliancy bligatins Stakehlder Statement Mandated Prduct Owner Dmain-A User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Scrum team-1 Sgeti PwerPint Referentie 2014 RQ s engineering & Agile Artefacts
Requirements Engineering and Agile Artefacts 1. Intr 2. System develpement: tw wrlds and three perspectives 3. (Agile) Artefacts psitined 4. Requirements Engineering & Agile Artefacts 5. Recap Initial User Stry & Stakehlder Statement Value Streams Epics & Objectives Prduct Increments Stakehlder Requirements & Acceptance criteria; Clusters Slutin Requirements User Stries, Acceptance criteria & tasks 13 RQ s engineering & Agile Artefacts
Reprting t the DNB: value stream(s) Epic; Prduct Increments User Stry Bus Objective Value Stream Bus Capability Clusters Stakehlder & slutin RQ Design Value stream Reprting t DNB Value stream X DNB Receive Reprt Dmain-A ( Capability) Receive Dataset-A n request Dmain-M ( Capability) Reprt Dataset- A As respnsible persn fr the DNB reprting I want less incidents during reprting t the DNB S we can better fulfil ur cmpliancy bligatins Receive Dataset-B n request Dataset- B Dmain-R ( Capability) Custmer Prcess-n Dmain-O ( Capability) Mandated Prduct Owner Dmain-A Custmer inf-n
Reprting t the DNB: prblems in value streams Within Data DNB 24 hurs Receive Reprt Dmain-A Quality Receive Dataset-A n request Dmain-M Reprt Dataset- A As respnsible persn fr the DNB reprting I want less incidents during reprting t the DNB S we can better fulfil ur cmpliancy bligatins Receive Dataset-B n request Dataset- B Up t date Dmain-R Custmer Prcess-n Dmain-O Mandated Prduct Owner Dmain-A Custmer inf-n Cmple- teness RQ s engineering & Agile Artefacts
DNB Within 24 hurs Receive Reprt Reprt As respnsible persn fr the DNB reprting I want less incidents during reprting t the DNB S we can better fulfil ur cmpliancy bligatins Reprting t the DNB: Dmain-A Data Quality Receive Dataset-A n request Dataset- A Receive Dataset-B n request Dataset- B Up t date Accuntable persn Dmain-M Dmain-M Dmain-R Accuntable persn Dmain-R accuntabilities in value streams Custmer Prcess-n Accuntable persn Dmain-O Dmain-O Accuntable persn Dmain-A Custmer inf-n Cmple- teness RQ s engineering & Agile Artefacts
Within 24 hurs Data Quality Up t date Cmple- teness Mandated Prduct Owner Dmain-A User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Scrum team-1 Mandated Prduct Owner Dmain-M User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Scrum team-2 Mandated Prduct Owner Dmain-R User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Scrum team-3 Mandated Prduct Owner Dmain-O User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Scrum team-n 17
Requirements Engineering and Agile Artefacts 1. Intr 2. System develpement: tw wrlds and three perspectives 3. (Agile) Artefacts psitined 4. Requirements Engineering & Agile Artefacts 5. Recap Initial User Stry & Stakehlder Statement Value Streams Buiness Epics & Objectives Prduct Increments Stakehlder Requirements & Acceptance criteria; Clusters Slutin Requirements User Stries, Acceptance criteria & tasks 18
Epic-x As accuntable persn fr the DNB reprting I want t cmply better t the (new) DNB-regulatins S we can keep ur banking licence Objective Epic; Prduct Increments User Stry Bus Objective Value Stream Bus Capability Clusters; Stakehlder & slutin RQ Design Accuntable persn Dmain-A Epic-x Epic-2 Epic-3 Epic-4 Epic-5 Epic-6 Epic-7 Epic-8 Epic-9 User Stry As respnsible persn fr the DNB reprting I want less incidents during reprting t the DNB S we can better fulfil ur cmpliancy bligatins Mandated Prduct Owner Dmain-A Sgeti PwerPint Referentie 2014 19 RQ s engineering & Agile Artefacts
Requirements Engineering and Agile Artefacts 1. Intr 2. System develpement: tw wrlds and three perspectives 3. (Agile) Artefacts psitined 4. Requirements Engineering & Agile Artefacts 5. Recap Initial User Stry & Stakehlder Statement Value Streams Buiness Epics & Objectives Prduct Increments Stakehlder Requirements & Acceptance criteria; Clusters Slutin Requirements User Stries, & tasks 20
Prgram layer Prduct Increment-1 Imprve reprting regarding t data (quality, cmpleteness, up t date) Prduct Increment-2 Imprve reprting regarding t SLA (within 24 hurs) Prduct Increment-3 DNB Recieve Reprt Value Stream Reprting t DNB Dmain-A Custmer Recieve Dataset-A n request Recieve Dataset-B n request Custmer inf-n Prcess-n Dmain-M Dmain-R Dmain-O Value Stream X Custmer inf-n Prduct Increment-x Within 24 hurs Data Quality Team Layer Up t date Cmple- teness Mandated Prduct Owner Dmain-A User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Scrum team-1 Mandated Prduct Owner Dmain-M User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Scrum team-2 Mandated Prduct Owner Dmain-R User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Scrum team-3 Mandated Prduct Owner Dmain-O User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Scrum team-4 21
Requirements Engineering and Agile Artefacts 1. Intr 2. System develpement: tw wrlds and three perspectives 3. (Agile) Artefacts psitined 4. Requirements Engineering & Agile Artefacts 5. Recap Initial User Stry & Stakehlder Statement Value Streams Buiness Epics & Objectives Prduct Increments Stakehlder Requirements & Acceptance Criteria; Clusters Slutin Requirements User Stries, Acceptance criteria & tasks 22
Epic; Prduct Increments User Stry Bus Objective Value Stream Bus Capability Clusters; Stakehlder & slutin RQ Design DNB Receive Reprt Value stream Reprting t DNB Dmain-A ( Capability) Receive Dataset-A n request Cluster (grup f RQ s related t subject) = Register Custmer Inf Reprt Dataset- A Dmain-M ( Capability) Custmer Value stream X Prcess-n Dmain-O ( Capability) As respnsible persn fr the DNB reprting I want less incidents during reprting t the DNB S we can better fulfil ur cmpliancy bligatins Mandated Prduct Owner Dmain-A Receive Dataset-B n request Dataset- B Custmer inf-n Dmain-R ( Capability) Cmple- teness Mandated Prduct Owner Dmain-O User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Scrum team-n 23
Epic; Prduct Increments User Stry Bus Objective Value Stream Bus Capability Clusters; Stakehlder & slutin RQ Design Stakehlder Requirement As respnsible persn fr Custmer inf I want the system t shw the custmer the [custmer data] we already knw S we dn t anny him with unnecessary questins and we give him the pssibility t update his/her data Stakehlder Requirement As respnsible persn fr Custmer inf I want the system t stre the [custmer data] entered1) by the custmer S we have his/her up t date infrmatin available 1) 1) changed r new [custmer data] Name* Adress* ZIP-cde*) & City* LEI* 2) ( = Legal Entity Identifier) *) = Mandatry 2) New RQ, needed fr DNB-reprting Custmer Custmer inf-n Value stream X Prcess-n Mandated Prduct Owner Dmain-O User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Dmain-O ( Capability) Register Custmer Inf Scrum team-n 24
Epic; Prduct Increments User Stry Bus Objective Value Stream Bus Capability Clusters; Stakehlder & slutin RQ Design Stakehlder Requirement As respnsible persn fr Custmer inf I want the system t shw the custmer the [custmer data] we already knw S we dn t anny him with unnecessary questins and we give him the pssibility t update his/her data Custmer Value stream X Prcess-n Dmain-O ( Capability) Custmer inf-n Register Custmer Inf RQ s Acceptance Criteria As respnsible persn fr Custmer inf I accept the slutin regarding t this RQ when It s clear t the custmer which data is mandatry RQ s Acceptance Criteria As respnsible persn fr Custmer inf I accept the slutin regarding t this RQ when It s clear t the custmer that (s)he has the pssibility t change the value f pre-filled fields Mandated Prduct Owner Dmain-O User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Scrum team-n 25
Requirements Engineering and Agile Artefacts 1. Intr 2. System develpement: tw wrlds and three perspectives 3. (Agile) Artefacts psitined 4. Requirements Engineering & Agile Artefacts 5. Recap Initial User Stry & Stakehlder Statement Value Streams Buiness Epics & Objectives Prduct Increments Stakehlder Requirements & Acceptance criteria; Clusters Slutin Requirements User Stries, Acceptance criteria & tasks 26
Epic; Prduct Increments User Stry Bus Objective Value Stream Bus Capability Clusters; Stakehlder & slutin RQ Design Value stream X Slutin Requirement (Specificatin dcument; type Use Case ) Custmer Prcess-n Dmain-O ( Capability) Custmer <<include>> Create custmeraccunt Shp Wrker Custmer inf-n Register Custmer Inf <<include>> Register Custmer <<include>> Cmplete accunt <<include>> Activate accunt Reset passwrd Mandated Prduct Owner Dmain-O User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Scrum team-n 27
Requirements Engineering and Agile Artefacts 1. Intr 2. System develpement: tw wrlds and three perspectives 3. (Agile) Artefacts psitined 4. Requirements Engineering & Agile Artefacts 5. Recap Initial User Stry & Stakehlder Statement Value Streams Buiness Epics & Objectives Prduct Increments Stakehlder Requirements & Acceptance criteria; Clusters Slutin Requirements User Stries, Acceptance criteria & tasks 28
Epic; Prduct Increments User Stry Bus Objective Value Stream Bus Capability Clusters; Stakehlder & slutin RQ Design User Stry-1 As respnsible persn fr Custmer inf I want the system t shw the custmer the [custmer data] we already knw S we dn t anny him with unnecessary questins and we give him the pssibility t update his/her data User Stry-2 As respnsible persn fr Custmer inf I want the system t shw the custmer the [custmer data] we already knw cnfrm the acceptance criteria (= mandatry/change prefilled) S we increase the change f capturing mandatry and changed [custmer data] User Stry-3 As respnsible persn fr Custmer inf I want the system t stre the [custmer data] entered1) by the custmer S we have his/her up t date infrmatin available 1) changed r new Custmer Custmer inf-n Value stream X Prcess-n Mandated Prduct Owner Dmain-O User Stry-1 User Stry-2 User Stry-3 User Stry-4 User Stry-5 User Stry-6 User Stry-7 User Stry-8 User Stry-9 Dmain-O ( Capability) Register Custmer Inf Scrum team-n 29
Requirements Engineering and Agile Artefacts 1. Intr 2. System develpement: tw wrlds and three perspectives 3. (Agile) Artefacts psitined 5. Requirements Engineering & Agile Artefacts 5. Recap Initial User Stry & Stakehlder Statement Value Streams Buiness Epics & Objectives Prduct Increments Stakehlder Rrequirements & Acceptance criteria; Clusters Slutin Requirements User Stries, Acceptance criteria & tasks 30
Change dcumentatin Implementatin independent System dcumentatin System & implementatin dependent System dcumentatin Objective layer JIRA Epic; Prduct Increments Value Stream Capability System Stakehlder & Slutin layer JIRA Stakehlder Statement Initial User Stry User Stry Stakehlder requirement Slutin RQ (specificatin dcument) RMSIS Cnfluence Cluster (feature, bject, utput, functin, ) Design
Hw des this help Yur team? Ding the right Thing, and ding things right. Enabling the PO t priritise n backlg items Be Agile & stay agile, by managing yur infrmatin Enabling fcus n the change, nt n reverse engineering Relate changes t their value streams Defining Prduct Increments RQ s engineering & Agile Artefacts 32
Hw des this help Yu? Quick turnarund n impact analysis Enable quick time t market Supprts refinement & estimatin RQ s engineering & Agile Artefacts 33
Hw des this help Yur rganisatin? By using the same language, increase effectiveness f team cperatin Enabling cmpliancy n Audit pints & cntrl bjectives Supprt quick nbarding f new team members, emplyability Pave the way fr future develpments (DevOps) RQ s engineering & Agile Artefacts 34
Agile artefacts & RQ s - perpetually linked Change dcumentatin Change/Sprint Implementatin independent System dcumentatin Current state / Enterprise & infrmatin mdel Check ut Check in New & updated Specs & designs 35
Castles in the air r fit fr future RQ s engineering & Agile Artefacts 36