LEADER 05476nam 2200721 a 450 001 9910814546703321 005 20200520144314.0 010 $a9786611373900 010 $a9781281373908 010 $a1281373907 010 $a9780470192672 010 $a0470192674 010 $a9780470192665 010 $a0470192666 035 $a(CKB)1000000000398282 035 $a(EBL)343652 035 $a(OCoLC)476158888 035 $a(SSID)ssj0000248115 035 $a(PQKBManifestationID)11208594 035 $a(PQKBTitleCode)TC0000248115 035 $a(PQKBWorkID)10201553 035 $a(PQKB)10897865 035 $a(MiAaPQ)EBC343652 035 $a(Au-PeEL)EBL343652 035 $a(CaPaEBR)ebr10232821 035 $a(CaONFJC)MIL137390 035 $a(OCoLC)124165171 035 $a(FINmELB)ELB178937 035 $a(Perlego)2775561 035 $a(EXLCZ)991000000000398282 100 $a20070507d2008 uy 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 10$aSoftware development rhythms $eharmonizing agile practices for synergy /$fKim Man Lui and Keith C.C. Chan 205 $a1st ed. 210 $aHoboken, N.J. $cWiley-Interscience$dc2008 215 $a1 online resource (325 p.) 300 $aDescription based upon print version of record. 311 08$a9780470073865 311 08$a0470073861 320 $aIncludes bibliographical references and index. 327 $aSOFTWARE DEVELOPMENT RHYTHMS; CONTENTS; PREFACE; Special Acknowledgment; Part I: Essentials; 1 NO PROGRAMMER DIES; 1.1 Developing Software versus Building a Tunnel; 1.1.1 The Good Old Days?; 1.1.2 The More Things Change, the More They Stay the Same?; 1.1.3 Behind Software Products; 1.1.4 Deal or No Deal; 1.2 Do-Re-Mi Do-Re-Mi; 1.2.1 Iterative Models; 1.2.2 Code and Fix; 1.2.3 Chaos; 1.2.4 Methodology that Matters; 1.3 Software Development Rhythms; 1.3.1 Stave Chart by Example; 1.3.2 Game Theory; 1.3.3 In-Out Diagram; 1.3.4 Master-Coach Diagram; 1.3.5 No Mathematics 327 $a1.3.6 Where to Explore RhythmsReferences; 2 UNDERSTANDING PROGRAMMERS; 2.1 Personality and Intelligence; 2.1.1 Virtuosi; 2.1.2 Meeting Your Team; 2.1.3 Recruiting Programmers; 2.2 Outsourced Programmers; 2.2.1 Programmers in Their Environments; 2.2.2 Programmers, Cultures, and Teams; 2.3 Experienced Management; 2.3.1 Being Casual about Causal Relationships; 2.3.2 Not Learning from Experience; 2.3.3 Doing Things Right Right Now; References; 3 START WITH OPEN SOURCE; 3.1 Process and Practice; 3.1.1 The Four Ps of Projects; 3.1.2 Agile Values; 3.1.3 Zero-Point Collaboration 327 $a3.2 Open-Source Software (OSS) Development3.2.1 Software Cloning; 3.2.2 Software Quality; 3.2.3 Starting Processes; 3.2.4 Open-Source Development Community; 3.2.5 Ugrammers; 3.2.6 Participant Roles; 3.2.7 Rapid Release; 3.2.8 Blackbox Programming; 3.2.9 OSS Practices; 3.3 OSS-Like Development; 3.3.1 Agile Practices; 3.3.2 Communication Proximity; 3.3.3 Loose and Tight Couples; 3.3.4 Collocated Software Development; 3.4 Conclusion; References; Part II: Rhythms; 4 PLAGIARISM PROGRAMMING; 4.1 Plagiarism; 4.1.1 Existing Code; 4.1.2 Social Network Analysis; 4.1.3 Being Plagiarized 327 $a4.1.4 Turn Everyone into a Programmer4.1.5 Pattern Language; 4.1.6 Software Team Capability; 4.1.7 Rough-Cut Design; 4.1.8 Training Is Not a Solution; 4.2 Nothing Faster than Plagiarism; 4.2.1 Immorality; 4.2.2 Unprecedented Code; 4.2.3 People Network; 4.2.4 Rhythm for Plagiarism; 4.2.5 Plagiarism at Work; 4.3 Business and Rhythm for Plagiarism; 4.3.1 15-Minute Business Presentation; 4.3.2 Marketing Research; 4.3.3 Chatting Robot; 4.3.4 Old Song, New Singer; References; 5 PAIR PROGRAMMING; 5.1 Art and Science; 5.1.1 The Right Partner; 5.1.2 Noisy Programming; 5.1.3 Just Training 327 $a5.1.4 Pay to Watch5.2 Two Worlds; 5.2.1 Moneyless World; 5.2.2 Money-Led World; 5.2.3 Economics; 5.2.4 Mythical Quality-Time; 5.2.5 Elapsed Time Accelerated; 5.2.6 Critical Path Method; 5.2.7 Why Two, Not Three: The Antigroup Phenomenon; 5.2.8 Software Requirements Are Puzzles; 5.3 Programming Task Demands; 5.3.1 2 and 4 Is 6; 5.3.2 2 and 4 Is 4; 5.3.3 2 and 4 Is 3; 5.3.4 2 and 4 2; 5.3.5 2 and 4 is Unknown; 5.4 Pair Programming Is More than Programming; 5.4.1 Design by Code; 5.4.2 Pair Design; 5.4.3 Rhythmic Pair Programming; 5.5 Pair Programming Team Coached; References 327 $a6 REPEAT PROGRAMMING 330 $aAn accessible, innovative perspective on using the flexibility of agile practices to increase software quality and profitability When agile approaches in your organization don't work as expected or you feel caught in the choice between agility and discipline, it is time to stop and think about software development rhythms! Agile software development is a popular development process that continues to reshape philosophies on the connections between disciplined processes and agile practices. In Software Development Rhythms, authors Lui and Chan explain how adopting one practice and combining 606 $aComputer software$xDevelopment 615 0$aComputer software$xDevelopment. 676 $a005.1 700 $aLui$b Kim Man$01643139 701 $aChan$b Keith C. C$01643140 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910814546703321 996 $aSoftware development rhythms$93988201 997 $aUNINA