Agile the pivotal way

agile, the Pivotal way 20 years of experience (condensed into some things that work for us) Mike Gehard, Software Engineer @mikegehard mgehard@pivotallabs.comThursday, April 7, 2011

Pivotal Labs SnapshotThursday, April 7, 2011

Pivotal Labs Snapshot • Founded 1989Thursday, April 7, 2011

Pivotal Labs Snapshot • Founded 1989 • Agile since mid ‘90sThursday, April 7, 2011

Pivotal Labs Snapshot • Founded 1989 • Agile since mid ‘90s • Rails since 2006Thursday, April 7, 2011

Pivotal Labs Snapshot • Founded 1989 • Agile since mid ‘90s • Rails since 2006 • Approximately 100 people, and growingThursday, April 7, 2011

Pivotal Labs Snapshot • Founded 1989 • Agile since mid ‘90s • Rails since 2006 • Approximately 100 people, and growing • HQ in San FranciscoThursday, April 7, 2011

Pivotal Labs Snapshot • Founded 1989 • Agile since mid ‘90s • Rails since 2006 • Approximately 100 people, and growing • HQ in San Francisco • Regional offices in Boulder, New York and SingaporeThursday, April 7, 2011

...starts with breakfast Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes HereThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes HereThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here The Theory Behind BreakfastThursday, April 7, 2011

Followed by Standup Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes HereThursday, April 7, 2011

Stand-Up for 50 People? Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes HereThursday, April 7, 2011

Large Standup Covers Items of Global Utility • Introductions • Anyone new to the office • Help • Anything anyone needs help on • Interesting • Anything of global interest or utility • New techniques, interesting gotchas, events • Stretch (optional)Thursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here A place for people to jot • Bulleted Text Goes Here • Bulleted Text Goes Here down Bulleted Text Goes Here not • topics so they’re forgottenThursday, April 7, 2011

The big standup is followed by Team Standups Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes HereThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here ...and then we start pairingThursday, April 7, 2011

Clients are Close at Hand Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes HereThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here PivotGoes Here • Bulleted Text • Bulleted Text GoesClient HereThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Wednesday Tech TalksThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here ...which we videotapeThursday, April 7, 2011

...and Title share... • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here http://pivotallabs.com/talksThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here email stationThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here PhoneboothsThursday, April 7, 2011

...and people go home around 6.Thursday, April 7, 2011

A Typical Day at Pivotal Labs SF • 8:45 Breakfast • 9:05 Standup • 9:15-ish Team Standups • Noonish Lunch • 6:00 End of the work day Pivot Pong as you wishThursday, April 7, 2011

A Typical Day at Pivotal Labs Boulder • 7:45 Breakfast • 8:05 Standup • 8:15-ish Team Standups • Noonish Lunch • 5:00 End of the work dayThursday, April 7, 2011

Why Sustainability Matters (for bean counters) • Predictable delivery is at a premium • Tired developers introduce bugs • Developer retention is important! • Crunch time buys short-term productivity at long-term costThursday, April 7, 2011

Why Developer Happiness is Important to the Business • Leading Indicator: Developer Happiness strongly correlated to Developer Productivity Grunt Work = Money Wasted • Happy developers are more focusedThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Multiple LocationsThursday, April 7, 2011

The New York Ofﬁce Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes HereThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Standup Agenda WhiteboardThursday, April 7, 2011

Pairing Stations Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes HereThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Tech TalksThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Email StationsThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Community EventsThursday, April 7, 2011

Boulder, ColoradoThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Tras Street SingaporeThursday, April 7, 2011

Starting new ofﬁces grongarThursday, April 7, 2011

Rotations Ralph HockensThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Simple TelepresenceThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Meeting rooms all set up for teleconferencingThursday, April 7, 2011

Cheap and Cheerful Telepresence • Mac Mini • HDTV • iSight • Snowball Mic • Skype or iChat • Total: about $1,500Thursday, April 7, 2011

Remote PairingThursday, April 7, 2011

