agile2016: stop using agile with waterfall goals: goal agility with okr

123
Stop Using Agile with Waterfall Goals: Goal Agility with OKR www.leanperformance.com Felipe Castro

Upload: felipe-castro

Post on 21-Apr-2017

2.356 views

Category:

Business


4 download

TRANSCRIPT

Page 1: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Stop Using Agile with Waterfall Goals: Goal Agility with OKR

www.leanperformance.com

Felipe Castro

Page 2: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR
Page 3: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipeLoosing my religion

Page 4: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

The Agile Manifesto is Wrong

Page 5: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

Agile was created for managing software projects.

As such, it is focused on managing deliverables (user

stories or features).

Page 6: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

There are no ceremonies for

tracking results.

Page 7: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

“Working Software”

Is not the same as

“Valuable Software”

The First Mistake

Page 8: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

“Working software is the primary measure of

progress.” Agile Manifesto

Page 9: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

“Working software is the primary measure of

progress.” Agile Manifesto✘

Page 10: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

“Our highest priority is to satisfy the customer

through early and continuous delivery

of valuable software.” Agile Manifesto

Page 11: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

Marty Cagan, Silicon Valley Product Group

“Teams today are all too often feature factories, with little regard for whether the

features actually solve business problems.”

Page 12: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Book Recommendation

Page 13: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

What is Value?

Page 14: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

Value is measured after

delivery

Page 15: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

User Stories are experiments

Page 16: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

Estimating Value

Is not the same as

Delivering Value

The Second Mistake

Page 17: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Decision by Committee

Commissioned Study by Forrester Consulting

Page 18: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Decision by Committee

Commissioned Study by Forrester Consulting

HiPPO

Personal Opinions

Page 19: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR
Page 20: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Ron KohaviMicrosoft, General

Manager, Analysis & Experimentation

Amazon, Ex-Director, Data Mining & Personalization

Page 21: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

“Humbling Statistics”•Only 1/3 of ideas created a statistically significant positive change.

•1/3 produced no significant difference.

•1/3 created statistically significant negative change.

•In general, 60-90% of ideas do not improve the desired metrics.

Page 22: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

User Stories are experiments

….with a low success rate

Page 23: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

Where is Empiricism when it comes to Value?

Page 24: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

Where is Inspect and Adapt?

Page 25: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

We need to move away from value estimation towards

value measurement.

Page 26: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

We need to evolve

Page 27: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

“Silicon Valley is Coming”

Jamie Dimon, CEO JP Morgan

Page 28: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Two Models

Page 29: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

What is your target?

Page 30: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Plan-Driven Vs. Data-Driven

Page 31: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Plan-Driven Vs. Data-DrivenDeterministic

Phase-Gate Waterfall

Command& Control

Iterative Agile

Distributed

Page 32: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

Why do we believe in plans?

Page 33: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Daniel Kahneman

Nobel Prize Winner

Page 34: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Planning Fallacy

We underestimate the time, costs, and risks of future actions.

While overestimating the benefits.

Page 35: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

The Plan-Driven model is still alive

Estimating without measuring is Plan-Driven

and a fallacy

Page 36: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Discovery-Driven Planning

Planning includes making a series of assumptions that are:

•Implicit •Non Validated

Page 37: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

“Your idea is just a series of non validated hypotheses.” Steve Blank

Page 38: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

“No plan survives contact with the enemy”. Helmuth von Moltke

(1800-1891)

Page 39: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Although we are using Agile tactically,

we are using waterfall for strategy and goal setting

Page 40: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Static Annual Planning 1

Page 41: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

“The only way it's all going to go according to plan

is if you don't learn anything.”

Kent Beck

Page 42: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Jeff Immelt CEO GE

Page 43: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

“In the digital age, sitting down once a year to do

anything is weird, is just bizarre.”

Jeff Immelt, CEO General Electric

Page 44: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Goals Cascade ?

Page 45: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Top-Down Unidirectional

Irreversible Flow No Feedback Loops

Ends Crashing on the Rocks

Cascade (or waterfall):

Page 46: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Laszlo Bock VP of People Operations, Google

“Research agrees with your intuition:

