agile & lean in context
DESCRIPTION
What is the relationship between Lean, Agile, and Scrum?TRANSCRIPT
Agile & Lean in Context
Presented By: Chad Pavliska
Topic
• What is the difference between Lean, Agile, and Scrum?
• Where did these terms come from?
Quick Bio - Chad Pavliska
• 15 years in technology industry (10 in development)
• “Product Coach” - Ship product!
• Freelance & Jackrabbitmobile
• Mobile specialty
• Follow me @chadpav
• Email: [email protected]
– Chad Pavliska
“I do manage projects but don’t call me a project manager.”
Agile Experience• 2002 - Software Developer / DBA (Learned
XP)
• 2007 - First exposed to Scrum (failed)
• 2009 - Successful implementation
• 2012 - Lean Startup, Studied history of Lean Manufacturing, Agile, and Scrum
• Present - 2 Scrum projects in progress
Lean -> Agile Timeline
• 1950’s - Toyota Production System (TPS) (Taiichi Ohno)
• 1990’s - Westerners begin to document TPS and label it Lean Manufacturing (John Krafcik)
• mid-90’s - Several “light” methodologies using lean principles exist in parallel (Scrum, XP, Crystal, etc.)
• 2001 - Agile Manifesto written to document similarities in software development methodologies
Lean Manufacturing
– W. Edwards Deming (circa 1950)
“…the bulk of the causes of low quality and low productivity belong to the
system and thus lie beyond the power of the work force.”
Toyota Production System
NUMMI Plant
… now a Tesla Factory
May 2010 - Model S production
– Wiki page on Lean Manufacturing
“Lack of understanding is one of the key reasons that a large share of lean manufacturing projects in the west fail
to bring any benefit.”
AGILE
- Chazz, Blades of Glory (2007)
Agile Software Development
• 2001 - 17 software developers gathered in Snowbird, Utah
• Goal: Outline similarities between different “lightweight” methods (Scrum, XP, Crystal, etc.)
• Published The Agile Manifesto
• Four Agile Values
• Twelve Agile Principles
– David Hawks (@agileaustin), CEO of Agile Velocity
“Agile is a set of values and principles, it doesn’t define your process.”
Four Agile Values• Individuals and interactions over
processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
* While there is value in the items on the right, we value the items on the left more.
Twelve Principles (paraphrased)
1. Deliver value early
2. Embrace change
3. Deliver frequently
4. Collaborate (business and technical)
5. Motivated individuals
6. Face-to-face conversation
Twelve Principals - Cont.
7. Working software is primary measure of progress
8. Sustainable development (pace)
9. Technical excellence
10.Maximize work not done (simplify)
11.Self-organizing teams
12.Reflect and Adapt regularly
– Martin Fowler
“…lean and agile are deeply intertwined in the software world. You can't really talk about them being alternatives, if
you are doing agile you are doing lean and vice-versa.”
SCRUM
Scrum Framework
• Early ’90’s - Schwaber and Sutherland began experimenting w/ techniques that evolved into Scrum
• 1995 - Scrum methodology paper (Ken Schwaber & Jeff Sutherland)
• 2001 - Agile Software Devlopment with Scrum Book (Schwaber & Mike Beedle)
Scrum Theory• Founded on empirical process control
theory (Empiricism)
• Three pillars of empiricism:
• Transparency
• Inspection
• Adaptation
Scrum Events
• 4 Formal Events:
• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective
The Scrum Team
• Product Owner
• The Development Team
• Scrum Master
Scrum Artifacts
• Product Backlog
• Sprint Backlog
• Definition of “Done”