High-performing Doesn't Happen Overnight, It Takes Practice

@agilebaconbeer @teamsinprogress
@GoAgileCamp
#AgileCamp2017
2017
High-performing Doesn’t
Happen Overnight,
It Takes Practice
Matt Badgley
VersionOne/CollabNet

I’m a person that really enjoys helping
others make great software, have fun,
and discover new ways to innovate. By
the way, I like to also hang with my BFFW,
fish, anything with my dogs, enjoy beer,
and smoke meat.
I work as a Services Director, Agile Coach,
Product Consultant, and constant learner
and frequent screw-up.
matt.badgley@versionone.com
@teamsinprogress @agilebaconbeer
www.agilebacon.com
www.linkedin.com/in/mattbadgley
Matt Badgley

@agilebaconbeer @teamsinprogress@agilebaconbeer @teamsinprogress

Areas we (or I) need to #suckless
are ____________
• What are you or your team(s) currently struggling with?
• e.g. Our sprint planning is so painful, Conversations are forced
between the team and business, Team members don’t escalate
early, Estimates rule our lives
• On the back of the hand-out, write two-three “struggles”
or things to #suckless at, be sure to give enough details so
that others can understand
3minutes

Product Backlog
Sprint Backlog
Burndown Chart
Story Writing
Release Planning
Estimation
Impediments Management
Scrum-of-Scrums
Sprint Planning
Daily Standup
Sprint Review
Sprint Retrospective
Sprint Demo
Sit Together
Whole Team
Informative Workspace
Sustainable Pace
Energized Work
40-hour Work Week
Pair Programming
Weekly Cycle
Quarterly Cycle
Slack
10 minute build
Continuous Integration
Test First Programming
Incremental Design
Planning Game
System Metaphor
Simple Design
Coding Standards
Refactoring
Limit Work-in-Progress
Manage Flow
Visualize
Make Policies Explicit
Implement Feedback
Improve Collaboratively
Automate Testing using APIs
Loosely Coupled Architecture
Deliver in Small Batches
Transparency
Eliminate Overhead
Dedicated Teams
Minimal Viable Product
Minimize Hand-offs, Maximize Flow
Economic Framework
Solution Intent
Lean Portfolio Management
Program Increment Planning
Cadence & Synchronization
Objective Based Milestones
System Demo
Inspect & Adapt
Lean Budgets
Hypothesis Driven
Story Mapping
BDD/ATDD
Lean UX
CI/CD

Product Backlog
Sprint Backlog
Burndown Chart
Story Writing
Release Planning
Estimation
Scrum-of-Scrums
Sprint Planning
Daily Standup
Sprint Review
Sprint Demo
Sit Together
Whole Team
Sustainable Pace
Energized Work
40-hour Work Week
Pair Programming
Weekly Cycle Quarterly Cycle
Slack
10 minute build
Incremental Design
Planning Game
System Metaphor
Simple Design
Coding Standards
Refactoring
Manage Flow
Visualize
Make Policies Explicit Implement Feedback
Transparency
Eliminate Overhead
Dedicated Teams
Minimal Viable Product
Minimize Hand-offs, Maximize Flow
Economic Framework
Solution Intent
System Demo
Inspect & Adapt
Lean Budgets
Hypothesis Driven
Story Mapping
BDD/ATDD
Lean UX
CI/CD
Simplicity--the art of maximizing the
amount of work not done--is essential.
Our highest priority is to satisfy the
customer through early and continuous
delivery of valuable software.
Welcome changing requirements, even
late in development. Agile processes
harness change for the customer's
competitive advantage.
Deliver working software
frequently, from a couple of
weeks to a couple of months,
with a preference to the
shorter timescale.
Business people and developers
must work together daily
throughout the project. Build projects around
motivated individuals. Give
them the environment and
support they need, and
trust them to get the job
done.
The most efficient and
effective method of
conveying information to
and within a development
team is face-to-face
conversation.
Working software is the primary
measure of progress.
Agile processes promote sustainable
development. The sponsors,
developers, and users should be able
to maintain a constant pace
indefinitely.
Continuous attention to
technical excellence and
good design enhances
agility.
The best architectures, requirements,
and designs emerge from self-
organizing teams.
At regular intervals, the
team reflects on how to
become more effective,
then tunes and adjusts its
behavior accordingly.
Eliminate Waste
Build Quality In
Create Knowledge
Defer Commitment
Deliver Fast
Respect
People
Optimize the Whole
Application and End-User
Focus
Collaboration
Performance Orientation
Development Speed
Service Orientation
Automation
Monitor Everything
Take an Economic View
Apply Systems Thinking
Assume variability; preserve
options
Build incrementally with fast, integrated
learning cycles
Base milestones on
objective evaluation of
working systems
Visualize and limit WIP, reduce
batch sizes, and manage queue
lengths
Apply cadence, synchronize
with cross-domain planning
Unlock the intrinsic motivation of knowledge workers
Decentralize decision-making

