LEADER 05661nam 2200769Ia 450 001 9910818861003321 005 20200520144314.0 010 $a9786612136924 010 $a9781282136922 010 $a1282136925 010 $a9780470385883 010 $a047038588X 010 $a9780470385876 010 $a0470385871 035 $a(CKB)1000000000687356 035 $a(EBL)427745 035 $a(OCoLC)646796242 035 $a(SSID)ssj0000240047 035 $a(PQKBManifestationID)11187812 035 $a(PQKBTitleCode)TC0000240047 035 $a(PQKBWorkID)10251120 035 $a(PQKB)10866360 035 $a(MiAaPQ)EBC427745 035 $a(Au-PeEL)EBL427745 035 $a(CaPaEBR)ebr10275716 035 $a(CaONFJC)MIL213692 035 $a(OCoLC)212908931 035 $a(FINmELB)ELB178468 035 $a(Perlego)2767285 035 $a(EXLCZ)991000000000687356 100 $a20080228d2008 uy 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 10$aRunning an agile software development project /$fMike Holcombe 205 $a1st ed. 210 $aHoboken, N.J. $cWiley$dc2008 215 $a1 online resource (328 p.) 300 $aDescription based upon print version of record. 311 08$a9780470136690 311 08$a0470136693 320 $aIncludes bibliographical references (p. 305-308) and index. 327 $aRunning an Agile Software Development Project; Contents; Preface; 1. What Is an Agile Methodology?; 1.1 Rapid Business Change: The Ultimate Driver; 1.2 What Must Agile Methodologies be Able to Do?; 1.3 Agility: What Is It and How Do We Achieve It?; 1.4 Evolving Software: Obstacles and Possibilities; 1.5 The Quality Agenda; 1.6 Do We Really Need All This Mountain of Documentation?; 1.7 The Human Factor; 1.8 Some Agile Methodologies; 1.8.1 Dynamic Systems Development Method; 1.8.2 Feature-Driven Design; 1.8.3 Crystal; 1.8.4 Agile Modeling; 1.8.5 SCRUM; 1.8.6 Summary Table; 1.9 Review; Exercise 327 $aConundrumReferences; 2. Extreme Programming Outlined; 2.1 Some Guiding Principles; 2.2 The Five Values; 2.2.1 Communication; 2.2.2 Feedback; 2.2.3 Simplicity; 2.2.4 Courage; 2.2.5 Respect; 2.3 The 12 Basic Practices of XP; 2.3.1 Test-First Programming; 2.3.2 Pair Programming; 2.3.3 On-Site Customer; 2.3.4 The Planning Game; 2.3.5 System Metaphor; 2.3.6 Small, Frequent Releases; 2.3.7 Always Use the Simplest Solution That Adds Business Value; 2.3.8 Continuous Integration; 2.3.9 Coding Standards; 2.3.10 Collective Code Ownership; 2.3.11 Refactoring; 2.3.12 Forty-Hour Week; 2.4 Can XP Work? 327 $a2.5 The Evidence for XP2.5.1 Evidence for Test First; 2.5.2 Evidence for Pair Programming; 2.5.3 Evidence for XP; 2.6 Preparing to XP; Exercise; Conundrum; References; 3. Foundations: People and Teams Working Together; 3.1 Software Engineering in Teams; 3.2 Personalities and Team Success; 3.3 Observations of Team Behavior in XP Projects; 3.4 Setting Up a Team; 3.5 Developing Team Skills; 3.6 Training Together; 3.7 Finding and Keeping a Client for a University-Based Project or a Small Business Start-Up; 3.8 The Organizational Framework; 3.9 Planning 327 $a3.9.1 PERT (Program Evaluation and Review Technique)3.9.2 Gantt Charts; 3.10 Dealing with Problems; 3.10.1 Basic Strategies; 3.10.2 When Things Go Really Wrong; 3.11 Risk Analysis; 3.12 Review; Exercises; Conundrum; References; 4. Starting an XP Project; 4.1 Project Beginnings; 4.1.1 Researching the Business Background; 4.1.2 Exploring the Outline System Description; 4.2 The First Meetings with the Client; 4.3 Business Analysis and Problem Discovery; 4.4 The Initial Stages of Building a Requirements Document; 4.5 Techniques for Requirements Elicitation; 4.6 Putting Your Knowledge Together 327 $a4.7 Getting Technical4.8 Developing the Requirements Documents; 4.9 Specifying and Measuring the Quality Attributes of the System; 4.9.1 Identifying Attributes; 4.9.2 Specifying the Acceptable Level of an Attribute; 4.9.3 User Characteristics and User Interface Characteristics; 4.10 The Formal Requirements Document and System Metaphor; 4.10.1 Commentary; 4.11 Contract Negotiation; 4.12 Case Study: The Impact of Organizational Politics; 4.13 Review; Conundrum; References; 5. Identifying Stories and Preparing to Build; 5.1 Looking at the User Stories; 5.2 Collections of Stories 327 $a5.2.1 Pharmacovigilance 330 $aA Practical Approach To Building Small To Medium Software Systems For Real Business Clients Based on more than 100 actual commercial projects, this book clearly explains how to run an agile software development project that delivers high-quality, high-value solutions to business clients. It concentrates on the practical, social, business, and management aspects as well as the technical issues involved. Professor Holcombe successfully connects readers with the wave of ""Agile 2.0"" concepts that take the techniques of agile development and place them in the service of business goals. Since 606 $aComputer software$xDevelopment 606 $aAgile software development 606 $aeXtreme programming 615 0$aComputer software$xDevelopment. 615 0$aAgile software development. 615 0$aeXtreme programming. 676 $a005.1/1 676 $a005.11 700 $aHolcombe$b W. M. L$g(William Michael Lloyd),$f1944-$047778 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910818861003321 996 $aRunning an agile software development project$94001618 997 $aUNINA