Extreme Programming and Agile Methods - XP/Agile Universe 2002 Second XP Universe and First Agile Universe Conference Chicago, IL, USA, August 4-7, 2002.Proceedings

The 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...

Full description

Bibliographic Details
Other Authors: Wells, Don (Editor), Williams, Lauris (Editor)
Format: eBook
Language:English
Published: Berlin, Heidelberg Springer Berlin Heidelberg 2002, 2002
Edition:1st ed. 2002
Series:Lecture Notes in Computer Science
Subjects:
Online Access:
Collection: Springer Book Archives -2004 - Collection details see MPG.ReNa
LEADER 05833nmm a2200421 u 4500
001 EB001884280
003 EBX01000000000000001047647
005 00000000000000.0
007 cr|||||||||||||||||||||
008 191115 ||| eng
020 |a 9783540456728 
100 1 |a Wells, Don  |e [editor] 
245 0 0 |a Extreme Programming and Agile Methods - XP/Agile Universe 2002  |h Elektronische Ressource  |b Second XP Universe and First Agile Universe Conference Chicago, IL, USA, August 4-7, 2002.Proceedings  |c edited by Don Wells, Lauris Williams 
250 |a 1st ed. 2002 
260 |a Berlin, Heidelberg  |b Springer Berlin Heidelberg  |c 2002, 2002 
300 |a XII, 296 p  |b online resource 
505 0 |a 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? --  
505 0 |a XP - Beyond Limitations? -- Extreme Fishbowl -- Agile Experiences 
505 0 |a Methods 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 --  
505 0 |a 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 ofAgile Practices: A Student Survey -- Tutorials -- XP in a Legacy Environment -- XP for a Day --  
653 |a Compilers (Computer programs) 
653 |a Computer Science Logic and Foundations of Programming 
653 |a Compilers and Interpreters 
653 |a Software engineering 
653 |a Programming Techniques 
653 |a Computer science 
653 |a Computer programming 
653 |a Software Engineering 
653 |a Electronic data processing / Management 
653 |a IT Operations 
700 1 |a Williams, Lauris  |e [editor] 
041 0 7 |a eng  |2 ISO 639-2 
989 |b SBA  |a Springer Book Archives -2004 
490 0 |a Lecture Notes in Computer Science 
028 5 0 |a 10.1007/3-540-45672-4 
856 4 0 |u https://doi.org/10.1007/3-540-45672-4?nosfx=y  |x Verlag  |3 Volltext 
082 0 |a 005.1 
520 |a The 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)