Having goals improve performance.

Spending hours cascading goals does not.”

Page 47: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

There has to be another way

Page 48: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Full-Stack Agility

Page 49: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Strategy

Tactics

Operations

Culture

Goals

The Stack

Page 50: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Strategy

Tactics

Operations

Culture

Goals

Waterfall Development

Big non-validated bets, long feedback cycles

Annual Static Planning

Top-Down, Command & Control

Cascading (Waterfall)

Goals

The Traditional Stack

Page 51: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Strategy

Tactics

Operations Agile Development

Lean Startup + Lean Prod Mgmt.

Culture

Goals

Half-Baked Agility

Cascading (Waterfall)

Goals

Annual Static Planning

Top-Down, Command & Control

Page 52: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Strategy

Tactics

Operations Agile Development

Lean Startup + Lean Prod Mgmt.

Culture

Goals

Half-Baked Agility

Cascading (Waterfall)

Goals

Annual Static Planning

Top-Down, Command & Control

Waterfall Legacy

Page 53: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

The Waterfall Legacy is in direct conflict with Agile

Page 54: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

70%of Agile practitioners

Report tension between their teams and the rest

of the organization.

Embracing Agile, HBR - 2016

Page 55: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Strategy

Tactics

Operations Agile Development

Culture

GoalsData Driven, Iterative, Hypothesis Validation

“Silicon Culture”

OKR (Goal

Agility)

Full-Stack Agility

Lean Startup + Lean Prod Mgmt.

Page 56: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Silicon Culture’s 7As

Agility Iterative, incremental, fast feedback

Agnosticism Data driven, hypothesis validation, experiments

Asymmetry Power Laws, Moonshots, 10x Talent

Autonomy Self-managed teams that question “orders”

Alignment 360º Alignment, continuous feedback

Accountability Focus on delivering value

Authenticity Purpose, consistent values

Page 57: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

James March Stanford University

“Culture is

Poetry and

Plumbing”

Page 58: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

When properly used, OKR can change the “cultural plumbing”

Page 59: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

How Silicon Valley sets goals?

Page 60: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

OKR - Objectives and Key Results

Page 61: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Created by Intel

Page 62: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Goal Agility 1

Page 63: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Simplicity

2

Page 64: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Adopted by Google in 1999

Page 65: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR
Page 66: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

John Doerr

Page 67: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Doerr’s Goal Formula

I will ____ as measured by ______

Page 68: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Doerr’s Goal Formula

I will (Objective) as measured by (this set of Key Results)

Page 69: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe3Measurement

Page 70: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Objective: •Aspirational. •Memorable – Simpler, shorter, remarkable. •Qualitative.

OKR: Components

Key Results: •2-5 per Objective. •Quantitative & Measurable. •Metrics (recommended) or Milestones.

Page 71: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipeEngaging Objectives 4

Page 72: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

“Ensure the dream”

Page 73: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

“Move to the clouds”

Page 74: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

Make Everybody Happy ;)

Page 75: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Key Results: •Increase average weekly visits to 3.3 per active user •Reach a Net Promoter Score of 52%. •Increase non paid (organic) traffic to 80%. •Reduce revenue churn to 1%. •Increase engagement (users that complete a full profile) to 75%.

Objective: Delight our customers

OKR - Example

Page 76: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Activity #01: Creating one OKR

Page 77: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

•Create one Objective with up to 5 Key Results for one initiative you are working on.

Talk to your neighbor

Page 78: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

5-minute exercise

Page 79: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Key Results: •Increase average weekly visits to 3.3 per active user •Reach a Net Promoter Score of 52%. •Increase non paid (organic) traffic to 80%. •Reduce revenue churn to 1%. •Increase engagement (users that complete a full profile) to 75%.

Objective: Delight our customers

OKR - Example

Page 80: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

•Activity-based Key Results: Measure the completion of tasks and activities or the delivery of project milestones or deliverables.

•Value-based Key Results: Measure actual results and the successful delivery of value (or a value component) to the organization.

Value-based key results measure the outcomes of successful activities.

Choosing your Key Results

There are two basic types of Key Results:

