MARTIN FASSUNGE & TOBIAS HILDENBRAND | SAP AG | 5 JULY 2012

COMBINING DESIGN AND DEVELOPMENT

Design

Dev

© SAP 2012 | 2

WHERE DO WE COME FROM?

© SAP 2012 | 3 40 YEARS OF SAP…

Source: SAP

© SAP 2012 | 4 …42 YEARS OF WATERFALL

© SAP 2012 | 5 THE WATERFALL – A BUREAUCRATIC APPROACH

Analyze Design

Code

Test

Year 1 Year 2 Year 3 Year 4

Fear of delivery

© SAP 2012 | 6

WHERE ARE WE TODAY?

© SAP 2012 | 7 COMPLEMENTING LEAN & SCRUM WITH AGILE ENGINEERING

Das Comeback (FOCUS 22/2012, S. 122ff.)

© SAP 2012 | 8

AGILE = “ABLE TO MOVE QUICKLY & EASILY”*

*) Definition from Longman Dictionary of Contemporary English

© SAP 2012 | 9 INTRODUCTION OF LEAN, AGILE DEVELOPMENT & SCRUM

Chief Product team

release backlog

sprint backlog

product backlog

BUT: “There is surely nothing quite so useless, as doing with great efficiency what should not be done at all” - Peter Drucker

?

© SAP 2012 | 10

…SO, WHAT DOES AGILE MEAN FROM A BUSINESS PERSPECTIVE?

© SAP 2012 | 11 WHAT DOES ‘AGILE’ MEAN FROM A BUSINESS PERSPECTIVE?

2. Quickly reprioritize

1. Respond to change

3. Intensive customer interaction

4. Iterative delivery

Source: Charles G.Cobb (2011) - Making Sense of Agile Project Management,

5. Right-sized processes

© SAP 2012 | 12

WHY CAN„T WE JUST MAKE A MASTER PLAN?

© SAP 2012 | 13 REQUIREMENTS SPECIFICATION UNDER UNCERTAINTY

simple

complicated

complex

anarchy

technology

requ

irement

s

far from certainty

close to certainty

close to alignment

far from alignment

.

.

.

© SAP 2012 | 14 FIXED SCOPE IS AN ILLUSION AND PROMISES FALSE SAFETY

Teams Timelines

Scope

fixed

variable

© SAP 2012 | 15 PROCESS-WISE, SOFTWARE DEVELOPMENT IS DIFFERENT

Creative

Repetitive

Intangible Physical

© SAP 2012 | 16

WHY DO WE LIKE SCRUM?

© SAP 2012 | 17 SCRUM REDUCED RISKS DRAMATICALLY

Retrospectives

Split organization into teams

Split work

Split time

Deliver more frequently

Risk

Risk

© SAP 2012 | 18 SCRUM IS PEOPLE-CENTRIC AND FOSTERS TEAM WORK

Personal Responsibility

Partnership

Shared Purpose

Mutual Trust

Collaboration Mindset

© SAP 2012 | 19

Lean

Scrum

ASE Set of principles

Project Management Framework

Agile Software Engineering

Practices

SCRUM IS CODE-CENTRIC WITH A SHARED SENSE OF QUALITY

© SAP 2012 | 20 COMPLEMENTING SCRUM WITH ENGINEERING PRACTICES

© SAP 2012 | 21 DON‘T WAIT ANOTHER 40 YEARS

1. Take an Economic View

2. Actively Manage Queues

3. Exploit Variability

4. Reduce Batch Size

5. Apply WIP Constraints

6. Control Flow: Cadence and Synchronization

7. Apply Fast Feedback

8. Decentralize Control?

The Principles of

Product Development

FLOW Second generation Lean Product Development Donald G. Reinertsen

Source: Donald G. Reinertsen (2009) – Lean Product Development Flow

© SAP 2012 | 22 SCRUM IMPLEMENTS MOST PRINCIPLES OF LEAN

Iterative feedback empirical process

control Velocity understood

Limited team size iteration cycles, limited WIP*

*) WIP = work-in-progress

© SAP 2012 | 23

…BUT, WHAT ABOUT THE ECONOMIC VIEW?

© SAP 2012 | 24 THE LEAN CANVAS TAKES AN ECONOMIC VIEW

Source: Ash Maurya (2012) – Running Lean

© SAP 2012 | 25 VALIDATED LEARNING INCLUDING THE ECONOMIC VIEW

Source: Eric Ries (2011) – The Lean Startup

…but beware of ”vanity metrics”!

Iterate…

© SAP 2012 | 26 EVOLVE BUSINESS MODELS, NOT JUST PRODUCTS

Problem/ Solution

Fit?

Solution/ Customer

Fit?

Solution/ Market Fit?

1 month 1 month 1 month

Pivot or persevere?

Pivot or persevere?

Scaling,dying or extending?

© SAP 2012 | 27

WHERE DO REQUIREMENTS COME FROM?

© SAP 2012 | 28 SCIENTIFIC ANALYSIS WITH A DEDUCTIVE APPROACH

Idea White paper Detailed specification

© SAP 2012 | 29

HOW DOES DESIGN WORK?

© SAP 2012 | 30 DIVERGING & CONVERGING TO UNDERSTAND THE PROBLEM

„Wicked problem„

Solvable problem

Less wicked problem

Development

© SAP 2012 | 31

WHAT IS DESIGN THINKING?

© SAP 2012 | 32

„„A DEVELOPER NEEDS TO BE CURIOUS AND ALSO DEVELOP EMPATHY FOR END USERS“…

Source: interview with SAP co-founder Hasso Plattner (2012)

© SAP 2012 | 33 DESIGN THINKING PILLARS

3. Approach

2. Space

1. People

© SAP 2012 | 34 SAP‘S DESIGN THINKING APPROACH

Address the right question …and create the right solution

Customers Stakeholders

Customers Stakeholders

© SAP 2012 | 35

HOW DO WE COMBINE DESIGN & DEVELOPMENT TODAY?

© SAP 2012 | 36 COMBINING DESIGN AND DEVELOPMENT IN PRACTICE

User Research Teams

Synthesis

Product Vision

Product Backlog

User Story Mapping

Personas Prototyping

© SAP 2012 | 37 DESIGN & DEVELOPMENT ARE COMPLEMENTARY

Design (Thinking) (Lean) Development

Set of shared values and principles

Thank You!

Contact Information: Martin Fassunge SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf T: +49 6227 7-47474 martin.georg.fassunge@sap.com

Dr. Tobias Hildenbrand SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf T: +49 6227 7-47474 tobias.hildenbrand@sap.com