Software Development Rhythms: Harmonizing Agile Practices for Synergy

325 Pages·2008·3.52 MB·English

by  Kim Man Lui

SOFTWARE DEVELOPMENT
RHYTHMS

SOFTWARE DEVELOPMENT
RHYTHMS
Harmonizing Agile
Practices for Synergy
Kim Man Lui and Keith C. C. Chan
TheHongKongPolytechnicUniversity,HongKong
AJOHNWILEY&SONS,INC.,PUBLICATION
Copyright(cid:1)2008byJohnWiley&Sons,Inc.Allrightsreserved.
PublishedbyJohnWiley&Sons,Inc.,Hoboken,NewJersey
PublishedsimultaneouslyinCanada
Nopartofthispublicationmaybereproduced,storedinaretrievalsystem,ortransmittedinany
formorbyanymeans,electronic,mechanical,photocopying,recording,scanning,orotherwise,except
aspermittedunderSection107or108ofthe1976UnitedStatesCopyrightAct,withouteitherthe
priorwrittenpermissionofthePublisher,orauthorizationthroughpaymentoftheappropriate
per-copyfeetotheCopyrightClearanceCenter,Inc.,222RosewoodDrive,Danvers,MA01923,978-
750-8400,fax[phone],oronthewebatwww.copyright.com.RequeststothePublisherfor
permissionshouldbeaddressedtothePermissionsDepartment,JohnWiley&Sons,Inc.,111
RiverStreet,Hoboken,NJ07030,201-748-6011,fax[phone],oronlineathttp://
www.wiley.com/go/permission.
LimitofLiability/DisclaimerofWarranty:Whilethepublisherandauthorhaveusedtheirbest
effortsinpreparingthisbook,theymakenorepresentationsorwarrantieswithrespecttothe
accuracyorcompletenessofthecontentsofthisbookandspecificallydisclaimanyimplied
warrantiesofmerchantabilityorfitnessforaparticularpurpose.Nowarrantymaybecreatedor
extendedbysalesrepresentativesorwrittensalesmaterials.Theadviceandstrategiescontained
hereinmaynotbesuitableforyoursituation.Youshouldconsultwithaprofessionalwhere
appropriate.Neitherthepublishernorauthorshallbeliableforanylossofprofitoranyother
commercialdamages,includingbutnotlimitedtospecial,incidental,consequential,orother
damages.
Forgeneralinformationonourotherproductsandservicesorfortechnicalsupport,please
contactourCustomerCareDepartmentwithintheUnitedStatesat800-762-2974,outsidetheUnited
Statesat317-572-3993orfax317-572-4002.
Wileyalsopublishesitsbooksinavarietyofelectronicformats.Somecontentthatappears
inprintmaynotbeavailableinelectronicformats.FormoreinformationaboutWileyproducts,
visitourwebsiteatwww.wiley.com.
LibraryofCongressCataloging-in-PublicationData:
Lui,KimMan.
Softwaredevelopmentrhythms:usingtheflexibilityofagilesoftware
practicesincombination/ByKimManLui&KeithC.C.Chan.
p. cm.
Includesindex.
ISBN978-0-470-07386-5(cloth)
1. Computersoftware–Development. I. Chan,KeithC.C. II. Title.
QA76.76.D47L862007
005.1–dc22
2007019073
PrintedintheUnitedStatesofAmerica
10987654321
To my mother and my sister
— K.M.L
To my parents and sisters
and to Emily, Samantha, and Jeremy
— K.C.C.C.

CONTENTS
PREFACE xiii
1
NO PROGRAMMERDIES 3
1.1 Developing SoftwareversusBuildinga Tunnel 4
1.1.1 The Good OldDays? 5
1.1.2 The More Things Change, theMoreThey Stay the Same? 6
1.1.3 BehindSoftwareProducts 7
1.1.4 Deal or No Deal 10
1.2 Do-Re-Mi Do-Re-Mi 12
1.2.1 Iterative Models 14
1.2.2 Code and Fix 16
1.2.3 Chaos 17
1.2.4 Methodology that Matters 21
1.3 Software Development Rhythms 24
1.3.1 StaveChart by Example 25
1.3.2 Game Theory 28
1.3.3 In–Out Diagram 30
1.3.4 Master–Coach Diagram 31
1.3.5 No Mathematics 32
1.3.6 Where to Explore Rhythms 33
References 34
2
UNDERSTANDING PROGRAMMERS 37
2.1 Personality andIntelligence 39
2.1.1 Virtuosi 40
vii
viii CONTENTS
2.1.2 Meeting Your Team 41
2.1.3 Recruiting Programmers 43
2.2 OutsourcedProgrammers 45
2.2.1 Programmersin TheirEnvironments 46
2.2.2 Programmers,Cultures, and Teams 47
2.3 Experienced Management 48
2.3.1 Being Casual about Causal Relationships 49
2.3.2 Not Learning from Experience 50
2.3.3 DoingThingsRight Right Now 52
References 54
3
STARTWITH OPEN SOURCE 55
3.1 Process and Practice 58
3.1.1 The Four Psof Projects 60
3.1.2 AgileValues 63
3.1.3 Zero-Point Collaboration 64
3.2 Open-SourceSoftware (OSS) Development 65
3.2.1 SoftwareCloning 66
3.2.2 SoftwareQuality 67
3.2.3 StartingProcesses 68
3.2.4 Open-Source DevelopmentCommunity 69
3.2.5 Ugrammers 70
3.2.6 ParticipantRoles 71
3.2.7 Rapid Release 72
3.2.8 Blackbox Programming 74
3.2.9 OSS Practices 76
3.3 OSS-Like Development 77
3.3.1 AgilePractices 78
3.3.2 CommunicationProximity 79
3.3.3 Loose and TightCouples 80
3.3.4 Collocated Software Development 81
3.4 Conclusion 82
References 83
4
PLAGIARISM PROGRAMMING 87
4.1 Plagiarism 89
4.1.1 ExistingCode 90