grows for executives

67
GROWS for Executives Jared Richardson @JaredRichardson Principal Consultant Agile Artisans

Upload: jaredrrichardson

Post on 16-Jul-2015

92 views

Category:

Software


1 download

TRANSCRIPT

GROWS for Executives

Jared Richardson@JaredRichardson

Principal ConsultantAgile Artisans

Who Am I?

Cofounder of GROWS Methodology

Author Ship It! and Career 2.0

Screencast editor PragProg.com

2nd public signatory of the Agile Manifesto

Started AgileRTP in 2007!

Coach

AgileArtisans.com

Jared Richardson

Outline

What is Agile?

What is GROWS?

What should I be doing?

Outline

What is Agile?

What is GROWS?

What should I be doing?

AgileManifesto.org

AgileManifesto.org

Individuals and interactions over processes and tools Working software over comprehensive documentation

Customer collaboration over contract negotiation Responding to change over following a plan

Which way?

flickr.com/photos/nkphillips/2865781749/

Outline

What is Agile?

What is GROWS?

What should I be doing?

Learning modelWorking model

Learning model: DreyfusWorking model: Intentional Experimentation

Learning Model

Dreyfus

Start

Familiar

Working

Smooth

Teaching

Dreyfus Model of Skills Acquisition

en.wikipedia.org/wiki/Dreyfus_model_of_skill_acquisition

Start

Familiar

Working

Smooth

Teaching

Dreyfus Model of Skills Acquisition

Steps

Recipes

Intuition

Stuck

Principles

Key Points

Skills don’t map

dilbert.com/strip/1990-09-13

Key Points

Beginners need steps

Working Model

Agile practices

Intentional Experimentation

Quick Overview

What does GROWS look like?

3 Rs

Rhythm

Right Thing (vision)

Right Way (craftsmanship)

RhythmScrum practices

Daily meetings

Iterations

Demos

Retrospectives

Teams find their own cadence

Right Thing

Vision

The Right Way

Technical Practices

Technical Practices

Version Control

Test First

Continuous Integration

Continuous Testing

Iteration (ship event or usable product)

Vision/ Initiatives/ Customers Product

Owner

Iteration

Retrospective

Demo

Planning Meeting

Daily Meetings Daily

Meetings

Steps

Principle

Feedback Loop

Long loops are bad

Short loops are good

Recognize loops

Shrink them

Neglected Feedback Loops

Architecture

Requirements

New features

Bug fixes

SCMDevelopers

Watch

Build

Unit Tests

Deploy to Dev

Integration Tests

First Look

Continuous Testing

On Demand Deploy to QA

Manual Testing

Requirements

Requirements

Write Code

The Traditional Approach

Demo

Rewrite

“Discussion”

Typically a confrontation &

argument

The demo forces a

discussion of the requirements

An isolated event, primarily worked by the

customer proxy

Demo

Write Code

Requirements

The Agile Approach

Rewrite

Before significant time

and $$ is invested

Discuss

Include the Golden Triad

Dev QA

Customer

ExperimentationLearn about software by writing software

Can’t study your way into experience

Like riding a bike

3+ experiments

Creating feedback loops

flickr.com/photos/schwar/6801765768

Requirements

Rewrite

Discuss

Development

Developers disagree on

which Javascript toolkit is best

Node.js

Bootstrap

Angular.js

Pick one

SOA

Monolithic

Peer to peer

Pick one

Developers disagree on

which architecture is best

Demo

Revise Rewrite Adjust

Frequent demos discover communication

failures early

Continue until you can demo

Discuss

Intentional Experimentation Study

Experiment

Learn

Decide! Learn

Learn Decide!

Two Paths

Outline

What is Agile?

What is GROWS?

What should I be doing?

Managers and Executives

Leadership

Vision

ShareCreate

Progress

EnsureTrack

Vision

Initiative

Themes

Epics

Features

Stories

Initiative

Themes

Epics

Features

Stories Days

Iterations

Months

Quarters

Years

Optional

Optional

Vision

3 to 5 initiatives

On the wall

Visible

Consumable

Electronic Tools

Hide size

Hide complexity

Great system of record

Great for remote teams

Work off the wall

Traceability

No orphan work

Everything fits in an initiative

Or we add a new initiative

Line of Sight

Everyone knows why

Everyone can understand

Commander’s Intent

No cogs in a machine

Progress

Track it

Progress

Don’t micromanage

Watch the appropriate level

Initiative

Themes

Epics

Features

Stories

Appropriate Level

Release Planning

Releases contain features

How many are ready to ship?

Releases contain features

Team Release Date

Release Theme

# Features

# Stories

Stories Complete

% Done

1

2

3

Release dateBurn Up Chart

Time

Features

Features in the release

Required rate of work

Will we hit our date?

Time

Features

ACTUAL rate of work

Burn Up Chart

Time

Features

ACTUAL rate of work

Feature Creep

Time

FeaturesACTUAL

rate of work

Observe Progress

On track

Behind

Unrealistic

The Solution

Reduce features

DO NOT focus on increased work

Good or Not?

Time

Features

ACTUAL rate of work

What’s the Fix?

Time

Features

How do I make the team work harder?

Longer Hours

Work Faster!Even Later

More Mistakes

Lots of Debugger

Time

What’s the Fix?

Time

Features

What’s the Fix?

Time

Features

What’s the Fix?

Time

Features

What Happens to Overloaded Planes?

flickr.com/photos/jameski/5322886899

Leadership

Vision Progress

Distinct training & practices for different rolesEmbraces the Dreyfus modelIntentional experimentationDynamicInclusive

GrowsMethod.com

AgileArtisans.com

[email protected]@GrowsMethod.com