Page 81: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Tactical shorter-term OKRs for the teams

High level strategic OKRs for the company

Page 82: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

~60% Bottom Up

Page 83: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Transparency

Page 84: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

How OKR complements Agile and Lean

Page 85: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

A

Moving from features to value

Page 86: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

Page 87: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

Page 88: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

OKR helps to create a culture focused on measuring and delivering business value.

Page 89: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

From Activities To Value

Definition of Done

Acceptance Criteria

Success Criteria(OKRs)

Page 90: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

B

Enabling autonomy

Page 91: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Is Agile Command & Control?

Page 92: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

Command&Control is still here

“Because Sam said.”

“When Sam is OK with it.”

Page 93: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

Command&Control is still here

We call them our delivery team…

…because they deliver what we tell them to.

Page 94: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

“To achieve the success criteria

as defined in the OKRs.”

“To deliver the features the stakeholders

want.”

What is the purpose of the team?

Vs.

Page 95: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

C

OKR incentivizes leaner approaches and smaller

batches

Page 96: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Is your project too big?

Page 97: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Value-based Timebox

You have to deliver value until the end of the OKR cycle.

Page 98: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

OKR helps prioritize the backlog

D

Page 99: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

“If a feature idea doesn’t speak directly to one the

OKRs, it’s generally off the list.”

Marty Cagan, Silicon Valley Product Group

Page 100: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

E

Enabling Agile Transformation

Page 101: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Why executives resist to Agile?

Page 102: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

“You want us to replace our GANTT charts with what?”

Page 103: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

“With a bunch of people standing up”

Page 104: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

“…and post-it notes!”

“Lots of them!”

Page 105: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

“And we have a MANIFESTO!”

Page 106: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR
Page 107: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Enabling Agile Transformation

Perceived predictability

Delivered Value

Page 108: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Instead of committing to deliver X by Y date, the team commits to iterate

towards the agreed results.

Page 109: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Transforming Activities into Value

Page 110: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

If we are successful with ____________,

we will have more ________

and/or less __________

Page 111: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

If we are successful with the new campaign,

we will have more customer satisfaction (NPS)

and/or less churn

Page 112: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Group Activity #02: Transforming Activities

into Value

Page 113: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Talk to your neighbor

•Evaluate your Key Results and separate those that are Activity-based and those that are Value-based.

•Select one Activity-based Key Result and convert it into Value.

OR

•Select one initiative that you have worked on and convert it into Value.

Page 114: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

5-minute exercise

Page 115: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

If we are successful with the new campaign,

we will have more customer satisfaction (NPS)

and/or less churn

Page 116: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

A different mindset

Page 117: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

IT Mindset

Vs.

Product Mindset

Page 118: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

IT Mindset Product Mindset

Exists to service the perceived needs of "the business."

Exists to service the needs of the customers.

Requirements gathering Product Discovery

Functional Silos Multi-functional teams

Measured by projects Measured by results

Engineers focus on delivery Engineers help create technology-inspired products

Page 119: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

How to handle the transition?

Page 120: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Activities

Goal Agility Autonomy

Static Plan Top-Down

Content

Process

Value

“IT/Delivery Mindset”

Decoupling Process and Content

1

2

3Transformation

Routes

Page 121: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Engaging

Working

Delivered

Valuable Business

Goal Maturity Levels

Engineering & Team

Product & UX

Project Management

Page 122: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

Level Delivered Working Engaging Valuable

Goals

Project Management

Engineering & Team

Product & UX Business

• Schedule• Budget• Scope• Predictability

• # de Bugs• MTTR• Uptime• Response Time• Lead time• Cycle time• Delivery frequency

• % Test Coverage

• Spotify Health Check

• Team Maturity

HEART• Happiness• Engagement• Adoption• Retention• Task success

• Revenue• EBIDTA• Revenue per employee

• Value obtained by the client:• ROI• Benefits• “Customer Success”

Page 123: Agile2016: Stop Using Agile with Waterfall Goals: Goal Agility with OKR

@meetfelipe

OKR Coach, Partner @ Lean Performance

Felipe Castro

leanperformance.com

linkedin.com/in/meetfelipe@meetfelipe