lanl methology comparison
TRANSCRIPT
-
7/31/2019 LANL Methology Comparison
1/37
RALLYS O F T W A R E
The BEST agile process
A discussion of XP, Scrum, Kanban and TSP
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
2/37
THERE ARE NOBEST
PRACTICES
ONLY GOOD
PRACTICES
IN CONTEXT
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
3/37
LARRYMACCHERONETwitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
4/37
RALLYS O F T W A R E
What is Agile?
VALUES
+
Controller System
Sensor
ReferenceMeasured
error
Measured output
System
input System output+
-
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
5/37
RALLYS O F T W A R E
TRADITIONAL/DMAIC
AGILE
PROCESS FEEDBACKFORMAL, AND CAN
BE HEAVY WEIGHTLIGHT BUT OFTEN
PRODUCT ANDDESIGN FEEDBACK
?EARLY, OFTEN,AND CLOSE TOTHE CUSTOMER
PLAN FEEDBACK ?FREQUENT BUT
QUICKDOMINANT VALUE PLANNING/CONTROL COLLABORATION
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
6/37
-
7/31/2019 LANL Methology Comparison
7/37RALLYS O F T W A R E
AGILE
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
8/37RALLYS O F T W A R E
How is agiledifferent?
REDUCTION IN
COORDINATIONCOSTS
(XP)
REDUCTIONIN
EVOLUTIONCOSTS
(KANBAN)
CHANGE INFEEDBACK
EMPHASIS(SCRUM)
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
9/37
XP
FOCUS:
ENGINEERING
PRACTICES
BEST AT:
REDUCTION INCOORDINATION
COSTS
Build the
thing
right!
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
10/37RALLYS O F T W A R E Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
11/37RALLYS O F T W A R E Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
12/37RALLYS O F T W A R E
XP: Reduces coordination costs
Continuous integration
Test driven development
Test-first design
Comprehensive testsuites
Simple design
Refactoring
System metaphor
Also: Coding standard
Whole team
Pair programming
Collective code ownership
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
13/37RALLYS O F T W A R E
Simple design
1. All tests must pass
2. No code is
duplicated
3. Code is self-
explanatory
4. No superfluous parts
exist
1. Passes tests (given TDD)
2. Minimizes duplication
3. Maximizes clarity (great
identifiers)
4. Has fewer elements
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
14/37
SCRUM
FOCUS:
PROJECT
MANAGEMENT
BEST AT:
CHANGE INFEEDBACK
EMPHASIS
Build the
right
thing!
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
15/37RALLYS O F T W A R E
Project
Inception
Discovery
Assessment
Iteration 0
Set up
Project
Infrastructure
TargetSystem
Iteration 1 Iteration 2 Iteration 3 Iteration n
AGILE
PROJECTLIFECYCLE
release 1 release n
Incremental delivery in time-boxed iterations
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
16/37RALLYS O F T W A R E
ProductBacklog
IterationBacklog
Iteration2-4
Weeks
DailyMeeting
ProductIncrement
MECHANICS
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
17/37
What did you
work on yesterday?
What are youcommitting to today?
Do you have anyimpediments?
STAND-UP
DAILY
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
18/37RALLYS O F T W A R E
POTENTIALLY
SHIPPABLE PRODUCT
Demo and get feedback EVERY SPRINT!!!
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
19/37RALLYS O F T W A R E
Burndown chart
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
20/37
ROLES
-
7/31/2019 LANL Methology Comparison
21/37
RALLYS O F T W A R E
Scrum framework
Product Increment
Daily
Daily Scrum Meeting
Planning Meeting
Revisit Release Plan
Review Product Backlog
Create Sprint Backlog
Commit to 2-4 weeks of work
Sprint Backlog Product Backlog Items assigned
to Sprint
Emergent list of estimated tasks
Vision
2-4 weeksSprint Retrospective
Product Backlog
Prioritized Features
desired by Customer
Sprint Review (Demo)
Release Planning
Burndown
Chart
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
22/37
KANBAN
FOCUS:
INCREMENTAL
IMPROVEMENT
BEST AT:
REDUCTION INEVOLUTION
COSTS
Go faster!
Get
better!
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
23/37
RALLYS O F T W A R E
A kanban
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
24/37
RALLYS O F T W A R E
Characteristics of the Kanban
Method
0. Start where you are
1. Visualize workflow
2. Limit WIP
3. Make management policies explicit
4. Manage flow
5. Improve collaboratively
Adapted from Kanban by David J. Anderson
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
25/37
0. Start where you are
-
7/31/2019 LANL Methology Comparison
26/37
RALLYS O F T W A R E
1. Visualize workflow
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
27/37
RALLYS O F T W A R E
1. Visualize workflow
-
7/31/2019 LANL Methology Comparison
28/37
RALLYS O F T W A R E
2. Limit work in process (WIP)
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
29/37
RALLYS O F T W A R E
3. Make policies explicit
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
30/37
-
7/31/2019 LANL Methology Comparison
31/37
RALLYS O F T W A R E
5. Improve collaboratively:measure outcomes
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
32/37
RALLYS O F T W A R E
5. Improve collaboratively:use data for decision making
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
33/37
RALLYS O F T W A R E
The Team Software Process
(TSP)
Where does it fit?
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
34/37
RALLYS O F T W A R E
How isagile
different?
Coordinationcosts
Evolution
costs
Feedback
emphasis
Aspects ofagile
Build thethingright
Build theright
thing
Improve
XP
Scrum
Kanban
Product
evolution also
(TSP, design,
design
patterns)
Twitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
35/37
RALLYS O F T W A R E
I recommend
1. Adopt XP engineering practices.
Add peer review.
Add design patterns and possibly more design/design review.
2. If you are doing product design and new to agile, adopt Scrum.
3. If you are doing IT work, or have a mature agile culture, or cant
accept all of Scrums changes, adopt Kanban.
4. If you need CMMi, adopt TSP.
5. If safety is critical, consider Crystal.
6. Buy Rally Software.
Twitter: @LMaccherone
LARRY
-
7/31/2019 LANL Methology Comparison
36/37
LARRYMACCHERONETwitter: @LMaccherone
-
7/31/2019 LANL Methology Comparison
37/37
RALLY
Credits
Kanban content. Rick
Simmons.([email protected])
Scrum content. Various at Rally Software.
XP content. Mostly from Kent Beck.
Simple design. Alistair McKinnell, Declan Whelan.
mailto:[email protected]:[email protected]:[email protected]:[email protected]