Agile Case Studies and Lessons Learned

Agile: Case Studies and Lessons Learned Jez Humble, ThoughtWorks Studios @jezhumble #continuousdelivery Agile Tokyo, 20 July 2011

what’s the problem?Time-to-market is too longCompetitors are moving ever fasterIT environment is ever more complexIT costs are being squeezed

what if......you could get valuablesoftware released faster, withhigher quality, and reducedrisk?

agile manifestoOur highest priority is to satisfythe customer through early andcontinuous delivery ofvaluable software

web 2.0 http://code.flickr.com/

UK’s most popular newspaper website - 700pages per second, 30% growth per yearMulti-year program to replace legacy contentmanagement systemsPrevious attempt to create a new platform hadfailedInteractive site with dynamic, multimediacontent and social networking

Started with 2-week inception phase focusingon travel sectionTravel section went live after 8 months - 10xincrease in pages viewed per visitorLessons from ﬁrst section applied to nextphasesEach of subsequent 22 releases completed ontime and with minimal disruption

customer feedback“at 70% of the way through theproject we were able to start addingto the project outside of plannedactivities. A multi-million poundproject running on time andabsorbing growth in scope -remarkable.” Tom Turcan - General Manager, Digital

UK’s leading independent online train ticketretailer. 100k transactions per day. 8.4m users.Multi-year program to replace huge legacyplatform across multiple channelsScaling team from 50 to 200 people, distributedacross UK and 2 sites in IndiaRoll-out had to be incremental, keeping keycustomers and partners happy

Started with rapid prototype to createroadmapUsed ThoughtWorks Studios agile ALM solution- Mingle, Go, TwistIterative delivery: 6 week release cyclesExtensive use of build, test and deploymentautomation and virtualization

customer feedback“We undertook a complex,technically challenging and businesscritical program of work withThoughtWorks. We trusted themwith the success of our futurebusiness and they delivered.” David Jack – CIO

ThoughtWorks clients

agile is mainstream“In this year’s Forrester/Dr. Dobb’sGlobal Developer Technographics®Survey, 37% of developers tell usthat they use Agile developmentas their primary developmentprocess, up six points from lastyear’s survey” Jeffrey Hammond, “Five Ways To Streamline Release Management”, Forrester

internal barriers stall change“The main obstacles to improvedbusiness responsiveness are slowdecision-making, conﬂictingdepartmental goals and priorities,risk-averse cultures and silo-based information.” Economist Intelligence Unit: “Organisational agility: How business can survive and thrive in turbulent times”

agile triangle Jim Highsmith: Agile Project Management

do lessFar more than 50% offunctionality in software is rarelyor never used. These aren’t justmarginally valued features; manyare no-value features. The Standish Group, reported in the IEEE conference 2002

innovate You cant just ask customers what they want and then try to give that to them. By the time you get it built, theyll wantSteve Jobs something new.

scientiﬁc methodcreate hypothesis Customerdeliver minimum developentviable product Agile product developmentget feedback Eric Ries, “The Lean Startup” http://bit.ly/8ZoX5F(repeat)

continuous delivery Customer Delivery team Constant ﬂow of new features into productionsoftware always production readyreleases tied to business needs, not operationalconstraints

continuous deliveryAutomation: build, deployment, testing, release,infrastructure, databasesPatterns and practices: continuous integration,conﬁg management, deployment pipelineCollaboration: developers, testers, operations(devops) work together throughout

build quality in “Cease dependence on mass inspection to achieve quality. Improve the process and build quality into the product in the ﬁrst place” W. Edwards Deming

different kinds of testing Business facing AUTOMATED MANUAL ShowcasesSupport programming Functional acceptance Usability testing tests Critique project Exploratory testing Unit tests Non-functional Integration tests acceptance tests System tests (performance, scaling, ...) AUTOMATED MANUAL / AUTOMATED Technology facing Diagram invented by Brian Marick

value your people“Human beings have an innateinner drive to be autonomous,self-determined, and connected toone another. And when that driveis liberated, people achieve moreand live richer lives” Dan Pink, Drive

enabling agileCreate autonomous, cross-functionalproduct teamsCreate feedback loopsContinuous Improvement: theretrospective is the key agile process

thank you!http://continuousdelivery.com/http://studios.thoughtworks.com/gohttp://thoughtworks.com/@jezhumblejez@thoughtworks.com#continuousdelivery

Agile Case Studies and Lessons Learned

by Jez Humble on Jul 25, 2011

Accessibility

Categories

Upload Details

Usage Rights

Statistics

Agile Case Studies and Lessons Learned — Presentation Transcript