Coaching Is More than Telling People What to do Coaching Is More than Telling People What to do We...

20
1 Coaching Is More than Telling People What to do We build, delivery, learn and coach We are Pragmatic coaches

Transcript of Coaching Is More than Telling People What to do Coaching Is More than Telling People What to do We...

1

Coaching Is More than

Telling People What to do

We build, delivery, learn and coach

We are Pragmatic coaches

2

Why?

Today we start with one little question?

Pair Up!

Developing Products

Discovering and Delivering

Designing Agility

3

From ideas …

… to iteration

Selecting and Suggesting

Pragmatic Personas

Planning to Discover

Setting the Stage

Questioning and Learning

Planning to Coach

Collaborative Chartering

Story Mapping

Planning to Deliver

Develop

Design

Deliver

The larger journey …

… to sustained production

Developing Products

Iterative Learning

Dealing w/ Adversity

Maintaining Health

Designing Agility

Discovering / Delivering

Continuous Delivery

Reflective Correction

Evolving the Process

Getting Productive

Staying Productive

Getting Ready

Some call me “Dude”?

4

Some call me “Skeptic” ( skeptical not cynical )

How Much Process Is Enough?

Appropriate Ceremony ( process should promote learning )

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)

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)

Discovery (Planning)

Product Releases (Value - Effort - Dependencies)

Iterative Delivery (Iterations [cycles] - Kanban [flow])

Dude’s Law: Value = Why / How

V= W H

V= W H

Designing Agility

( tools for building your process )

6

Selecting and Suggesting

Planning to Coach

Questioning and Learning

2 3 1 Who Why How

for each do …

Why ask why?

Continuously test the status quo

7

Interviews, Assessment, Audience

Interviewers learn

Interrogators merely question

Who do you interview?

Sponsors and Investors

Teams and Individuals

8

How do you start

meaningful discussions?

What would you say to if asked …

What do you do well?

Where are your challenges?

9

Why change? - Why agile?

What, Where, When?

What are the constraints?

What will help, what will hinder?

Change is not free

( context matters )

10

What is their current process?

What are the strengths and challenges?

What are their motives for change?

What constraints lie ahead?

Your First Interview

Selections and Suggestions

Planning to Coach

Questioning and Learning

Where do you start? ( process - practices - projects)

11

Respectful Change Sticks

Lasting change happens with people and not to them

Which Process?

Kanban

People deliver, processes help

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

Retrospectives

Iteration 0

Sustainable Pace

Chartering

Domain Driven Design Collective Ownership

Which Practices?

12

Intentional Selections

Community - Teams

Products - Planning Tuning - Improving

Iterative Delivery

Collaborative Chartering

Common Workspace

Information Radiators

Iteration 0

User Stories / Story Maps

Product Backlogs

Personas

Discovery-Delivery Planning

Acceptance Testing

Burnup / Velocity

Continuous Integration

Test Driven / Refactoring

Retrospectives

Stand Up Meetings

Product Reviews

Continuous Feedback

Which projects?

Which products?

A Few Discussion Starters

13

How much change is respectful?

What are the change constraints?

Which process or practices?

Which projects or products?

How big? How many locations?

How new? How much visibility?

Deeper Learning to Guide Suggestions

Selections and Suggestions

Planning to Coach

Questioning and Learning

14

Planning, Coaching and Coaches

Who makes a good coach?

Good Coaches “Blink”

15

Ask - Listen - Repeat (playback)

“We have two ears and one mouth so we

listen twice as much as we speak”

Epictetus

Prescriptive vs. Descriptive

“This is what you should do”

“This is what I have seen work”

Experiences Sell - Stories Stick

Theory vs. Experience

Why have a coach?

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

17

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

… but the work is never ending

Balance is essential!

( many new coaches blow up )

How will you coach (well)?

18

Create a Coaching Plan ( How )

Timeframe

Locations/Tools

Practices

Tests

When

Which

What

Why

Timeframe ( when )

Which teams which locations?

What tools and why?

Locations and Logistics ( which )

19

Interests and Constraints ( what )

Timeframe and Testing ( why )

Practice Tests (shu)

Product Tests (ha)

Learning Tests (ri)

When How long will be around? Where Which projects or products? What Which changes and why? How What success measures?

What’s a Meaningful Coaching Plan?

20

What questions do you have?

Why design your own agility?

Learning is the New Currency

© 2012 DevJam - All rights reserved.

[email protected]