Agile Processes in Software Engineering and Extreme Programming
13th International Conference, XP 2012, Malmö, Sweden, May 21-25, 2012, Proceedings
Published on 12. May 2012
X, 202 pages
978-3-642-30350-0 (ISBN)
Description
This book contains the refereed proceedings of the 13th International Conference on Agile Software Development, XP 2012, held in Malmö, Sweden, in May 2012.
In the last decade, we have seen agile and lean software development strongly influence the way software is developed. Agile and lean software development has moved from being a way of working for a number of pioneers to becoming, more or less, the expected way of developing software in industry. The topics covered by the selected full papers include general aspects of agility, agile teams, studies related to the release and maintenance of software, and research on specific practices in agile and lean software development. They are complemented by four short papers capturing additional aspects of agile and lean projects.
More details
Other editions
Additional editions
Claes Wohlin
Agile Processes in Software Engineering and Extreme Programming
13th International Conference, XP 2012, Malmö, Sweden, May 21-25, 2012, Proceedings
Book
05/2012
1st Edition
Springer
€53.49
Shipment within 7-9 days
Content
- Title
- Preface
- Organization
- Table of Contents
- Being Agile
- Agile Principles as Software Engineering Principles: An Analysis
- Introduction
- Conceptual Framework and Methodology
- Three Key Concepts: Value, Principle, Practice
- Principles Analysis Method
- Analysis of the Agile Manifesto Principles
- Analysis of Three Agile Methods Principles
- eXtreme Programming
- Scrum
- DSDM
- Discussion
- Conclusion
- References
- Agile Software Development Practice Adoption Survey
- Introduction
- Related Work
- Literature on Agile Practices
- Agile Surveys
- Survey Design
- Results
- Survey Demographics
- Commonality of Agile Practice Usage
- Combination of Agile Practices
- Compliance to Agile Development Processes (XP and Scrum)
- Success of Adoption
- Conclusion
- References
- Applying Agile Development in Mass-Produced Embedded Systems
- Introduction
- Context and Problem Statement
- Case 1: Introduction of Distributed Software Architecture
- Case 2: Architecture Maintenance Process
- Case 3: Development Project of an Infotainment System
- Research Problem
- Research Methodology
- Method for Introducing Agile Software Development in Mass-Produced Embedded Systems
- Requirements
- Product Project Gates
- Validation
- Software Delivery
- Internal Activities
- Method Validation
- Case 4: Agile Development of an Infotainment Sub-system
- Case 5: Climate Control Software
- Case 6: Next Generation Infotainment System
- Method Use in the Three Cases
- Related Work
- Summary
- References
- Agile Teams
- Understanding Team Dynamics in Distributed Agile Software Development
- Introduction
- Research Method
- Grounded Theory
- Data Collection
- Participant and Project Details
- Data Analysis
- Results
- `One Team' Mindset
- Personal Touch
- Open Communication
- Team Collocation
- Team Ambassadors
- Coach Travels
- Discussion
- Limitations
- Conclusion
- References
- Information Flow within a Dispersed Agile Team: A Distributed Cognition Perspective
- Introduction
- The Study
- The Team
- Data Gathering
- Distributed Cognition
- DiCOT (Distributed Cognition for Teamwork)
- DiCOT Analysis
- Physical Layout to Support Cognition
- Artefacts Created or Used
- Information Flow
- Discussion
- Agile Dispersed Development and Global Software Development Issues
- Co-located Agile versus Dispersed Agile
- Limitations
- Conclusions and Future Work
- References
- Sensing High-Performing Software Teams: Proposal of an Instrument for Self-monitoring
- Introduction
- Background and Related Work
- High-Performing Teams
- Software Team Performance
- Developing High-Performing Teams
- Knowledge Gaps and Research Needs
- Instrument Design and Analysis Principles
- Instrument for Self-monitoring
- Analysis Guidelines
- Case Studies
- Student Case
- Industrial Cases
- Comparisons
- Discussion
- Analysis and Evaluation
- Implications
- Future Work
- Conclusions
- References
- Release and Maintanance
- Release Readiness Indicator for Mature Agile and Lean Software Development Projects
- Introduction
- Related Work
- Organizational Context
- ISO/IEC 15939
- Streamline Development, SD
- Research Method and Study Design
- Release Readiness (RR) Indicator
- Time to Release
- Results from Evaluation
- Evaluation Results
- Validity Evaluation
- Conclusions
- References
- A Palette of Lean Indicators to Detect Waste in Software Maintenance: A Case Study
- Introduction
- Related Work
- Palette of Lean Indicators for Software Maintenance
- Maintenance Inflow (M1)
- Visualization through Cumulative Flow Diagrams (M2)
- Lead-Time (M3)
- Workload (M4)
- Combined Analysis
- Research Method
- Case and Context
- Unit of Analysis
- Proposition
- Data Collection and Analysis
- Validity Threats
- Results
- Indicator for Maintenance Inflow (M1)
- Indicator for Flow of MRs (M2)
- Lead-Time Measurement (M3)
- Workload (M4)
- Combined Analysis
- Discussion
- Conclusion
- References
- A Comparative Study of Scrum and Kanban Approaches on a Real Case Study Using Simulation
- Introduction
- The Case-Study and the Related Processes
- The Original Process
- The Lean-Kanban Process
- The Scrum Process
- Agent-Based Process Modeling
- The Model of the Original Process
- The Model of the Scrum Process
- Results and Discussion
- The Original Process
- The Kanban Process
- The Scrum Process
- Conclusions and Future Work
- References
- Specific Agile Practices
- Impact of Test Design Technique Knowledge on Test Driven Development: A Controlled Experiment
- Motivation
- Problem Statement
- Research Objective
- Context
- Paper Outline
- Related Work
- TDD and Testing Knowledge
- Experiments in TDD
- Experimental Design
- Goals, Hypotheses, Parameters, and Variables
- Experiment Design
- Subjects
- Objects
- Instrumentation
- Data Collection Procedure
- Execution
- Sample
- Preparation
- Data Collection Performed
- Analysis
- Descriptive Statistics
- Data Set Reduction
- Hypothesis Testing
- Interpretation
- Evaluation of Results and Implications
- Limitations of the Study
- Conclusions and Future Work
- Relation to Existing Evidence
- Impact
- Future Work
- References
- Escalation of Commitment: A Longitudinal Case Study of Daily Meetings
- Background
- Decision Making in Agile Software Development
- Escalating Commitment
- Research Method
- Case Study Design
- Study Context
- Data Collection and Analysis
- Results
- The Team Justifying Their Decisions to the Product Owner
- Team Members Justifying Their Decisions to Each Other
- Discussion
- Psychological Self-justification
- Social Self-justification
- Implications for Practice
- Conclusions and Further Work
- References
- Short Papers
- Agile User Stories Enriched with Usability
- Introduction
- Specifying Functional Usability Features
- Documenting Usability in User Stories
- Tool and Process
- Proof of Concept
- Conclusion
- References
- Evidence-Based Timelines for Agile Project Retrospectives - A Method Proposal
- Introduction
- Retrospectives
- Research Approach
- Creating Evidence-Base Timelines
- Discussion
- Conclusions
- References
- Who Is Stronger in Your Agile Deployment - The Id or the Superego?
- Introduction
- Who Is Stronger - The Id or the Superego?
- How to Build a Dominant Superego?
- How Does the Dominant Superego Approach Agile Deployment?
- What Is Next?
- References
- adVANTAGE: A Fair Pricing Model for Agile Software Development Contracting
- Introduction
- Challenges in Traditional Project Contracting
- Challenges in Agile Project Contracting
- Related Work
- The adVANTAGE Contracting Model
- Industry Example and Conclusion
- References
- Author Index
