ein containerschiff wird agile - asqf · 2020-03-20 · impact backlog map team product stream...

24. Oktober 2019 0

Ein Containerschiff wird Agile

David Heitzinger, Raiffeisen Bank International

Agile Night, 24. Oktober 2019

Agile Night 2019 – Ein Containerschiff wird Agile

„Ein Containerschiff wird Agile“

1

The sea is getting rougher for

financial services companies:

• Fintechs

• Digital Startups

• Big tech companies on the market: ApplePay,

GooglePay, etc.

• Mobile banks

• New technology trends like Digital Banking, AI, data centricity, …

24. Oktober 2019Agile Night 2019 – Ein Containerschiff wird Agile

RBI’s bumpy road to agility

2

Kanban

Hybrid projects (dead-end)

Quantitative Scrum goals (dead-end)

Scaling Scrum/LESS/Safe (dead-end) The way out: Adaptive Organization

First Scrum (2011)


Goals and impact of Adaptive organization


Adaptive Organization covers many dimensions

4

Adaptive Organization: holistic approach

• From Projects to Products (tribes)

• Culture: Mindset, leadership

• Employees: education, job roles, career model

• Organizational changes

• Processes (budgeting, performance management,

strategy, …)

• Governance (technologies, Audit, Security, regulatory authorities, …)

?


Tribe concept

5

Trib

e 1

Business

Owner

GoalsKPIsRun-Rate

and Split

Delivery

Manager

Pro

du

ct

Str

ea

m

Business

ServicesProduct

Owner Product

BacklogImpact

Map

Team

Pro

du

ct

Str

ea

m

Business

Services

Product

Owner Product

BacklogImpact

Map

Team 1

Team 2

Scrum

Master

Scrum

Master

Vision

Vision

IT

What is a Tribe?• A collection of Product Streams• organized around the same purpose

• Business + IT working closely together

Business

TRIBENOT A TRIBE

Business

NOT A TRIBE

IT


The adaptive change consists of many pieces

6

Top Management Support

Reference Model

Agile Coaches


OfficesExperimenting & Learning

Organizational Changes

Agile Engineering Support

7

A new piece in the puzzle: Agile Engineering Support

• Engineering Coaches

• Agile Tool Chain

• People excellence

Focus areas

• Continuous Integration &

Delivery

• Test Automation

• DevOps

• Cloud

Continuous

Delivery platformEngineering

platform

Collaboration

platform

Agile Engineering

Coaches

CI/CD

Test automation

GIT/Bitbucket

Nexus

JIRA

Confluence

Workplace

Dev Server

Coaching Platforms


4 steps Coaching approach


Coaching fosters mindset change

Starting with the mindset

§ It’s not only about changing technologies. The change starts with a mindset change

§ Engineers and non-Engineers have to re-think their approach

§ As a guidance, we have defined values & principles

§ Engineering principles go

hand-in-hand with Agile principles

§ In accordance with company values


Agile Engineering Support – Our principles

10

Agile software development

§ Agile principles are at the core of our work

Continuous Integration & Delivery

§ Continuously change, test and deploy the product by using a build- and delivery pipeline

Managing complexity & technical debt

§ Invest into the future by keeping the product clear and simple

Value first

§ Use customer value as the main guidance for decisions

Open Source & Open Documentation

§ Openly share code and experience to foster collaboration and people development

API first

§ Services do not share databases but communicate via events and APIsAPI


Agile Engineering Support – What we value

11

Engineering Mindset

§ Structured, systematic, analytical, fact- and observation-based approach

Coding Excellence

§ We build code, we’re proud of

Speed of execution and time-to-market

§ Create environments that facilitate teams to deliver fast and frequent

Clear Ownership and Responsibilities

§ We take clear ownership and responsibility for our product

Outcome over Output

§ The impact of our work is more important than the effort we've been putting in

Simplicity over Complexity

§ Simplicity over complexity to sustain a high innovation pace also in the long run

Services and Data can be consumed by Others

§ Each product provides business level functionality and data for others to be consumed

Openly share Information and Knowledge

§ To facilitate mutual learning and collaboration

Continuous Learning and Improvement

§ Continuously improve to achieve better time-to-market & higher customer satisfaction


Engineering Values & Principles are commonly used


WHAT

§ Automated build, test, deployment and provision without manual intervention

§ Single gateway to bring any change into any environment

Continuous Integration & Delivery - what do we want to

achieve?

13

KPI Comment

Release frequencyIncrease deployment and release frequency. Typically from

quarterly to multiple times a day

Shipping speed Build, test and deploy in less than one hour