Product Backlog
Sprint Backlog
Burndown Chart
Story Writing
Release Planning
Estimation
Scrum-of-Scrums
Sprint Planning
Daily Standup
Sprint Review
Sprint Demo
Sit Together
Whole Team
Sustainable Pace
Energized Work
40-hour Work Week
Pair Programming
Slack
10 minute build
Incremental Design
Planning Game
System Metaphor
Simple Design
Coding Standards
Refactoring
Manage Flow
Visualize
Transparency
Eliminate Overhead
Dedicated Teams
Minimal Viable ProductMinimize Hand-offs, Maximize Flow
Economic Framework
Solution Intent
System Demo
Inspect & Adapt
Lean Budgets
Hypothesis Driven
Story Mapping
BDD/ATDD
Lean UX
CI/CD
Simplicity--the art of maximizing
the amount of work not done--is
essential.
customer through early and
continuous delivery of valuable
software.
Welcome changing requirements,
even late in development. Agile
processes harness change for the
customer's competitive advantage.
shorter timescale.
Business people and
developers must work
together daily throughout
the project.
Build projects around motivated individuals.
Give them the environment and support they
need, and trust them to get the job done.
effective method of
conveying information
to and within a
development team is
face-to-face
conversation.
Working software is the primary measure of
progress.
Agile processes promote sustainable development. The
sponsors, developers, and users should be able to
maintain a constant pace indefinitely.
Continuous attention to technical excellence
and good design enhances agility.
The best architectures,
requirements, and designs
emerge from self-organizing
teams.
At regular intervals, the team reflects on how to become more effective,
then tunes and adjusts its behavior accordingly.
Eliminate Waste
Build Quality In Create Knowledge Defer Commitment
Deliver Fast
Respect People Optimize the Whole
Application and End-User Focus
Collaboration
Development Speed
Service Orientation
Automation
Monitor Everything
options
Build incrementally with fast,
integrated learning cycles
Base milestones on
working systems
Visualize and limit WIP,
reduce batch sizes, and
manage queue lengths
Apply cadence, synchronize with
cross-domain planning
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Openness
Courage
Respect
Focus
Commitment
Culture
Collaboration
Automation
System-
thinking
Decreasing-silos
Measurement
Trust
Feedback
Communication
Built-in Quality
Alignment
Transparency
Program Execution

[High-performing story]
What is a high-performing team?

In my experience, a
high-performing team
is one that
___________________
Source: http://blog.dilbert.com

A good team … believes in doing Quality,
consistent work.

A good team … is customer focused and makes users great.

A good team … has shared core values,
a noble cause, and
common
virtues.
Recommended reading:

A good team …
possesses these key
attributes.

A good team … is continuously improving,
and working to #suckless.

To get better through practice …
1. You must have tenacity to get better … you have to
possess grit.
2. You must have the right environment to practice.
3. You have to practice deliberately
(a.k.a. leverage deliberate practice).

Grit
A passion and perseverance for long-term goals.

Environment
“My job as a manager is to create a
fertile environment, keep it healthy,
and watch for the things that
undermine it.”
- Ed Catmull, Creativity, Inc.

Deliberate Practice
“…deliberate practice sounds like a very
organized, canonized, or codified, way of
working really, really hard.”
- Stephen Dubner, host of Freakonomics Radio

Deliberate Practice is not …

