The document presents the concepts of empirical versus defined processes in software development, particularly focusing on Scrum and Agile methodologies. It details the roles, artifacts, and events in Scrum, highlights the advantages of empirical approaches over defined ones, and discusses the changing nature of software requirements. Additionally, it mentions the experiences of Ralph Jocham and the significance of adaptability in project management.

1. Empericism
with Scrum
effective agile.Ralph Jocham ralph.jocham@effectiveagile.com

2. Ralph Jocham
• Started as programmer; discovered process as a problem early on
• First Unified Process with UML
• Agile since 2000 with XP
• Scrum in 2003
• Oracle, LinkedIn, Roche, Google, The Gap, Swisscom, Texas Instruments, Siemens Medical,
ThoughtWorks, JPMorganChase
• Did come around, different cultures and domains
• Founder of effective agile.
• Trainer with
effective agile.

3. 28-Mar-14 effective agile. 3
Plan
Analyze
Design
Code
Test
Release

4. 28-Mar-14 effective agile. 4
Work is organized
by activity
 Big Batches

5. 28-Mar-14 effective agile. 5
Is this the right
approach for software
development?
Big Batches

6. 28-Mar-14 effective agile. 6
Scientific
Management
Is this the right
approach for software
development?

7. 28-Mar-14 effective agile. 7
Scientific Management

8. 28-Mar-14 effective agile. 8

9. 28-Mar-14 effective agile. 9
Simple Complicated
Complex
Chaos
Requirements
Technologyclose to
certainty
far from
certainty
closeto
agreement
farfrom
agreement
Simple
Complicated
Chaos
Complex
Sense
Categorize
Respond
Sense
Analyze
Respond
Probe
Sense
Respond
Best Practices
Good PracticesEmergent
Act
Sense
Respond
Novel
(source: Dave Snowden, IBM)
Cynefin
Complexity
Stacey Graph
(source: Ralph Stacey, University of Herfordshire)
DefinedEmpirical

10. 28-Mar-14 effective agile. 10
Demming Cycle

11. 35% of Requirements Change
25-Nov-2011 effective agile. 11

12. >60% of features are rarely or never used
(source: Standish Group)
25-Nov-2011 effective agile. 12

13. Value
28-Mar-14 effective agile. 13
Original Vision
Original Solution
AdditionalValue
Welcoming change/
Coping with Complexity

14. 28-Mar-14 effective agile. 14

15. 28-Mar-14 effective agile. 15

16. 28-Mar-14 effective agile. 16

17. 28-Mar-14 effective agile. 17
Defined
Waterfall (Defined)
Plan for the entire
project up-front
V-Model
Hermes MIL-STD-2167
GAM-T-17
JSP-188
MIL-STD-498

18. Defined vs Emperical
28-Mar-14 effective agile. 18
Scrum (Empirical)
Waterfall (Defined)
Plan for the entire
project up-front
Plan a little for the
entire project and then
a little for each Sprint
(source: effective agile)
intern
extern
intern
extern
intern
extern

19. 28-Mar-14 effective agile. 19

20. Higher Chance of Success
28-Mar-14 effective agile. 20
(source: ADM)
Defined
Empirical
Edge of
Chaos
Complexity
Low Medium High
Probality of
Success

21. Why a higher Change?
28-Mar-14 effective agile. 21
(source: ADM)
Visibility Ability to Change
Business Value Risk
Waterfall Scrum

22. • Scrum (n): A framework within which
people can address complex problems,
and productively and creatively develop
products of the highest possible value.
(source: ADM)
A simple Definition of Scrum
28-Mar-14 effective agile. 22

23. Framework
28-Mar-14 effective agile. 23
Roles
• Product Owner
• Dev Team
• Scrum Master
Artifacts
• Increment
• Product
Backlog
• Sprint Backlog
Events
• Sprint
• Sprint Planning
• Daily Scrum
• Sprint Review
• Retrospective
(source: ADM)

24. Roles, Artifacts and Events
in Action
28-Mar-14 effective agile. 24
Roles
Product Owner
Development Team
Scrum Master
Artifacts
Product Backlog
Sprint Backlog
Increment
Events
Sprint Planning
Sprint
Daily Scrum
Sprint Review
Retrospective
Product
Backlog
Sprint
Planning
Meeting
Sprint
Backlog
Sprint
Increment
Review
Retrospective
Daily
Scrum
ScrumMaster
(source: ADM)
Potentially
Releasable

25. 28-Mar-14 effective agile. 25
Ensure Quality

26. Dev
Release
Plannin
g
Design ReleaseAnalysis Dev Testing
Planning Design ReleaseAnalysis Testing
Design Dev Testing Release
100%
50% 40%
Plannin
g
Design ReleaseAnalysis Dev Testing
Plannin
g
Design ReleaseAnalysis Dev Testing
100%
Major Release
Major
Release
Major Release
Point Release
V1
Point
Release V4
Point Release
V1.5
Point Release
V4.2
Major Release
FR
Functional
Release FR FR
FR
FR
FR
FR
FR
Dev
FR
V1 © 2012 Ralph Jocham
effective agile.
www.effectiveagile.com
Stop
(Source: Gerald Weinberg, Quality Software Management: Systems Thinking)

27. Cost of fixing a Bug
Construction
Detailed Design
Architecture
Requirements
Requirements
Architecture
Detailed Design
Construction
Maintenance
Construction
Detailed Design
Architecture
Requirements
25-Nov-2011 effective agile. 27
(source: Barry Boehm “Equity Keynote Address” March 19, 2007)

28. 28-Mar-14 effective agile. 28
Reporting

29. <Name> Summary Sprint 5 (8 Jan 2014 – 21 Jan 2014) Release Burndown
Risks Quality
Good Found solution on how to persistent geo data
Bpttsra[Difficult Bootstrap JS is not as easy to program as assumed
sdfsDifferent JavaScript is an easy to use language and versatile
Done &
Releaseable
3

30. 28-Mar-14 effective agile. 30

31. Questions?
28-Mar-14 effective agile. 31

32. Ralph Jocham www.effectiveagile.com
effective agile. ralph@effectiveagile.com
@rjocham
25-Nov-2011 effective agile. 32