Agile Companies Go P.O.P.

49
TOWARDS A NEW AGILE MANIFESTO CURTIS “OVID” POE Agile Companies Go P.O.P. P.O.P. Copyright 2012, Curtis "Ovid" Poe

description

This my keynote speech for YAPC::Europe, 2012. It went over very well, but it is effectively a rough draft of this concept and needs work. However, it was popular enough that people kept asking to see it, even in its incomplete form.

Transcript of Agile Companies Go P.O.P.

Page 1: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

TOWARDS A NEW AGILE MANIFESTO

CURTIS “OVID” POE

Agile Companies Go P.O.P.

Page 2: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Keynotes

Why are you here?

Page 3: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Are Great Companies Lucky?

Published in Harvard Business ReviewOver 20,000 CompaniesFrom 1966 to 2006http

://hbr.org/2009/04/are-great-companies-just-lucky/ar/1

Page 4: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poehttp://www.flickr.com/photos/redwoodphotography/4356518997/§

Most studies are crap

http://www.flickr.com/photos/redwoodphotography/4356518997/

Most studies are crap

Page 5: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Sharpshooter Problem Shoot first. Announce your target.

Page 6: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Reality trumps opinion

Book Apparent Superstars Real Superstars

Alchemy of Growth 29 0%

Big Winners/Big Losers 9 13%

Blueprint to a Billion 26 8%

Breakthrough Company 9 17%

Built to Last 18 7%

Creative Destruction 11 0%

Good to Great 11 0%

Granularity of Growth 42 0%

In Search of Excellence 14 0%

Peak Performance 21 0%

Profit from the Core 32 17%

Stall Points 67 0%

What Really Works 14 0%

Page 7: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

?

Page 8: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

http://commons.wikimedia.org/wiki/File:Chess-king.JPG

Between

Between players of equal skill, a bad strategy beats no strategy.

Page 9: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

So let’s pick a good plan

Page 10: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

A Bad Plan

http://en.wikipedia.org/wiki/File:Waterfall_model_(1).svg

Page 11: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Worst Case Scenario

Lots of meetingsBig projectsAgile is AmateurProcess is everything

Page 12: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Conform

Page 13: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Page 14: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Agile Manifesto

1. Individuals over process2. Software over documentation3. Customer collaboration over negotiation4. Change over plans

http://agilemanifesto.org/

Page 15: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Chess

Goal CheckmateStrategy Plan to achieve your goalTactics Moves to support your

strategy

Page 16: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Business

Goal Mission statementStrategy An agile companyTactics P.O.P.

Page 17: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

What is P.O.P.?

P eople

O rganization

P rocess

Page 18: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

People

Page 19: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

People Are Everything

Page 20: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Unstructured Interviews

Interviewers aren’t trained in interviewsDifferent candidates/different questionsPersonality valued over performanceVery little predictive power

https://apps.opm.gov/ADT/ContentFiles/SIGuide09.08.08.pdf

Page 21: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Structured Interviews

Same questions in same orderFocused on specific skills neededExcellent predictive power

Page 22: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Structured Interviews

1. Job analysis 2. Determine desired skills3. Develop questions4. Goal, role, action, score, speculation (GRASS)5. Immediately assess answers

Page 23: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Organization

Page 24: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Eyjafjallajökull Eruption 2010

http://en.wikipedia.org/wiki/File:Eyjafjallajokull_volcano_plume_2010_04_18.JPG

Page 25: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Agile Organizations

Everyone is an ownerOwnership means responsibilityResponsibility requires authorityAuthority requires information

Page 26: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Agile Organizations

Small projects over large projectsInformation over opinionEmployees are as important as customers

Page 27: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Ownership Implies Trust

Page 28: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Trust

Did you hire the right people?Trust them to make decisionsDecisions require information

Page 29: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Information

Page 30: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Log Everything

http://www.flickr.com/photos/ex_magician/4931775369/

Page 31: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Monitor Everything

Monitor Everything

http://commons.wikimedia.org/wiki/File:Eyes_at_the_Prague_Police_Museum.jpg

Page 32: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Challenge Assumptions

http://commons.wikimedia.org/wiki/File:Leaning_Tower-Pisa.jpg

Page 33: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Large projects fail

http://commons.wikimedia.org/wiki/File:Space_Shuttle_Columbia_launching.jpg

http://www.idlewords.com/2005/08/a_rocket_to_nowhere.htm

http://www.ralentz.com/old/space/feynman-report.html

Page 34: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Break Down Large Projects

Don’t do large projects (major caveats!)Do a series of small projectsEach should add value

Page 35: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

VA LV E

http://www.valvesoftware.com/company/Valve_Handbook_LowRes.pdf

Page 36: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Process

Page 37: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

This Subroutine

sub perambulate { my @thingies = @_; foreach my $thing (@thingies) { # validate the thingy } return \@thingies;}

Page 38: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

5 lines of code …5 page “code review”

http://www.flickr.com/photos/titouanrusso/6153880964/

Page 39: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Workflow: Management Perspective

Page 40: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Workflow: Developer Perspective

Page 41: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Workflow: Agile Perspective

CompromiseTasks, not processesTesting, logging, and monitoring

Page 42: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Continuous … What?

Continuous integration is old-skool!Try continuous deploymentCourage instead of fearMinimize risk/maximize reward

Continuous Deployment at IMVU: Doing the impossible fifty times a day

Page 43: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Testing

TDD is not QATradeoffs between unit/integration testingA/B test your bug fixes!

Testing

http://commons.wikimedia.org/wiki/File:94-707-6_hybrid_rocket_test.jpg

Page 44: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Agile Project Management

XP?Scrum?Kanban?Crystal?Something else?

Page 45: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Implementing P.O.P.

Becoming agile is a hard projectAn agile projectOne step at a timeHigh value steps first

Page 46: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Implementing P.O.P.

Hiring: easy and hardTalk to your employeesAssess risk/rewardPareto!

Page 47: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Once You’re Agile

Never forget your goalAlways question your processesAgile is a mindset, not a process

Page 48: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

Agile Manifesto

1. People over process2. Software over documentation3. Customer collaboration over negotiation4. Change over plans

Page 49: Agile Companies Go P.O.P.

P.O.P. Copyright 2012, Curtis "Ovid" Poe

A New Agile Manifesto?

1. People over process2. Information over opinion3. Courage over fear4. Change over plans