What do you mean, agile? Ralph HockensThursday, April 7, 2011

Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Title Individuals and interactions over processes and tools • software Text Goes Here Working Bulleted over comprehensive documentation • Bulleted Text Goes Here Customer collaboration over contract negotiation Responding to change over following a plan • Bulleted Text Goes Here That is, while there is value in the items on • Bulleted Text Goes Here the right, we value the items on the left more. • Bulleted Text Goes Here Kent Beck Mike Beedle James Grenning Jim Highsmith Robert C. Martin Steve Mellor Arie van Bennekum Andrew Hunt Ken Schwaber Alistair Cockburn Ron Jeffries Jeff Sutherland Ward Cunningham Jon Kern Dave Thomas Martin Fowler Brian Marick © 2001, the above authors this declaration may be freely copied in any form, but only in its entirety through this notice.Thursday, April 7, 2011

That’s nice... How do we do that?Thursday, April 7, 2011

That’s nice... How do we do that? • Business DrivenThursday, April 7, 2011

That’s nice... How do we do that? • Business Driven • Iterative Development, with Short IterationsThursday, April 7, 2011

That’s nice... How do we do that? • Business Driven • Iterative Development, with Short Iterations • Test/Behavior Driven DevelopmentThursday, April 7, 2011

That’s nice... How do we do that? • Business Driven • Iterative Development, with Short Iterations • Test/Behavior Driven Development • Continuous Integration/ReleasabilityThursday, April 7, 2011

That’s nice... How do we do that? • Business Driven • Iterative Development, with Short Iterations • Test/Behavior Driven Development • Continuous Integration/Releasability • Pair ProgrammingThursday, April 7, 2011

That’s nice... How do we do that? • Business Driven • Iterative Development, with Short Iterations • Test/Behavior Driven Development • Continuous Integration/Releasability • Pair Programming • Productive Work EnvironmentThursday, April 7, 2011

Business Driven Accept RejectThursday, April 7, 2011

Business Driven • Requirements come from business stakeholders Accept RejectThursday, April 7, 2011

Business Driven • Requirements come from business stakeholders • One designated Customer is empowered to make decisions Accept RejectThursday, April 7, 2011

Business Driven • Requirements come from business stakeholders • One designated Customer is empowered to make decisions • Priorities are set by that Customer Accept RejectThursday, April 7, 2011

Business Driven • Requirements come from business stakeholders • One designated Customer is empowered to make decisions • Priorities are set by that Customer • The Customer can change priorities on anything unstarted Accept RejectThursday, April 7, 2011

Business Driven • Requirements come from business stakeholders • One designated Customer is empowered to make decisions • Priorities are set by that Customer • The Customer can change priorities on anything unstarted • The Customer accepts the work in ﬁne-grained increments Accept RejectThursday, April 7, 2011

Business Driven • Requirements come from business stakeholders • One designated Customer is empowered to make decisions • Priorities are set by that Customer • The Customer can change priorities on anything unstarted • The Customer accepts the work in ﬁne-grained increments • The Customer is intimately aware of progress, and projected completion dates Accept RejectThursday, April 7, 2011

Business Driven • Requirements come from business stakeholders • One designated Customer is empowered to make decisions • Priorities are set by that Customer • The Customer can change priorities on anything unstarted • The Customer accepts the work in ﬁne-grained increments • The Customer is intimately aware of progress, and projected completion dates Accept Reject • Closing the feedback loop is criticalThursday, April 7, 2011

Iterative DevelopmentThursday, April 7, 2011

Iterative Development • Feedback cycle is shortThursday, April 7, 2011

Iterative Development • Feedback cycle is short • This keeps the cost of change lowThursday, April 7, 2011

Iterative Development • Feedback cycle is short • This keeps the cost of change low • Prevents unnecessary workThursday, April 7, 2011

Iterative Development • Feedback cycle is short • This keeps the cost of change low • Prevents unnecessary work • New insights to be gained from the work we’ve already completedThursday, April 7, 2011

Iterative Development • Feedback cycle is short • This keeps the cost of change low • Prevents unnecessary work • New insights to be gained from the work we’ve already completed • Iterations are as short as we can make themThursday, April 7, 2011

TDD/BDDThursday, April 7, 2011

TDD/BDD • Tell us when we’ve met the customer requirementsThursday, April 7, 2011

TDD/BDD • Tell us when we’ve met the customer requirements • Tell us when we’ve broken behavior that used to workThursday, April 7, 2011

