Agile, Rails and the Cloud - Pivotal Labs

Individuals and interactions over processes and tools. Working software over .... Realistic load testing environments much simpler. • Clone production data when ...
8MB Sizes 3 Downloads 110 Views
Agile, Rails, and the Cloud Why your customer should care about Agile, Rails and the Cloud

Ian McFarland, VP Technology

[email protected]

Or... Why companies can’t afford to ignore the efficiencies of modern development approaches

Ian McFarland, VP Technology

[email protected]


You • Most or all of you are Rails Developers, Agile Developers, Craftsman Developers, and run a rails shop

• Most or all of you have current deployments • On hardware not owned by your company • ...managed by someone else like Engine Yard? • On EC2? On other ‘Clouds’?

What were you doing before? • • • • •

Java Developer C/C++ Developer PHP Developer COBOL Developer Nothing: Rails/Ruby is my first development platform

• Goat Farmer? Stock Broker? Shoe Salesman?

Pivotal Labs • We make Pivotal Tracker • We’ve been doing agile for 10 years, first in SmallTalk, then in Java, now Rails and JavaScript

• We’ve grown from 20 to 70 since starting the Rails Practice 4 years ago

• We do enablement, but mostly implementation

Why do we build software • Because it’s cool • Because it’s fun • Because it’s exciting • Because we love the challenge • Because it beats the crap out of coal mining • Because employment is a nice thing to have

Why do Companies build software

• To make money • To save money • To manage risk • To satisfy business and government requirements

Building Business Value The revolution in Software is about one thing: Building business value as cheaply and efficiently as possible

So what’s expensive about software • Developers • Defects • Deployment/Operations • Code Maintenance • Change

Three Trends • Agile • Rails • The Cloud

What is it?

What’s in it for Us

What’s in it for Them


Cleaner, more flexible code; more fun coding; code is more maintainable

Fewer defects, more predictable delivery, more transparency, business determines what’s built



More powerful, more Less effort = lower cost expressive, less grunt Less effort = shorter work, more gets done time to market with less effort, more Less effort = lower TCO fun. Lower TCO, No initial Easy Scaling, capacity investment, lower planning, setup, no operating costs, shorter pagers deployment cycle, no sunk cost

It’s the Economy, Stupid

• Budgets are smaller • The stakes are higher • Departments have to do more with less money • Failure, though always an option, is more catastrophic

So what’s this Agile stuff?

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:


Individuals and interactions over processes and tools Goes Here documentation • Bulleted Working software Text over comprehensive Customer collaboration over Here contract negotiation Text Goes • Bulleted Responding to change over following a plan

• Bulleted Text Goes Here That is, while there is value in the items on Bulleted Text Goes • right, the we value the items on Here the left more. • Bulleted Text Goes Here

Kent Beck

James Grenning

Robert C. Martin

Mike Beedle

Jim Highsmith

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.

That’s nice... How do we do that? •