Six Steps to Deliberate Practice
1. Get Motivated
2. Set specific, realistic goals
3. Break out of your comfort
zone
4. Be consistent and persistent
5. Seek feedback
6. Take time to
recover
Source: https://medium.com/the-crossover-cast/get-better-at-anything-6-steps-of-deliberate-practice-19830bfc9460

Product Backlog
Sprint Backlog
Burndown Chart
Story Writing
Release Planning
Estimation
Scrum-of-Scrums
Sprint Planning
Daily Standup
Sprint Review
Sprint Demo
Sit Together
Whole Team
Sustainable Pace
Energized Work
40-hour Work Week
Pair Programming
Slack
10 minute build
Incremental Design
Planning Game
System Metaphor
Simple Design
Coding Standards
Refactoring
Manage Flow
Visualize
Transparency
Eliminate Overhead
Dedicated Teams
Minimal Viable ProductMinimize Hand-offs, Maximize Flow
Economic Framework
Solution Intent
System Demo
Inspect & Adapt
Lean Budgets
Hypothesis Driven
Story Mapping
BDD/ATDD
Lean UX
CI/CD
Simplicity--the art of maximizing
the amount of work not done--is
essential.
customer through early and
continuous delivery of valuable
software.
Welcome changing requirements,
even late in development. Agile
processes harness change for the
customer's competitive advantage.
shorter timescale.
Business people and
developers must work
together daily throughout
the project.
Build projects around motivated individuals.
Give them the environment and support they
need, and trust them to get the job done.
effective method of
conveying information
to and within a
development team is
face-to-face
conversation.
Working software is the primary measure of
progress.
Agile processes promote sustainable development. The
sponsors, developers, and users should be able to
maintain a constant pace indefinitely.
Continuous attention to technical excellence
and good design enhances agility.
The best architectures,
requirements, and designs
emerge from self-organizing
teams.
At regular intervals, the team reflects on how to become more effective,
then tunes and adjusts its behavior accordingly.
Eliminate Waste
Build Quality In Create Knowledge Defer Commitment
Deliver Fast
Respect People Optimize the Whole
Application and End-User Focus
Collaboration
Development Speed
Service Orientation
Automation
Monitor Everything
options
Build incrementally with fast,
integrated learning cycles
Base milestones on
working systems
Visualize and limit WIP,
reduce batch sizes, and
manage queue lengths
Apply cadence, synchronize with
cross-domain planning
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Openness
Courage
Respect
Focus
Commitment
Culture
Collaboration
Automation
System-
thinking
Decreasing-silos
Measurement
Trust
Feedback
Communication
Built-in Quality
Alignment
Transparency
Program Execution
How does Deliberate Practice help
us #suckless at all this stuff?

Deliberate Practice to #suckless
• Working in small groups (1..4), pick one person’s ”struggle”
that everyone can relate to and is closer to root cause.
• Using that “struggle” as an Area to Improve, complete as
much of the Practice Canvas as possible.
• Start with brainstorming Skills and Practice/Games/Activities
• Time permitting, start another …
7minutes

@agilebaconbeer @teamsinprogress@agilebaconbeer @teamsinprogress
Questions?

When I was young and free and my imagination had no limits, I
dreamed of changing the world. As I grew older, and wiser, I discovered
the world would not change, so I shortened my sights somewhat and
decided to change only my country.
But it, too, seemed immovable.
As I grew into my twilight years, in one last desperate attempt, I settled
for changing only my family, those closest to me, but alas, they would
have none of it.
And now, as I lie on my deathbed, I suddenly realize: If I had only
changed myself first, then by example I would have changed my family.
From their inspiration and encouragement, I would then have been able
to better my country, and who knows, I may have even changed the
world.
Inscribed on the tomb of an Anglican Bishop in Westminster Abbey (1100 A.D.)

Thank You
I believe in working with teams to help them get better, learn, and be
successful in building stuff while having fun.
My Purpose …
@agilebaconbeer

High-performing Doesn't Happen Overnight, It Takes Practice

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à High-performing Doesn't Happen Overnight, It Takes Practice

Similaire à High-performing Doesn't Happen Overnight, It Takes Practice (20)

Plus de Matt Badgley

Plus de Matt Badgley (9)

Dernier

Dernier (14)

High-performing Doesn't Happen Overnight, It Takes Practice