TDD/BDD • Tell us when we’ve met the customer requirements • Tell us when we’ve broken behavior that used to work • Tell us when we haven’t, so we can refactor with impunityThursday, April 7, 2011

TDD/BDD • Tell us when we’ve met the customer requirements • Tell us when we’ve broken behavior that used to work • Tell us when we haven’t, so we can refactor with impunity • Writing tests ﬁrst keeps us from over designingThursday, April 7, 2011

TDD/BDD • Tell us when we’ve met the customer requirements • Tell us when we’ve broken behavior that used to work • Tell us when we haven’t, so we can refactor with impunity • Writing tests ﬁrst keeps us from over designing • Writing tests ﬁrst forces cleaner API designThursday, April 7, 2011

TDD/BDD • Tell us when we’ve met the customer requirements • Tell us when we’ve broken behavior that used to work • Tell us when we haven’t, so we can refactor with impunity • Writing tests ﬁrst keeps us from over designing • Writing tests ﬁrst forces cleaner API design • Leads to looser coupling and encourages higher cohesionThursday, April 7, 2011

TDD/BDD • Tell us when we’ve met the customer requirements • Tell us when we’ve broken behavior that used to work • Tell us when we haven’t, so we can refactor with impunity • Writing tests ﬁrst keeps us from over designing • Writing tests ﬁrst forces cleaner API design • Leads to looser coupling and encourages higher cohesion • Good developer testing keeps the cost of change constantThursday, April 7, 2011

Test-Drive Everything! •Rails, Ruby, of course •JavaScript too! •Mobile too!Thursday, April 7, 2011

Continuous Integration, Continuous ReleasabilityThursday, April 7, 2011

Continuous Integration, Continuous Releasability • Knowing when things break is critical to reducing the cost of ﬁxing defects.Thursday, April 7, 2011

Continuous Integration, Continuous Releasability • Knowing when things break is critical to reducing the cost of ﬁxing defects. • Keep the build status visible, so you can ﬁx it quicklyThursday, April 7, 2011

Continuous Integration, Continuous Releasability • Knowing when things break is critical to reducing the cost of ﬁxing defects. • Keep the build status visible, so you can ﬁx it quickly • A broken build is a ‘stop the line’ eventThursday, April 7, 2011

Continuous Integration, Continuous Releasability • Knowing when things break is critical to reducing the cost of ﬁxing defects. • Keep the build status visible, so you can ﬁx it quickly • A broken build is a ‘stop the line’ event • Continuous releasability does not mean you release every day.Thursday, April 7, 2011

Continuous Integration, Continuous Releasability • Knowing when things break is critical to reducing the cost of ﬁxing defects. • Keep the build status visible, so you can ﬁx it quickly • A broken build is a ‘stop the line’ event • Continuous releasability does not mean you release every day. • It just means you can.Thursday, April 7, 2011

Continuous Integration, Continuous Releasability • Knowing when things break is critical to reducing the cost of ﬁxing defects. • Keep the build status visible, so you can ﬁx it quickly • A broken build is a ‘stop the line’ event • Continuous releasability does not mean you release every day. • It just means you can. • Releases can be distracting, so weigh the cost of a release against the value it adds to the business.Thursday, April 7, 2011

Pair ProgrammingThursday, April 7, 2011

Pair Programming • Do we really have to pair?Thursday, April 7, 2011

Pair Programming • Do we really have to pair? • Isn’t Pairing Slower?Thursday, April 7, 2011

Pair Programming • Do we really have to pair? • Isn’t Pairing Slower? • I don’t like pairing.Thursday, April 7, 2011

Pair Programming • Do we really have to pair? • Isn’t Pairing Slower? • I don’t like pairing. • I’m shy.Thursday, April 7, 2011

Pair Programming • Do we really have to pair? • Isn’t Pairing Slower? • I don’t like pairing. • I’m shy. • I don’t want to look stupid.Thursday, April 7, 2011

Do we really have to pair?Thursday, April 7, 2011

Do we really have to pair? •Yes, you do.Thursday, April 7, 2011

Do we really have to pair? •Yes, you do. • ...but only if you want to be efficientThursday, April 7, 2011

