just enough: minimally viable agile
TRANSCRIPT
InfoDiagram: Kanban toolbox
Just Enough: Minimally Viable AgileTroy TuttleLean Agile [email protected]@troytuttle
KC PMI Professional Development Days
Speaker eval formsAgilehood open space!LWS KC1
Minimum Viable AgileBorrowing from the Product Development concept of MVP or Minimum Viable Product.
"The minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort."What is it?
Minimum Viable AgileMinimum Viable Agile is a search for Agile practices and ceremonies, informed by Lean and Agile theory, that produces the maximum amount of customer value, with the least amount of effort.
(Or Just Enough practices and ceremonies to be effective).What is it?
Agile Is?Burn Down ChartsSticky NotesCard WallsKanban BoardsStandup MeetingsRetrospectivesPair ProgrammingTDDSprint PlanningPlanning PokerVelocityStory PointsUser StoriesRelease PlanningEstimationTeam RoomDefinition of DoneWIP Limits
Write down the first few things that come to mind when you Complete the sentence
4
Agile Is
(Actual Google Search, BTW)
The Agile Dysfunction SpiralCoaching to helpimprove sprint planningSprint planningtakes longerManagementApplies pressureCulture of Blame creeps back inTeam works overtimeAre we really just after better sprints?
Amortized death marches
6
Cargo Cult (Agile)
Many early Agile attempts simply installed practices (recipes).Warning!Following recipes leads to Cargo Cult Agile
Practices divorced (mostly) from principlesLets install this process, or follow this recipe!
7
Mob Programming
8
Mob Programming: The original MVA?No Stand up meetingProduct Owner engagedDriver Navigators 15 min. rotationsEveryone takes a full lunch break!All the needed expertise in same roomAll the Brilliant PeopleWorking on the same problemAt the same timeOn the same computer
Mob Programming: The original MVA?Reduces or Eliminates: Standup or other alignment meetingsDetailed planning-only sessionsThe need for estimatesContext SwitchingBurn-down charts for performance trackingCode ReviewsIncreases: QualityCollaborationProductivitySatisfaction
10
Mob Programming: Why does it work?Sample timeline of a user story or requirement.Time2= wait timeweeks= touch time
weeks4 - 10
4 - 10
2
Customer RequestPrioritized in Product BacklogBacklog GroomingPlanning Intoa SprintStory Completed(tacit knowledge decay)
11
The Essence of AgileFocusLearningSimplicity(The art of the work not done.)(Collaboration is an outcome.)(Feedback loops enable improvements)Customer Value(We wouldnt be here otherwise.)
Building the right thing12
The Essence of AgileFocusLearningSimplicityCustomer ValueVisualize workWIP limitsCadenceRetrospectivesSmall batchesATDD and CIContinuous DeliveryMeasurement based planningEmergent Architecture
Track progress of Value, not tasksCustomer based metrics
Building the right thing13
Visceral Reaction Disclaimer We might cover some controversial topics.
14
Minimum Viable AgileLets take a closer look at some traditional Agile practices in need of improvement. Story Point based VelocitySprint Burn Downs
15
Story Points based Velocity
16
Story Points based VelocityCourtesy of Bennet ValletDirector of Development Siemens Health Services
Expected Distribution
Actual Distribution
Story Point based Velocity (refactored)
18
Planning in the world of MVAOption #1Hours-long traditional sprint planning meetings spent playing planningpoker and a team arguing about the difference between 2s and 3s. Option #2Short story slicing meeting where the focus is on understanding and slicing large stories.
Do we understand this story? If not, lets keep slicing.12358132140100Right-sizing the work
Planning in the world of MVAInput QDesignDevelopTestDone3
1
2
9
7
8
6
4
5
Cycle Time
Throughput10
14 days from this point5 stories per week
Sprint Burn Downs
Why do we assume this is the wrong place for this team to be?WorkTime
Nature of the Work
Manufacturing = repeatable processesProduct Development = one time processesOne-time processes are non-deterministic in nature
iPhone as an example software is a design process.Think about the software you use everyday at your job.. Email, calendar, web browser.Software dev is a non-deterministic activity, but we try to approach software projects in a deterministic fashion.Every attempt is a prototype!Its about writing a recipe vs. following a recipe.
22
Nature of the Work
Deterministic ApproachProject StartKnowledgeCompletePlanned Activity
Non-deterministic RealityProject StartKnowledgeComplete?What Customer Really WantsBetter KnowledgeProject Managers in the middle, pulling out their hair
Project problems are due to misunderstanding about the nature of software development.Software dev is a non-deterministic activity, but we try to approach software projects in a deterministic fashion.
23
Sprint Burn Downs
This is a problem.What exactly do we do now?WorkTimeIts not actionable!
Sprint Burn Downs (refactored)
Actionable Information!
Sprint Burn Downs (refactored)
(from ActionableAgile.com)
WorkTimeActionable Information!
Coaching Minimum Viable AgileTraining teams on estimation techniques or schemes.Focusing on making fixed scope, fixed time, commitment-based sprints work.Teaching teams how to use burn-down charts.Teaching teams to use Velocity to plan releases.
Less of:
Coaching Minimum Viable AgileCoaching teams to Limit their WIP to achieve better focus.Using simple and pragmatic time-boxes for better risk management.Teaching teams how to visualize their work.Coaching teams to conduct retrospectives and adopt continuous improvement.Planning releases based on historical measurements.
More of:
Where does Agile go from here?The first 15 years of Agile prompted us to ask: What are all the practices we need to adopt to be successful?Minimum Viable Agile prompts us to ask:Now, what practices do we change ordiscard to be successful?
Just Enough: Minimally Viable AgileTroy TuttleLean Agile [email protected]@troytuttle
KC PMI Professional Development Days Thank you!
Speaker eval formsAgilehood open space!LWS KC30