tuning and improving your agility
DESCRIPTION
Are you using agile practices but struggling? If so, you are not alone. Experienced agile practitioners know that some practices are more difficult than others, and most need tuning over time. If you are looking for ways to get more value or improve your skills, this session will pass your acceptance tests. David Hussman shares his coaching tools for improving and tuning practices including product planning, roadmapping, story writing, planning sessions, and stand up meetings. David divides the journey to deliver value into four essential areas: growing community and vision, planning releases and iterative delivery, delivering value, and continuing to improve and learn. For each area, David shares tools for evaluating the value you are receiving relative to the ceremony you are using. If your stand up lacks value or energy, learn new ideas for truly getting value instead of merely meeting and standing; standing is the easiest part.TRANSCRIPT
MH Half‐day Tutorial 6/3/2013 8:30 AM
"Tuning and Improving Your Agility"
Presented by:
David Hussman DevJam
Brought to you by:
340 Corporate Way, Suite 300, Orange Park, FL 32073 888‐268‐8770 ∙ 904‐278‐0524 ∙ [email protected] ∙ www.sqe.com
David Hussman DevJam
Working with companies of all sizes worldwide, David Hussman teaches and coaches the adoption of agile methods as powerful delivery tools. Sometimes he pairs with developers and testers; other times he helps plan and create product roadmaps. David often works with leadership groups to pragmatically use agile methods to foster innovation and a competitive business advantage. Prior to working as a full-time coach, he spent years building software in a variety of domains: audio, biometrics, medical, financial, retail, and education. David now leads DevJam, a company composed of agile collaborators. As mentors and practitioners, DevJam focuses on agility as a tool to help people and companies improve their software production skills. For more information, visit devjam.com.
4/28/2013
1
Tuning and Improving Your Agility
David Hussman - DevJam
DevJam coaches and produce products
Design
Deliver
Learn
DevJam Tunings Vary
4/28/2013
2
Today’s Session
Learning thru Story Telling
Inventorying Your Skills
Questioning The Status Quo
Evolving and Augmenting
What are your expectations?
Learning by Story Telling
4/28/2013
3
A bit about me …
Extremely Familiar
- practical and pragmatic -
Extremely Popular
4/28/2013
4
Prescriptive vs. Descriptive
“This is what you should do”
“This is what I have seen work”
Extremely Essential
Extremely Skeptical
``
`
Goals (Why) and Mechanics (How)
Creating Community (Common Vision)
Form Communities (Collaborative Chartering)
Develop Product (Personas - Story maps - Sketching)
Create an Eco-System (Iteration 0 - Common Workspace)
Delivery (Iterating)
Staying Connected (Standup - Common Workspace)
Tracking Progress (Task Walls - Burncharts - Velocity)
Technical Agility (CI / CD - Test Driven - Refactoring)
Measuring Value (Acceptance Tests – User Testing)
Learning (Tuning)
Examining Progress (Product Reviews - User Feedback)
Learn and Improve (Retrospectives – Pivots – Replanning)
Discovery (Planning)
Product Releases (Opportunity - Effort - Dependencies)
Iterative Delivery (Iterations [cycles] - Kanban (flow))
What’s your story?
What’s your process?
4/28/2013
5
What Tools Do You Use? ( let’s inventory a bit )
The Agile Tool Chest
Test Driven Refactoring User Stories
Acceptance Tests
Sprints Product Backlogs Sprint Reviews
Sprint Backlog
Continuous Integration Evolutionary Design
Burndown
Burnup Velocity
Information Radiators
Iterations Releases
Personas Kanban Kaizen
Common Workspace
Mura
Cross Functional Teams Daily Scrum Meeting
Retrospectives
Iteration 0
Sustainable Pace
Chartering
Domain Driven Design
Collective Ownership
WIP
Pivot MVP Story Map
Planning Poker Story Points Story Telling
Technical Debt
Create a post it for each tool you use today
( values - principles - practices )
Then add tools you’d like to use in the future
What’s In Your Tool Set?
What’s Missing?
4/28/2013
6
Test Driven Refactoring User Stories
Acceptance Tests
Sprints Product Backlogs Sprint Reviews
Sprint Backlog
Continuous Integration Evolutionary Design
Burndown
Burnup Velocity
Information Radiators
Iterations Releases
Personas Kanban Kaizen
Common Workspace
Mura
Cross Functional Teams Daily Scrum Meeting
Retrospectives
Iteration 0
Sustainable Pace
Chartering
Domain Driven Design
Collective Ownership
WIP
Pivot MVP Story Map
Planning Poker Story Points Story Telling
Technical Debt
Why are you the tools you listed?
Dude’s Law: Value = Why / How
V= W H
V= W H
Qualifying Your Tool Set
Add a status of each
(w)orking - (c)hallenged - (b)roken
- (d)ead - (m)issing
Any tools you want to drop?
4/28/2013
7
What challenges do you face?
What questions do have ?
Questioning the Status Quo
What is commonly working?
What is commonly challenged?
4/28/2013
8
Checklist Thinking (and leaning)
Focusing on outcomes over process
Questioning Standups
What could you change?
What are trying to accomplish?
4/28/2013
9
Questioning Planning
Why are you planning?
When are you done?
Questioning Testing
4/28/2013
10
Are you learning or just coding?
Expected Outcome
Working Code Adaptive System
Which tests are you not writing?
How much testing is enough?
What’s your next investment?
Questioning Metrics
4/28/2013
11
What does this data tell you?
What’s missing?
What questions do you need to ask?
What data do you need?
Do your metrics teach?
0
20
40
60
80
100
120
140
160
1.1 1.2 1.3 2.1 2.2 2.3 3.1 3.2 3.3 4.1 4.2 4.3 5.1 5.2 5.3
To
tal
Po
ints
Iteration (Sprint) End
Release Burnup Chart
How do they help you improve?
4/28/2013
12
Questioning Retrospectives
Do people value your retrospective?
How do you know it is helpful?
Questioning and Measuring ( What real value are you getting? )
4/28/2013
13
Choose four practices to question
What value do you seek from each?
How can you improve each practice?
Do you need to change the “how”?
What are we questioning?
What do we want to improve?
Let’s Sample the Room
Evolving and Augmenting
4/28/2013
14
Avoiding Epistemic Arrogance
The difference between what you know
and what you think you know
Unnamed or Overlooked Evolution
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
Why iterate?
Why sprint?
What is the “evidence of success?”
What are the real measures?
4/28/2013
15
From Cycles to Flow
What’s a meaningful learning cycle?
What’s a meaningful product cycle?
From Continuous Integration …
… to Continuous Delivery
4/28/2013
16
What does this graph tell you?
0
20
40
60
80
100
120
140
0
1
2
3
4
5
6
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
# fails avg fix time (min)
Who cares?
Who doesn’t?
Continuous Delivery
4/28/2013
17
What are your integration challenges?
How would more deploys help?
From measuring story points …
… to measuring value delivered
Personas, Maps and Slices
Who wants to do what and why?
4/28/2013
18
How often do you engage users?
What do you do with user feedback?
Outstanding Questions?
Be an Epistemocrat
“… someone of epistemic humility, one who holds
her/ his own knowledge in greatest suspicion.”
4/28/2013
19
If you are looking for some help …
Learning is the New Currency
© 2012 DevJam - All rights reserved.
Questions?
________________________________________
Coaching and Developing Agility
www.devjam.com
© 2013 DevJam - All rights reserved.