Richard Brenner, Zvonimir Durcevic

SAFe® 4.5 und LeSS Scaling Agile Frameworks im Vergleich

2

(Software) Quality

“Quality is value to some person.” (Weinberg, 1991)

“The difficulty in defining quality is to translate future needs of the user into measurable

characteristics, so that a product can be designed and turned out to give satisfaction at a

price that the user will pay” W. Edwards Deming (Wikipedia, 2017a)

“Quality is a customer determination, … It is based on the customer's actual

experience with the product or service, measured against his or her requirements --

stated or unstated … and always representing a moving target in a competitive market.”

A.V. Feigenbaum (Wikipedia, 2017a)

“… multiple meanings .. 1. Quality consists of those product features which meet the

need of customers and thereby provide product satisfaction. 2. Quality consists of

freedom from deficiencies. … “fitness for use”” J.M. Juran (Wikipedia, 2017a)

3

Qualität in Agilen Methoden durch

› … Kunden-Fokus

› … Rasches Feedback

› … „Time to Learn“ vom Kunden wird kürzer

› … Qualitätsbewusstsein in den Teams

› … DevOps Prinzipien/Techniken

4

Welches Problem lösen Skalierungs-Frameworks?

› Neuproduktentwicklung, die sich über mehrere Teams erstreckt

› Wie fokussiere ich Teams auf den Business Value?

› Wie stelle ich gute Qualität sicher?

5

SAFe® 4.5– Scaled Agile Framework Essential Configuration

Quelle: Scaled Agile Framework® http://www.scaledagileframework.com

6

Wir nutzen die Stärke agiler Teams

Cross-funktionale, selbstorganisierende Einheiten, die ein Feature definieren, entwickeln und testen

Plan—Do—Check—Adjust

Liefern alle zwei Wochen einen Wert

Team

1

Team

n

Do

Check Adjust

Plan

PDCA

© Scaled Agile, Inc.

7

Einschwören der Teams auf die Kernwerte von SAFe®

›Built-In Quality

›Transparency

›Program Execution

›Alignment

“Built-in Quality ensures that every increment of the solution

reflects quality standards.

Quality is not “added later.”

Built-in quality is a prerequisite of Lean and flow;

without it, the organization will likely operate with large

batches of unverified, unvalidated work.

Excessive rework and slower velocities are the likely outcome.

There can be no ambiguity about the importance

of built-in quality in large-scale systems. It is mandatory.”

Quelle: http://www.scaledagileframework.com/safe-core-values/

8

SAFe® 4.5– Qualität im SAFe Prozess

Quelle: Scaled Agile Framework® http://www.scaledagileframework.com

Continious Delivery und Deployment

Inspect and Adapt PI Planning

Value Stream, Wert für den Kunden

9

LeSS – Large Scale Scrum (Principles)

Quelle: https://less.works/

10

LeSS – Large Scale Scrum (Frameworks – LeSS Huge)

Quelle: Large-Scale Scrum: More with LeSS; Craig Larman & Bas Vodde

11

LeSS – Roles & Responsibilities

Quelle: Large-Scale Scrum: More with LeSS; Craig Larman & Bas Vodde

12

LeSS – Customer Centric

13

Referenzen

Craig Larman, Bas Vodde (2016) Large-Scale Scrum: More with LeSS, Addison-Wesley

Signature Series (Cohn)

Gerald M. Weinberg (1991) Quality Software Management, Volume 1, Systems Thinking,

Dorset House Publishing

Wikipedia (2017a) “Software Quality” [Online] Available from:

https://en.wikipedia.org/wiki/Software_quality (Last accessed: 10.10.2017)