Does your business solution delivery capability contributes to business agility?

1. Etienne Venteretienne.venter@santam.co.za
https://www.linkedin.com/in/etienne-venter-15185131/
Business Solution Delivery Capability

2. Business Agility
1. Business Agility
Overview
Agility is the ability of an organization to
renew itself, adapt, change quickly, and
succeed in a rapidly changing,
ambiguous, turbulent environment.
Aaron De Smet

3. Speak up when something’s not right
and should be improved. Don’t be afraid
to challenge and shoot for better.
Care enough about the work
you do and the business you
are part of. Bring a sense of
energy and drive to your work.
Remember that clients trust us with
their insurance needs.
Don’t take short cuts, do a proper
job, finish things. Strive for success
Think about the long term
impact of your actions.
Strive to see beyond the facts
in front of you and care about
the human behind them.
Keep your promises.
Do what you say you are
going to do.

4. Crew: +- 5500 & rotates every 6 months Crew: +- 3000 (permanent + contractors)
dynamic elements
McKinsey Quarterly December 2015
Business Agility

5. McKinsey Quarterly December 2015
Business Agility
BSDF
structure
BSDF
Processes
BSDF DPF +
SDF + PEG

6. Business Agility & IP
Knowledge
retention
Knowledgelost

7. Business Solution Delivery
Framework
2. BSDF Overview

8. Business Solution Delivery Framework
Technology Layer
Application + Data Layer
Business Layer

9. Business Solution Delivery Framework
C: Information
Systems
Architectures
D: Technology
Architecture
E: Opportunities
& Solutions
F: Migration
Planning
G: Implementation
Governance
H: Architecture
Change
Management
B: Business
Architecture
A: Architecture
Vision
Concept
L1 processes impacted
Project Concept
Scope Definition
Deploy
● User Story Design
● Build
● Test
Inception Construction
S0 BC S1 BC
Production
Solution Architecture
Design
Product Backlog
Change Requests
● Pilot
● Migration
● Warrantee
● Operational
Integration Impact | New
Foundation Component
Enhancement
Current Technology
Current Systems
Requirements
Management

10. Business Solution Delivery Framework - Concepts
Data
ConstructionSolutionConceptScope
Sea
Level
Cloud
Level
Project Goal
Process Goal
Requirements
Project Owner
Process Owner
System Owner $
Class diagram
IE data model
Process diagram
Sequence diagram
State machine
Screen navigation
Screen design
DW structure
Test definitions
Component diagram
Build
Test
Maintainbacklog
Sub-process design (BPMN) & Requirements
Main process context
Project scope (Project canvas)
$
UC Scenarios Requirements
S1 S2 S3 R1 R2 R3



a
1
a
2
a
3
a
4
a
1
a
4
BusinessApplication+Technology
Fish
Level
Use
Case
Project
Main Process
1..*
Design 0..*
Tasks
Application co-operation
viewpoint
Infrastructure usage
viewpoint
Sub -
process
+
R1 R2 R3
a1
a5a2
a3
a4
a
1
a
5
a
3
a
4

11. Business Solution Delivery Framework + Project Portfolio
B.
Business
Architecture
G.
Implementation
Governance
A.
Architecture
Vision
D.
Technology
Architecture
H.
Architecture
Change
Management
E.
Opportunities
&
Solutions
F.
Migration
Planning
C.
Information
Systems
Architecture
Requirements
Management
Preliminary
Business
Unit A
Business
Unit B
Business
Unit C
Business
Unit D
E. Opportunities & Solutions
F. Migration Planning
AA A A
Business
Strategy
Desired State
Desired State
Desired State
B.B. B. B. Current State Gaps
CC C C Current State Gaps
D D D D Current State Gaps
Identification of Required Change
Implementation of Change
C: Information
Systems
Architectures
D: Technology
Architecture
E: Opportunities
& Solutions
F: Migration
Planning
G: Implementation
Governance
H: Architecture
Change
Management
B: Business
Architecture
A: Architecture
Vision
Concept
L1 processes impacted
Project Concept
Scope Definition
Deploy
● User Story Design
● Build
● Test
Inception Construction
S0 BC S1 BC
Production
Solution Architecture
Design
Product Backlog
Change Requests
● Pilot
● Migration
● Warrantee
● Operational
Integration Impact | New
Foundation Component
Enhancement
Current Technology
Current Systems
Requirements
Management

