1. Coaching Is More than
Telling People What to do
We build, delivery, learn and coach
We are Pragmatic coaches
1
2. Today we start with one little question?
Why?
Pair Up!
Designing Agility
Developing Products
Discovering and Delivering
2
3. From ideas …
Questioning and Learning
Design Selecting and Suggesting
Planning to Coach
Collaborative Chartering
Pragmatic Personas Develop
Story Mapping
Planning to Discover
Deliver Planning to Deliver
Setting the Stage
… to iteration
The larger journey …
Designing Agility
Getting Ready Developing Products
Discovering / Delivering
Continuous Delivery
Iterative Learning Getting Productive
Reflective Correction
Dealing w/ Adversity
Evolving the Process
Staying Productive
Maintaining Health
… to sustained production
Some call me “Dude”?
3
4. Some call me “Skeptic”
( skeptical not cynical )
How Much Process Is Enough?
Appropriate Ceremony
( process should promote learning )
4
5. 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)
Discovery (Planning)
Product Releases (Value - Effort - Dependencies)
Iterative Delivery (Iterations [cycles] - Kanban [flow])
Delivery (Iterating)
Staying Connected (Standup - Common Workspace)
Tracking Progress (Task Walls - Burncharts - Velocity)
Technical Agility (CI / CD - Test Driven - Refactoring)
Delivering Value (Acceptance Tests – User Testing)
Learning (Tuning)
Examining Progress (Iteration Reviews - User Feedback)
Reflect and Improve (Retrospective – Pivots)
Dude’s Law: Value = Why / How
W W
V= H V= H
Designing Agility
( tools for building your process )
5
6. Questioning and Learning
Selecting and Suggesting
Planning to Coach
for each do …
123
Who Why How
Why ask why?
Continuously test the status quo
6
7. Interviews, Assessment, Audience
Interviewers learn
Interrogators merely question
Who do you interview?
Sponsors and Investors
Teams and Individuals
7
8. How do you start
meaningful discussions?
What would you say to if asked …
What do you do well?
Where are your challenges?
8
9. Why change? - Why agile?
What, Where, When?
What are the constraints?
What will help, what will hinder?
Change is not free
( context matters )
9
10. Your First Interview
What is their current process?
What are the strengths and challenges?
What are their motives for change?
What constraints lie ahead?
Questioning and Learning
Selections and Suggestions
Planning to Coach
Where do you start?
( process - practices - projects)
10
11. Respectful Change Sticks
Lasting change happens with people and not to them
Which Process?
Kanban
People deliver, processes help
Which Practices?
Sprint Backlog Burndown
Sprint Reviews Product Backlogs
Daily Scrum Cross Functional Teams Sprints
Mura Test Driven Personas Iterations
Kanban Refactoring User Stories Releases
Kaizen Iteration 0 Acceptance Tests Velocity
Evolutionary Design Chartering Burnup
Continuous Integration Retrospectives
Domain Driven Design Common Workspace
Collective Ownership Information Radiators
Sustainable Pace
11
12. Intentional Selections
Collaborative Chartering
Burnup / Velocity
Common Workspace Acceptance Testing
Information Radiators Test Driven / Refactoring
Iteration 0 Continuous Integration
Community - Teams Iterative Delivery
Products - Planning Tuning - Improving
Product Backlogs Stand Up Meetings
Personas Product Reviews
User Stories / Story Maps Retrospectives
Discovery-Delivery Planning Continuous Feedback
Which projects?
Which products?
A Few Discussion Starters
12
13. What are the change constraints?
How much change is respectful?
Deeper Learning to Guide Suggestions
Which process or practices?
Which projects or products?
How big? How many locations?
How new? How much visibility?
Questioning and Learning
Selections and Suggestions
Planning to Coach
13
15. Ask - Listen - Repeat (playback)
“We have two ears and one mouth so we
listen twice as much as we speak”
Epictetus
Experiences Sell - Stories Stick
“This is what you should do”
Theory vs. Experience
Prescriptive vs. Descriptive
“This is what I have seen work”
Why have a coach?
15
16. Coaching helps …
teach practices
build community
promote learning
deliver real value
What does a coach do?
Productive coaching includes …
helping with customer and product discovery
_____________________________________________________
fostering real delivery and real measures
____________________________________________________
patterning reflective behavior
____________________________________________________
tracking continuous learning
16
17. … but the work is never ending
lead chartering sessions – help create story maps or build
backlogs – grow product ownership – promote acceptance
testing – connect with the investors and sponsors
____________________________________________________________________________
teach practices – lead planning sessions – start
conversations – foster honest feedback – pair with people –
promote test driven and refactoring – ensure value is
delivered – keeps the build alive & well
___________________________________________________________________________
attend retrospective reflective thinking – balance metrics
and intuition – resolve conflicts – create test driven
everything eco-systems – keep the community connected
and vibrant – helps connect with the outside world
Balance is essential!
( many new coaches blow up )
How will you coach (well)?
17
18. Create a Coaching Plan ( How )
Timeframe When
Locations/Tools Which
Practices What
Tests Why
Timeframe ( when )
Locations and Logistics ( which )
Which teams which locations?
What tools and why?
18
19. Interests and Constraints ( what )
Timeframe and Testing ( why )
Practice Tests (shu)
Product Tests (ha)
Learning Tests (ri)
What’s a Meaningful Coaching Plan?
When How long will be around?
Where Which projects or products?
What Which changes and why?
How What success measures?
19