Software quality No additional failures due to deployment errors

Transparency Full traceability for every change

System downtime No downtime, whenever possible. Changes fully reversable

WHY


Example: Build pipeline, as used in a Retail Banking

app

14

Everything is

code, even

Infrastructure

Code quality,

security checks

Managed

environments with

dedicated test goals

Development

workplace, outside of

test & production


CDA for orchestration of product build and deployment

15

Average

#Build & Deployment runs in CDA

• Avg. throughput: 1.500 per day

#Active products in CDA

• Continuous increase of usage

#Target environments in CDA

• Ca. 1.000 environments configured

Deployment duration into production

• Average duration: 3,3 min



16

Average











17

Average










Test automation - what do we want to achieve?

18

KPI Comment

Software qualityIncrease quality by testing as much as possible and by

avoiding human error

Shipping speed Build, test and deploy in less than one hour

Testing effortDecrease repetitive, manual tasks and focus on specific,

manual tests only

System costsReduce long-term costs by increasing system stability and

keeping technical debt low

Bug riskAssess and manage risk of system bugs by smart test

automation approaches

WHY

“Automation does not do what testers used to do,

unless one ignores most things a tester really does.

Automated testing is useful for extending the reach

of the tester’s work, not to replace it.”James Bach | Founder and CEO of Satisfice Inc

WHAT


DevOps – what do we want to achieve

19

WHAT

§ The team, that builds and tests the software is also responsible for shipping and operating it

§ Automation, Team-Responsibility, T-shaped skills

KPI Comment

Software qualityImprove quality by enabling end-to-end thinking and

responsibility of all team members

System failure Reduce failure through tight monitoring and feedback

Team performanceIncreased and stable delivery performance through smart

resource balancing with T-shaped skill profiles

Employee satisfaction Employee empowerment and development

WHY


DevOps in a nutshell

20

3. Continuous Learning,

Experimentation and

Improvement

2. Tighten Feedback Loops (right-to-left)

1. Keep the value stream flowing (left-to-right)

Requirements

Customer

Automation: Build, Test, Deployment, CI/CD Pipeline, Infrastructure as Code, Security,Reduce Batch Size & Wait Times, Full Stack Teams, Limit Handoffs, Collaboration

Technical Debt Management, Blameless Post Mortems, Standardization, Self-organizing, Risk taking culture, Reserve 20% for improvement, Job Rotation, …

Automated Test Reports, Metrics, Logging & Monitoring, Integration with Collaboration Tools, Analytics, Know your Customer, Canary Rollouts


Gartner’s DevOps Model

21

People

ProcessTechnology

Culture

Continuous

Monitoring

Technical

Debt

Test-driven

Development

Test-Driven

Deployment

Test

Everything

Instrument

Everything

Integrated

Tool Chains

Trust

Culture

Monitor

Everything

Infrastructure as

Code

Engineering

Culture

Collective

Ownership

Autonomous

Teams

Joint

Meetings

Learning

Culture

Developer

Self-Service

Job

Rotation

Full-Stack

Teams

Continuous

Testing

Continuous

Integration

ChatOps

Site Reliability

Engineers

One-Step Build,

Test, Deploy

Minimum

Viable

Process

Common

Metrics

Feature

Flags

Optimize

Flow

Chaos

Monkey

Value

Streams

Collaborative

Culture

Never

Done

Small

Batches

Automated

Testing

Minimum

Viable

Product

Release

Automation

Automated

Builds

Canary

Rollouts

Fail Forward

Continuous

Delivery

Version

Everything

Servant

Leadership

Platform

Engineers

Feature

Teams


Cloud – what do we want do achieve

22

WHY

§ Putting all things together

§ Cloud native means automation

§ Cloud native means monitoring and measuring

§ Cloud native means build and run

§ Cloud native means flexibility and scalability

§ Cloud is a paradigm change from “Design for stability” to “Design for change”

§ Minimizing Mean Time To Repair (MTTR) instead of maximizing Mean Time between Failures

(MTBF) to

§ In general: being fit for the future


Agile Engineering Support – What else?

23

There is much more to do: Communities, Guilds, people development, minimum

standards, …Agile Engineering Event Schedule

Agile Round Table Sep 26

Meetup „Software Testing Metrics“ Oct 2

RBI Testing Day Oct 3

Agile Night Oct 24

RBI SDLC Nov 7/8

RBI GoIT!Academy Q1 2020

Meetup Software Testing MetricsRBI Testing Day, May 2019Test automation training - Jenga

people coaching


ein containerschiff wird agile - asqf · 2020-03-20 · impact backlog map team product stream...

Documents