000 06340nam a22005415i 4500
001 978-3-540-45672-8
003 DE-He213
005 20160624102006.0
007 cr nn 008mamaa
008 121227s2002 gw | s |||| 0|eng d
020 _a9783540456728
_9978-3-540-45672-8
024 7 _a10.1007/3-540-45672-4
_2doi
050 4 _aQA76.6-76.66
072 7 _aUM
_2bicssc
072 7 _aCOM051000
_2bisacsh
082 0 4 _a005.11
_223
245 1 0 _aExtreme Programming and Agile Methods — XP/Agile Universe 2002
_h[electronic resource] :
_bSecond XP Universe and First Agile Universe Conference Chicago, IL, USA, August 4–7, 2002 Proceedings /
_cedited by Don Wells, Laurie Williams.
260 1 _aBerlin, Heidelberg :
_bSpringer Berlin Heidelberg,
_c2002.
264 1 _aBerlin, Heidelberg :
_bSpringer Berlin Heidelberg,
_c2002.
300 _aXII, 296 p.
_bonline resource.
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
347 _atext file
_bPDF
_2rda
490 1 _aLecture Notes in Computer Science,
_x0302-9743 ;
_v2418
505 0 _aMethods and Support Tools -- Designing Requirements: Incorporating Usage-Centered Design into an Agile SW Development Process -- Supporting Distributed Extreme Programming -- Using Ant to Solve Problems Posed by Frequent Deployments -- Supporting Adaptable Methodologies to Meet Evolving Project Needs -- Introducing Extreme Programming and Agile Methods -- Strategies for Introducing XP to New Client Sites -- Establishing an Agile Testing Team: Our Four Favorite “Mistakes” -- Turning the Knobs: A Coaching Pattern for XP through Agile Metrics -- Experience Reports -- Agile Project Management Methods for ERP: How to Apply Agile Processes to Complex COTS Projects and Live to Tell about It -- Extreme Programming in a Research Environment -- Tailoring XP for Large System Mission Critical Software Development -- Testing -- Acceptance Testing HTML -- Probe Tests: A Strategy for Growing Automated Tests around Legacy Code -- An Informal Formal Method for Systematic JUnit Test Case Generation -- A Light in a Dark Place: Test-Driven Development with 3rd Party Packages -- Empirical Studies -- Agile Meets CMMI: Culture Clash or Common Cause? -- Circle of Life, Spiral of Death: Are XP Teams Following the Essential Practices? -- Tracking Test First Pair Programming — An Experiment -- How to Get the Most out of Extreme Programming/Agile Methods -- Empirical Findings in Agile Methods -- Pair Programming -- Exploring the Efficacy of Distributed Pair Programming -- Pair Programming: Addressing Key Process Areas of the People-CMM -- When Pairs Disagree, 1-2-3 -- Educator’s Symposium -- Triggers and Practice: How Extremes in Writing Relate to Creativity and Learning -- Extreme Teaching — An Agile Approach to Education -- Extreme Programming as a Teaching Process -- From the Student’s Perspective -- Perceptions of Agile Practices: A Student Survey -- Tutorials -- XP in a Legacy Environment -- XP for a Day -- Accelerated Solution Centers — Implementing DSDM in the Real World -- Refactoring: Improving the Design of Existing Code -- The Agile Database -- Change Wizardry - Tools for Geeks -- Beyond the Customer: Agile Business Practices for XP -- XP Release Planning and User Stories -- Steering the Big Ship: Succeeding in Changing an Organization’s Practices -- Scrum and Agile 101 -- How to Be a Coach -- Sharpening the Axe for Test Driven Development -- Pair Programming: Experience the Difference -- How to Start an XP Project: The Initial Phase -- Effective Java Testing Strategies -- Test Drive for Testers: What, When, and How Testers Do for XP Teams -- Scaling Agile Processes: Agile Software Development in Large Projects -- Applying XP Tools to J2EE for the Extreme Programming Universe -- Workshops -- Distributed Pair Programming -- Agile Acceptance Testing -- XP Fest -- Empirical Evaluation of Agile Processes -- Panels -- Are Testers eXtinct? How Can Testers Contribute to XP Teams? -- XP - Beyond Limitations? -- Extreme Fishbowl -- Agile Experiences.
520 _aThe second XP Universe and ?rst Agile Universe brought together many p- ple interested in building software in a new way. Held in Chicago, August 4–7, 2002 it attracted software experts, educators, and developers. Unlike most c- ferences the venue was very dynamic. Many activities were not even well de?ned in advance. All discussions were encouraged to be spontaneous. Even so, there were some written words available and you are holding all of them now. We have collected as much material as possible together into this small volume. It is just the tip of the iceberg of course. A reminder to us of what we learned, the people we met, and the ideas we expressed. The conference papers, including research and experience papers, are rep- duced in these proceedings. Forty-one (41) papers were submitted. Each subm- ted paper received three reviews by program committee members. The program committee consisted of 40 members. Papers submitted by program committee members were refereed separately. This ensured that reviewers could provide an honest feedback not seen by the paper submitters. In many cases, the program committee shepherded authors to signi?cantly improve their initial submission prior to completing the version contained in these proceedings. In the end, the program committee chose 25 papers for publication (60% acceptance).
650 0 _aComputer science.
650 0 _aSoftware engineering.
650 0 _aLogic design.
650 0 _aInformation Systems.
650 1 4 _aComputer Science.
650 2 4 _aProgramming Techniques.
650 2 4 _aSoftware Engineering.
650 2 4 _aProgramming Languages, Compilers, Interpreters.
650 2 4 _aLogics and Meanings of Programs.
650 2 4 _aManagement of Computing and Information Systems.
700 1 _aWells, Don.
_eeditor.
700 1 _aWilliams, Laurie.
_eeditor.
710 2 _aSpringerLink (Online service)
773 0 _tSpringer eBooks
776 0 8 _iPrinted edition:
_z9783540440246
786 _dSpringer
830 0 _aLecture Notes in Computer Science,
_x0302-9743 ;
_v2418
856 4 0 _uhttp://dx.doi.org/10.1007/3-540-45672-4
942 _2EBK5511
_cEBK
999 _c34805
_d34805