Software in 30 Days for Agile Managers

214 Pages·2012·2.31 MB·English

FFIRS 03/10/2012 14:31:18 Page2
FFIRS 03/10/2012 14:31:18 Page1
FFIRS 03/10/2012 14:31:18 Page2
FFIRS 03/10/2012 14:31:18 Page3
KEN SCHWABER and JEFF SUTHERLAND
JohnWiley&Sons,Inc.
FFIRS 03/10/2012 14:31:24 Page4
Copyright#2012byKenSchwaberandJeffSutherland.Allrightsreserved.
PublishedbyJohnWiley&Sons,Inc.,Hoboken,NewJersey.
PublishedsimultaneouslyinCanada.
Nopartofthispublicationmaybereproduced,storedinaretrievalsystem,ortransmittedinanyformorbyanymeans,
electronic,mechanical,photocopying,recording,scanning,orotherwise,exceptaspermittedunderSection107or108of
the1976UnitedStatesCopyrightAct,withouteitherthepriorwrittenpermissionofthePublisher,orauthorization
throughpaymentoftheappropriateper-copyfeetotheCopyrightClearanceCenter,Inc.,222RosewoodDrive,Danvers,
MA 01923, [phone], fax [phone], or on the web at www.copyright.com. Requests to the Publisher for
permissionshouldbeaddressedtothePermissionsDepartment,JohnWiley&Sons,Inc.,111RiverStreet,Hoboken,NJ
07030, [phone], fax [phone], or online at http://www.wiley.com/go/permissions.
LimitofLiability/DisclaimerofWarranty:Whilethepublisherandauthorhaveusedtheirbesteffortsinpreparingthis
book,theymakenorepresentationsorwarrantieswithrespecttotheaccuracyorcompletenessofthecontentsofthisbook
andspecificallydisclaimanyimpliedwarrantiesofmerchantabilityorfitnessforaparticularpurpose.Nowarrantymaybe
createdorextendedbysalesrepresentativesorwrittensalesmaterials.Theadviceandstrategiescontainedhereinmaynot
besuitableforyoursituation.Youshouldconsultwithaprofessionalwhereappropriate.Neitherthepublishernorauthor
shallbeliableforanylossofprofitoranyothercommercialdamages,includingbutnotlimitedtospecial,incidental,
consequential,orotherdamages.
Forgeneralinformationonourotherproductsandservicesorfortechnicalsupport,pleasecontactourCustomer
CareDepartmentwithintheUnitedStatesat(800)762-2974,outsidetheUnitedStatesat(317)572-3993or
fax[phone].
Wileypublishesinavarietyofprintandelectronicformatsandbyprint-on-demand.Somematerialincludedwithstandard
printversionsofthisbookmaynotbeincludedine-booksorinprint-on-demand.IfthisbookreferstomediasuchasaCD
or DVD that is not included in the version you purchased, you may download this material at http://booksupport.wiley.
com. For more information about Wiley products, visit www.wiley.com.
LibraryofCongressCataloging-in-PublicationData:
Schwaber,Ken.
Softwarein30days:howAgilemanagersbeattheodds,delighttheircustomers,andleavecompetitorsinthedust/
KenSchwaber,JeffSutherland.
p.cm.
Includesindex.
ISBN978-1-118-20666-9(pbk.);ISBN978-1-118-22854-8(ebk);ISBN978-1-118-24090-8(ebk);
ISBN978-1-118-26574-1(ebk)
1. Agilesoftwaredevelopment. 2. Scrum(Computersoftwaredevelopment) 3. Computersoftware–
Development. I. Sutherland,JeffreyVictor. II. Title. III. Title:Softwareinthirtydays.
QA76.76.D47S32232012
005.1–dc23
2011050969
PrintedintheUnitedStatesofAmerica
10987654321
FFIRS 03/10/2012 14:31:24 Page5
To Ikujiro Nonaka, Babatunde A. Ogunnaike, and
Hirotaka Takeuchi for their inspiration andguidance.
FFIRS 03/10/2012 14:31:24 Page6
FTOC 03/05/2012 11:7:16 Page7
Contents
About the Authors xi
Acknowledgments xiii
Introduction xv
Section I WhyEvery Business in theWorld Can ProduceSoftware
in30 Days 1
Youareprobablyfrustratedwithyoursoftwareorganization.Youwouldlikeitto
bequicker,moreflexible,understandyourneedsbetter,andhelpyoubecome
moreprofitable.Welookatwhyyouarefrustratedandhowtofixtheproblem.
1 TheCrisisinSoftware:TheWrongProcessProducestheWrongResults 3
Manysoftwareorganizationsfollowadevelopmentprocessthatguarantees
waste,uncontrolledrisk,unpredictability,surprises,andlowvalue.Wewill
investigatewhythisprocesswaschosen,howitguaranteesfailure,andlook
andsomeorganizationsthathaverecoveredfromit.
2 Scrum:TheRightProcessProducestheRightResults 17
Thereisaprocessthatisappropriateforsoftwaredevelopment.Whenyouget
yourdeveloperstouseit,youwillimmediatelygainproductivity,quality,value,
control,predictability,andsatisfaction.Welookathowthishappensin
thischapter.
vii
FTOC 03/05/2012 11:7:16 Page8
viii CONTENTS
3 TryItYourself:ThePilot 33
Youhavereadourassertionthatthereisabetterwayforyoutogetsoftware
developedforyou.However,alotofpeoplehavemadeassertionsandtaken
alotofyourmoneyinthepast,withlittleornoimprovement.Inthischapter
weshowyouhowtoprovethatourapproachworksfornomoney.
4 WhatCanIDo? 49
Youlearnedhowtodobetterandyou’vetriedityourself.Youliketheresults
andyouknowwhattotellthesoftwareorganizationtodo.Inthischapter,we
lookatwhatyoucandotohelpwhatyouexperienceinthepilotprojectsucceed.
Section II Howto Produce Software in 30Days 55
Havingbettersoftwaredevelopedforyourneedsisnotsomuchhardas
itisdifferentfromwhatyouareusedto.Inthissection,welookata
progressivelybeneficialsetofapproachestogetyoufromwhereyouare
nowtoorganizationalagility.
5 GettingStartedwithScrum 57
Oursecretsauceforimprovingyourbenefitsfromsoftwareiscalled
“Scrum.”Yes,thisistherugbyeventthatkeepstheballmovingdown
thefield.We’lldiscussScrum,howitworks,andwhyitworksinthischapter.
6 ScrumattheProjectLevel 63
Mostpersistentimprovementinsoftwaredevelopmentstartsatthe
projectlevel.YoucanuseScrumtofurtherproveitsutility,oron
criticallyimportantinitiativethatmustsucceed.We’llexplorewhat
youcantellyourdeveloperstodoafterreadingthischapter.
7 DevelopaScrumCapability 75
Successoftenbreedssuccess.Asmoresoftwareinitiativesusing
Scrumsucceed,morepeoplewillwanttogetonthewagon.Rather
thanchangingtheentireorganization,let’slookathowwecansetup
asoftwaredevelopmentuniverseseparatefromthedisappointing,
existingdepartment.Youcanincreasinglyreapbenefitshereonan
increasingnumberofprojectsandreleases.