The document describes Johanna Rothman's presentation titled "My Agile Suitcase" given at Agile 2013 in Nashville. Some of the key points included in her suitcase are: working tiny and proving results incrementally, getting work done through small batches, learning constantly, improving together, being trustworthy and predictable, and winning together. The presentation encourages attendees to define their own Agile suitcases by including important principles and practices. It also involves exercises where attendees work in pairs and groups to introduce their suitcases and identify shared and unique contents.
29. Work tiny – impressive results eventually
Check in
Ship live
Validate business impact
30. Prove it
Traditional or 1 star Agile 2+ star Agile
Dev’s job
• deliver software
Write ~8 bugs / man-day
Dev’s job
• Deliver software
• Demonstrate software does
what devs expect
Tools
• Mechanized refactoring
• Small steps, with reverting
• Test first
• Automated developer testing
• Design in units
• Design for testability
Write ~1 bug / 80 man-days
42. Work tiny
Prove it
Get done
Learn constantly
Improve together
Be trustworthy
Win together
My packing list generator
43. Pair or mob, 100%
Design small units
100% mechanized refactoring
Tests are specs; write them first
Finish and prove each step before
starting the next
1 process change / week (minimum)
Decentralize all decisions
Involve people directly
My current packing list
73. Most Value from Mindset/Culture, not Practices
~20% Benefit ~3X Benefit
•Ability to manage changing priorities
•Improved Visibility
•Increased Productivity
•Improved Quality
•Reduced Risk
•Customer Delight
•Joy at work
•Engagement
•Innovation, Creativity
•Continuous Learning
93. Define your common Agile Suitcase by
• Introducing each others suitcase
• Packing new suitcase(keep family tree)
Your Agile Suitcases
of two Pairs
11 1+ =
99. How much process is enough?
Test Driven
Refactoring
User Stories
Acceptance Tests
Sprints
Product Backlogs
Sprint Reviews
Sprint Backlog
Continuous Integration
Evolutionary Design BurndownBurnupVelocity
Information Radiators
IterationsReleases
PersonasKanban
Kaizen
Common Workspace
Cross Functional Teams
Daily Scrum
Retrospectives
Iteration 0
Chartering
Collective Ownership
WIP
Pivot
MVP
Planning Poker
Story Points
Technical Debt
Story Maps
Domain Driven Design
Don’t tell me what the book says Walter,
what practices do we really need man?
100. Don’t assume you know where you’re going
Getting Ready
Getting Productive
Staying Productive
Don’t assume you know how to get there
113. Epistemic Arrogance: “The difference between
what you know and what you think you know”
Staying Productive: Avoid Arrogance
114. Staying Productive: Frame and Reframe
Building for the future Building to adapt
Talking about code Talking about tests
Late integration Continuous Deployment
What’s required? What’s needed?
How many hours? How much product?
How much cost? How much opportunity?
(from) Last Millennia (to) This Millennia
How big? Too big?
Learning to estimate Learning from estimates
Completing work Validating value delivered
117. Define your common Agile Suitcase by
• Introducing each others suitcase
• Packing new suitcase(keep family tree)
Your Agile Suitcases
of two groups of four
11 1+ =