Embed Size (px)
DESCRIPTION
Understand the underlying principles and practices of Scrum. This workshop explains the history of Scrum, the differences of plan-driven defined development approaches and how progress can be easily measured. Come learn and understand through theory and joyful exercises the power of Scrum.
Citation preview
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.
28-Mar-14 effective agile. 3
Plan
Analyze
Design
Code
Test
Release
28-Mar-14 effective agile. 4
Work is organized
by activity
Big Batches
28-Mar-14 effective agile. 5
Is this the right
approach for software
development?
Big Batches
28-Mar-14 effective agile. 6
Scientific ManagementIs this the right
approach for software
development?
28-Mar-14 effective agile. 7
Scientific Management
28-Mar-14 effective agile. 8
28-Mar-14 effective agile. 9
Simple Complicated
Complex
Chaos
Req
uir
eme
nts
Technologyclose to certainty
far from certainty
clo
se t
o
agre
em
ent
far
fro
m
agre
em
ent
Simple
Complicated
Chaos
Complex
SenseCategorizeRespond
SenseAnalyzeRespond
ProbeSense
Respond
Best Practices
Good PracticesEmergent
ActSense
Respond
Novel
(source: Dave Snowden, IBM)
Cynefin
Complexity
Stacey Graph
(source: Ralph Stacey, University of Herfordshire)
DefinedEmpirical
28-Mar-14 effective agile. 10
Demming Cycle
35% of Requirements Change
25-Nov-2011 effective agile. 11
>60% of features are rarely or never used
(source: Standish Group)
25-Nov-2011 effective agile. 12
Value
28-Mar-14 effective agile. 13
Original Vision
Original Solution
Ad
dit
ion
al V
alu
e
Welcoming change/
Coping with Complexity
28-Mar-14 effective agile. 14
28-Mar-14 effective agile. 15
28-Mar-14 effective agile. 16
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
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
28-Mar-14 effective agile. 19
Higher Chance of Success
28-Mar-14 effective agile. 20
(source: ADM)
DefinedEmpirical
Edge of Chaos
Complexity
Low Medium High
Probality of Success
Why a higher Change?
28-Mar-14 effective agile. 21
(source: ADM)
Visibility Ability to Change
Business Value Risk
Waterfall Scrum
• 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
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)
Roles, Artifacts and Events
in Action
28-Mar-14 effective agile. 24
RolesProduct OwnerDevelopment TeamScrum Master
ArtifactsProduct BacklogSprint BacklogIncrement
EventsSprint PlanningSprintDaily ScrumSprint ReviewRetrospective
Product Backlog
Sprint Planning Meeting
Sprint Backlog
Sprint
Increment
Review
Retrospective
Daily Scrum
ScrumMaster
(source: ADM)
Potentially Releasable
28-Mar-14 effective agile. 25
Ensure Quality
Dev
ReleasePlannin
gDesign ReleaseAnalysis Dev Testing
Planning Design ReleaseAnalysis Testing
Design Dev Testing Release
100%
50% 40%
Planning
Design ReleaseAnalysis Dev Testing
Planning
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
FunctionalRelease FR FR
FR
FR
FR
FR
FR
Dev
FR
V1 © 2012 Ralph Jochameffective agile.
www.effectiveagile.com
Stop
(Source: Gerald Weinberg, Quality Software Management: Systems Thinking)
Cost of fixing a Bug
Construction
Detailed Design
Architecture
Requirements
RequirementsArchitecture
Detailed DesignConstruction
Maintenance
Construction
Detailed Design
Architecture
Requirements
25-Nov-2011 effective agile. 27
(source: Barry Boehm “Equity Keynote Address” March 19, 2007)
28-Mar-14 effective agile. 28
Reporting
<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
28-Mar-14 effective agile. 30
Questions?
28-Mar-14 effective agile. 31
Ralph Jocham www.effectiveagile.com
effective agile. [email protected]
@rjocham
25-Nov-2011 effective agile. 32
![Phenomenology, Empiricism, and Science · 1. Husserl’s Critique of Empiricism “[Empiricism] destroys the possibility of the rational justification of mediate knowledge, and so](https://img.pdfslide.us/doc/110x75/5e82c34a6d2ded2336153c37/phenomenology-empiricism-and-1-husserlas-critique-of-empiricism-aoeempiricism.jpg)
