scrum day 2012 keynote: combining design and development
DESCRIPTION
Scrum Day 2012 Keynote together with Martin Fassunge in St. Leon-Rot, GermanyTRANSCRIPT
![Page 1: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/1.jpg)
MARTIN FASSUNGE & TOBIAS HILDENBRAND | SAP AG | 5 JULY 2012
COMBINING DESIGN AND DEVELOPMENT
Design
Dev
![Page 2: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/2.jpg)
© SAP 2012 | 2
WHERE DO WE COME FROM?
![Page 3: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/3.jpg)
© SAP 2012 | 3 40 YEARS OF SAP…
Source: SAP
![Page 4: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/4.jpg)
© SAP 2012 | 4 …42 YEARS OF WATERFALL
![Page 5: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/5.jpg)
© SAP 2012 | 5 THE WATERFALL – A BUREAUCRATIC APPROACH
Analyze Design
Code
Test
Year 1 Year 2 Year 3 Year 4
Fear of delivery
![Page 6: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/6.jpg)
© SAP 2012 | 6
WHERE ARE WE TODAY?
![Page 7: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/7.jpg)
© SAP 2012 | 7 COMPLEMENTING LEAN & SCRUM WITH AGILE ENGINEERING
Das Comeback (FOCUS 22/2012, S. 122ff.)
![Page 8: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/8.jpg)
© SAP 2012 | 8
AGILE = “ABLE TO MOVE QUICKLY & EASILY”*
*) Definition from Longman Dictionary of Contemporary English
![Page 9: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/9.jpg)
© 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
?
![Page 10: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/10.jpg)
© SAP 2012 | 10
…SO, WHAT DOES AGILE MEAN FROM A BUSINESS PERSPECTIVE?
![Page 11: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/11.jpg)
© 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
![Page 12: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/12.jpg)
© SAP 2012 | 12
WHY CAN„T WE JUST MAKE A MASTER PLAN?
![Page 13: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/13.jpg)
© 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
.
.
.
![Page 14: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/14.jpg)
© SAP 2012 | 14 FIXED SCOPE IS AN ILLUSION AND PROMISES FALSE SAFETY
Teams Timelines
Scope
fixed
variable
![Page 15: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/15.jpg)
© SAP 2012 | 15 PROCESS-WISE, SOFTWARE DEVELOPMENT IS DIFFERENT
Creative
Repetitive
Intangible Physical
![Page 16: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/16.jpg)
© SAP 2012 | 16
WHY DO WE LIKE SCRUM?
![Page 17: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/17.jpg)
© SAP 2012 | 17 SCRUM REDUCED RISKS DRAMATICALLY
Retrospectives
Split organization into teams
Split work
Split time
Deliver more frequently
Risk
Risk
![Page 18: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/18.jpg)
© SAP 2012 | 18 SCRUM IS PEOPLE-CENTRIC AND FOSTERS TEAM WORK
Personal Responsibility
Partnership
Shared Purpose
Mutual Trust
Collaboration Mindset
![Page 19: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/19.jpg)
© 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
![Page 20: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/20.jpg)
© SAP 2012 | 20 COMPLEMENTING SCRUM WITH ENGINEERING PRACTICES
![Page 21: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/21.jpg)
© 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
![Page 22: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/22.jpg)
© 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
![Page 23: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/23.jpg)
© SAP 2012 | 23
…BUT, WHAT ABOUT THE ECONOMIC VIEW?
![Page 24: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/24.jpg)
© SAP 2012 | 24 THE LEAN CANVAS TAKES AN ECONOMIC VIEW
Source: Ash Maurya (2012) – Running Lean
![Page 25: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/25.jpg)
© SAP 2012 | 25 VALIDATED LEARNING INCLUDING THE ECONOMIC VIEW
Source: Eric Ries (2011) – The Lean Startup
…but beware of ”vanity metrics”!
Iterate…
![Page 26: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/26.jpg)
© 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?
![Page 27: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/27.jpg)
© SAP 2012 | 27
WHERE DO REQUIREMENTS COME FROM?
![Page 28: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/28.jpg)
© SAP 2012 | 28 SCIENTIFIC ANALYSIS WITH A DEDUCTIVE APPROACH
Idea White paper Detailed specification
![Page 29: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/29.jpg)
© SAP 2012 | 29
HOW DOES DESIGN WORK?
![Page 30: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/30.jpg)
© SAP 2012 | 30 DIVERGING & CONVERGING TO UNDERSTAND THE PROBLEM
„Wicked problem„
Solvable problem
Less wicked problem
Development
![Page 31: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/31.jpg)
© SAP 2012 | 31
WHAT IS DESIGN THINKING?
![Page 32: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/32.jpg)
© 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)
![Page 33: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/33.jpg)
© SAP 2012 | 33 DESIGN THINKING PILLARS
3. Approach
2. Space
1. People
![Page 34: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/34.jpg)
© SAP 2012 | 34 SAP‘S DESIGN THINKING APPROACH
Address the right question …and create the right solution
Customers Stakeholders
Customers Stakeholders
![Page 35: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/35.jpg)
© SAP 2012 | 35
HOW DO WE COMBINE DESIGN & DEVELOPMENT TODAY?
![Page 36: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/36.jpg)
© SAP 2012 | 36 COMBINING DESIGN AND DEVELOPMENT IN PRACTICE
User Research Teams
Synthesis
Product Vision
Product Backlog
User Story Mapping
Personas Prototyping
![Page 37: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/37.jpg)
© SAP 2012 | 37 DESIGN & DEVELOPMENT ARE COMPLEMENTARY
Design (Thinking) (Lean) Development
Set of shared values and principles
![Page 38: Scrum Day 2012 Keynote: Combining Design and Development](https://reader033.vdocuments.mx/reader033/viewer/2022051515/558c187cd8b42aca718b4627/html5/thumbnails/38.jpg)
Thank You!
Contact Information: Martin Fassunge SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf T: +49 6227 7-47474 [email protected]
Dr. Tobias Hildenbrand SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf T: +49 6227 7-47474 [email protected]