12. Concept
3. Concept

13. Concept – Project Canvas
C: Information
Systems
Architectures
D: Technology
Architecture
E: Opportunities
& Solutions
F: Migration
Planning
G: Implementation
Governance
H: Architecture
Change
Management
B: Business
Architecture
A: Architecture
Vision
Concept
L1 processes impacted
Project Concept
Scope Definition
Deploy
● User Story Design
● Build
● Test
Inception Construction
S0 BC S1 BC
Production
Solution Architecture
Design
Product Backlog
Change Requests
● Pilot
● Migration
● Warrantee
● Operational
Integration Impact | New
Foundation Component
Enhancement
Current Technology
Current Systems
Requirements
Management

14. Inception – Scope
Definition
4. Inception

15. Inception – Scope Definition
C: Information
Systems
Architectures
D: Technology
Architecture
E: Opportunities
& Solutions
F: Migration
Planning
G: Implementation
Governance
H: Architecture
Change
Management
B: Business
Architecture
A: Architecture
Vision
Concept
L1 processes impacted
Project Concept
Scope Definition
Deploy
● User Story Design
● Build
● Test
Inception Construction
S0 BC S1 BC
Production
Solution Architecture
Design
Product Backlog
Change Requests
● Pilot
● Migration
● Warrantee
● Operational
Integration Impact | New
Foundation Component
Enhancement
Current Technology
Current Systems
Requirements
Management

16. 4. Inception
Inception – Solution
Architecture Definition

17. Inception – Solution Architecture Definition
C: Information
Systems
Architectures
D: Technology
Architecture
E: Opportunities
& Solutions
F: Migration
Planning
G: Implementation
Governance
H: Architecture
Change
Management
B: Business
Architecture
A: Architecture
Vision
Concept
L1 processes impacted
Project Concept
Scope Definition
Deploy
● User Story Design
● Build
● Test
Inception Construction
S0 BC S1 BC
Production
Solution Architecture
Design
Product Backlog
Change Requests
● Pilot
● Migration
● Warrantee
● Operational
Integration Impact | New
Foundation Component
Enhancement
Current Technology
Current Systems
Requirements
Management

18. 4. Inception
Inception – Product
Backlog

19. Inception – Product Backlog
C: Information
Systems
Architectures
D: Technology
Architecture
E: Opportunities
& Solutions
F: Migration
Planning
G: Implementation
Governance
H: Architecture
Change
Management
B: Business
Architecture
A: Architecture
Vision
Concept
L1 processes impacted
Project Concept
Scope Definition
Deploy
● User Story Design
● Build
● Test
Inception Construction
S0 BC S1 BC
Production
Solution Architecture
Design
Product Backlog
Change Requests
● Pilot
● Migration
● Warrantee
● Operational
Integration Impact | New
Foundation Component
Enhancement
Current Technology
Current Systems
Requirements
Management

20. Construction
5. Construction

21. Construction – User Story Realization
C: Information
Systems
Architectures
D: Technology
Architecture
E: Opportunities
& Solutions
F: Migration
Planning
G: Implementation
Governance
H: Architecture
Change
Management
B: Business
Architecture
A: Architecture
Vision
Concept
L1 processes impacted
Project Concept
Scope Definition
Deploy
● User Story Design
● Build
● Test
Inception Construction
S0 BC S1 BC
Production
Solution Architecture
Design
Product Backlog
Change Requests
● Pilot
● Migration
● Warrantee
● Operational
Integration Impact | New
Foundation Component
Enhancement
Current Technology
Current Systems
Requirements
Management

22. Traceability
6. Traceability

23. Construction – Traceability
JIRA Issue Types & Relationships
User Story
Test Case
Subtask
Artifact (Code) Release
Artifact
(Model)
Use Case
is blocked by
has
is part of
Developer
subtask
Design
subtask
Testing
subtask
realizes
Process
groups
Swim lane
Epic
Story

24. Summary
7. Summary

25. Business & IT Alignment

26. Process
Activity Detail
Process Scenarios
PublishedinConfluence
Modelledin
ARIS
JIRAAsset
Management