Do we really have to pair? •Yes, you do. • ...but only if you want to be efficient • This is one of the least-used practices, and one of the most important.Thursday, April 7, 2011

Do we really have to pair? •Yes, you do. • ...but only if you want to be efficient • This is one of the least-used practices, and one of the most important. • And stop whining! You do it already when you get stuck on something.Thursday, April 7, 2011

What do developers really do all day? • Coding • Reading web pages about coding • Stuck on some problem, unsure of: • The right approach • What the API for that object was • How SQL indexes are selected • How bind(this) works in JavaScript • Checking email • Checking news, stock price, staring blankly into spaceThursday, April 7, 2011

How does pairing help? • 80/20 rule: You don’t get stuck, so you spend your time on the most interesting part of the code. • You talk through design, and reﬁne before you code. • You learn from your pair, everything from design and testing techniques to (no)SQL, CSS, and JavaScript tips. • Focus matters: Your pair keeps you paying attention, and can smooth over disruptionsThursday, April 7, 2011

How does pairing help? • New team members: You’re really productive the ﬁrst hour, not marginally productive starting two weeks in • They have a local sherpa to tell them how the code they’re working on actually works. • Knowledge Silos: Your bus number approaches ∞Thursday, April 7, 2011

Pairing CombinationsThursday, April 7, 2011

Pairing Combinations ? ? ? ? ? ? ? ?Thursday, April 7, 2011

Pairing CombinationsThursday, April 7, 2011

Anchors ell brownThursday, April 7, 2011

All but the anchor can swap out wheneverThursday, April 7, 2011

Standard Development Workstation • Keeping tools consistent across machines is critical to high-rotation pairing. • People don’t have their own machines, but sit where their project is. • Machines are re-imaged after each project • A brand new machine is ready to use within 30 minutes of it showing up on the ﬂoor.Thursday, April 7, 2011

Agile is not... Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes HereThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here ...a religion.Thursday, April 7, 2011

...but a tool that works well Terinea IT SupportThursday, April 7, 2011

...and that needs to be renewed continuously. donielleThursday, April 7, 2011

RetrospectivesThursday, April 7, 2011

Company MeetingsThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here The Client EngagementThursday, April 7, 2011

Family andresmhThursday, April 7, 2011

pedrosimoes7Thursday, April 7, 2011

Family jronaldleeThursday, April 7, 2011

Engaging with Pivotal LabsThursday, April 7, 2011

Start with an initial scoping... toptechwriterThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here ... then comes the Agile inception...Thursday, April 7, 2011

... followed by the building of “stuff”... yakobusanThursday, April 7, 2011

... all the while doing retrospectives ... creative_stockThursday, April 7, 2011

... and wrapping it up when everything is implemented jayneanddThursday, April 7, 2011

Ramp up or down as needed alexliivetThursday, April 7, 2011

TheTruthAbout...Thursday, April 7, 2011

Culture Matters! • Consistency of service between teams and locations • It works! Maintaining the Culture kaibara87Thursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here The Team MattersThursday, April 7, 2011

The Location MattersThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Market Street San FranciscoThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Broadway ManhattanThursday, April 7, 2011

Pearl Street BoulderThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Tras Street SingaporeThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Hire WellThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Hire for Aptitude and FitThursday, April 7, 2011

The Rob Pairing InterviewThursday, April 7, 2011

Title • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here • Bulleted Text Goes Here Pairing with a CandidateThursday, April 7, 2011

Listen to your gut! TheGiantVerminThursday, April 7, 2011

The Two Beer TestThursday, April 7, 2011

Don’t keep people who don’t ﬁt jessicafmThursday, April 7, 2011

Come Visit! • You all have an open invitation to come visit us in any of our locations. • Keep an “eye” out for upcoming events at our Boulder office. • Just drop me a note and we’ll set it up.Thursday, April 7, 2011

Thanks! •Mike Gehard, Software Engineer, Pivotal Labs •@mikegehard •@pivotalboulder •@pivotallabs •mgehard@pivotallabs.com •Talks at http://pivotallabs.com/talksThursday, April 7, 2011

Agile the pivotal way

by Mike Gehard on Apr 07, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

Statistics

Agile the pivotal way — Presentation Transcript