Agile Processes in Software Engineering and Extreme Programming (eBook)

Preface 5
Organization 7
Table of Contents 10
Essence: Facilitating Agile Innovation 14
Introduction 14
A New Outlook for Software Innovation 14
Product 15
Project 15
Process 16
People 16
SIRL- Software Innovation Research Lab 17
Essence – Innovation in the Agile Team 18
Product 19
Project 20
Process 20
People 20
Early Experiments with Essence and SIRL 20
Experiences with Physical Space 21
Experiences with Logical Views 22
Conclusion 22
References 23
Scrum and Team Effectiveness: Theory and Practice 24
Introduction 24
Research Design and Method 25
Study Context 25
Data Sources and Analysis 25
Team Effectiveness The “Big Five” and Scrum
Coordinating Mechanisms 26
The “Big Five” of Teamwork 29
Conclusion and Further Work 31
References 32
Misfit or Misuse? Lessons from Implementation of Scrum in Radical Product Innovation 34
Introduction 34
Related Work 35
Case Study 36
Case Background 36
Research Approach 36
Analysis Framework 37
Analysis 37
Observations 38
Summary 41
Discussion 41
Limitations and Future Work 42
Conclusion 43
References 43
Method Configuration: The eXtreme Programming Case 45
Introduction 45
Research Approach 46
Method for Method Configuration—Key Concepts 47
The Method Component Concept 48
The Configuration Package 49
The Configuration Template 50
Empirical Examples 50
Lessons Learned 51
Concluding Discussion 52
References 53
Adopting Agile in a Large Organisation 55
Introduction 55
Adopting Agile in Large Organisations 56
Technological Frames 56
The Empirical Study: Data Gathering and Analysis 57
The Case Study Organisation 57
Data Gathering 57
Data Analysis 58
Results: Making Sense of Agile 58
Agile Advocates and Coaches 58
The Agile Software Development Team 61
Project Z 62
The ‘Business’ (or Customer Proxy) 63
Discussion 64
Conclusions 64
References 65
An Observational Study of a Distributed Card Based Planning Environment 66
Introduction 66
Related Works 67
Distributed AgilePlanner (DAP) 68
Interacting with Planning Artifacts 69
Distributed Planning 69
Study Design 70
Participants and Context 70
Data Collection and Evaluation Criteria 71
Study Results 71
Observations 71
Feedback 72
Real-Time Performance 73
Limitations 73
Conclusions 74
References 74
The TDD-Guide Training and Guidance Tool for Test-Driven Development 76
Introduction 76
TDD-Guide and the AOPS Framework 77
TDD-Guide User-Interface 78
Rule Definition 78
Evaluating TDD-Guide 80
First Experiment 80
Second Experiment 81
Conclusion and Future Work 84
References 85
JExample: Exploiting Dependencies between Tests to Improve Defect Localization 86
Introduction 86
Related Work 87
JExample in a Nutshell 89
Case Study 90
Evaluation Procedure 91
Results 92
Discussion and Conclusion 94
An Agile Development Process and Its Assessment Using Quantitative Object-Oriented Metrics 96
Introduction 96
The Agile Practices Used 97
The Project and Its Phases 99
Software Metrics 100
FlossAr Metrics Evolution 101
Discussion 104
Conclusions 105
References 106
Historical Roots of Agile Methods: Where Did “Agile Thinking” Come From? 107
Introduction 107
What Does It Mean to Be Agile 108
The Author’s View 108
What Was Behind Agile Methods 109
Reaction to Traditional Approaches and Business Change 109
Reusing Ideas from History 109
People’s Experience 112
What’s New (and Not) About Agile Methods 113
Discussion and Conclusion 114
References 115
Seven Years of XP - 50 Customers, 100 Projects and 500 Programmers – Lessons Learnt and Ideas for Improvement 117
Introduction 117
The Observatory Context 118
Problems Associated with Introducing XP 119
Adoption of and Compliance with the XP Methodology 120
Areas Where XP Needs Strengthening and Supporting 121
People and XP 122
Conclusions 124
References 125
Applying XP to an Agile–Inexperienced Software Development Team 127
Introduction 127
The Study Context 128
Methodology 128
The Course 128
The Project 129
The Team 130
Project Constraints 130
Development Environment 131
Workload 131
Customer Involvement 131
Leadership 131
Team 131
Tracking 132
XP Practices 132
Achieved Results 135
Problems 135
Results 136
Lessons Learned 137
Conclusion 138
References 138
Investigating the Usefulness of Pair-Programming in a Mature Agile Team 140
Introduction 140
Related Work 141
The Study 141
Environment 142
Data 142
Results 143
Discussion 146
Limitations 147
Conclusions and Future Work 148
References 149
Just Enough Structure at the Edge of Chaos: Agile Information System Development in Practice 150
Introduction 150
Theoretical Background and Framework 151
The Research Approach and Case Setting 152
Analysis and Discussion 154
Individuals and Interaction over Processes and Tools 155
Working Software over Comprehensive Documentation 156
Customer Collaboration over Contract Negotiation 156
Responding to Change over Following a Plan 157
Conclusions 158
References 158
A Preliminary Conceptual Model for Exploring Global Agile Teams 160
Introduction 160
Literature Review 161
Agile Software Development Methods 161
Global Software Development 162
Virtual Teams 162
The Use of Agile Methods in Globally Distributed Environments 163
Conceptual Model 164
Team Structure 164
Team Agility 168
Team Virtualness 168
Challenges 169
Research Methodology 170
Conclusion 170
References 171
Scrum Implementation Using Kotter’s Change Model 174
Introduction 174
An Ever-Changing Software Development Industry 174
Agile Development 175
Scrum Model 175
Implementing Organisational Change 176
Case Study at Rhythm Ltd. 177
Research Methodology 177
Implementation of Kotter’s Change Model 178
Discussion 182
Conclusion 182
References 183
Agile Estimation with Monte Carlo Simulation 185
Introduction 185
Background 186
Our Approach 187
Conclusion 191
References 192
The Pomodoro Technique for Sustainable Pace in Extreme Programming Teams 193
Introduction 193
Pomodori for Time Boxing 194
Applying the Pomodoro Technique in XP 194
Case Study: XP User Groups and Teams 195
Concluding Remarks 196
Adopting Iterative Development: The Perceived Business Value 198
Background 198
Findings and Observations 199
Implications for Practice 202
References 202
Explicit Risk Management in Agile Processes 203
Introduction 203
The DaVinci Transform Project 204
The Stakeholders 204
Methodologies 204
The Product 204
Implicit Risk Management in Agile Processes 205
The Need for Explicit Risk Management in Agile Processes 205
Team DaVinci Risk Management Framework 206
Experiences with Explicit Risk Management and Agile Processes 207
Lessons Learned 210
Risk Manager Role 210
Wiki 210
Small Team Software Risk Evaluation 211
Mitigation Tasks in Sprint Backlog 211
Multiple Tasks Per Mitigation Strategy 211
Mitigation Trigger 211
Mid-Iteration Triggers 211
Multi-voting 212
Mitigation Strategies for New Risks 212
Conclusion 212
References 213
APDT: An Agile Planning Tool for Digital Tabletops 215
Introduction 215
Agile Planner for Digital Tabletops (APDT) 216
Reference 216
Investigating the Role of Trust in Agile Methods Using a Light Weight Systematic Literature Review 217
Introduction 217
Agile Methods 217
Trust 218
Systematic Literature Reviews 218
Results 219
Discussion 219
Conclusion 219
References 220
Agile Practices in a Product Development Organization 221
Introduction 221
Introduction of Agile Practices 221
Conclusion 222
Reference 222
Building and Linking a Metaphor: Finding Value! 223
Introduction 223
Evaluation 224
Conclusion 224
References 224
The Story of Transition to Agile Software Development 225
References 227
Predicting Software Fault Proneness Model Using Neural Network 228
Multi-modal Functional Test Execution 231
Introduction 231
Multi-modal Functional Test Execution 232
References 232
Social Network Analysis of Communication in Open Source Projects 233
The Value of Communication in Open Source Teams 233
Social Network Analysis 233
The Social Network of Open Source Communities 234
References 234
Toward Empowering Extreme Programming from an Architectural Viewpoint 235
References 236
A Metric-Based Approach to Assess Class Testability 237
References 238
Inside View of an Extreme Process 239
Introduction 239
XP Motivation 239
The Project 239
Evaluating the Process 240
Conclusion 240
References 240
To Track QA Work or Not That Is the Question
References 242
Build Notifications in Agile Environments 243
Introduction 243
Previous Work 243
Experimental Setup 243
Results and Discussion 244
Conclusion and Future Work 244
References 244
Supporting Distributed Pair Programming with the COLLECE Groupware System: An Empirical Study 245
Supporting Distributed Pair Programming: An Empirical Study 245
References 246
Experience on the Human Side of Agile 247
Overview 247
References 248
Retrospective Exploration Workshop 249
Overview 249
About the Session Organizers 250
References 250
Exposing the “Devils” within: Agile Taboos in a Large Organization 251
Workshop Overview 251
Organizers’ Experience 252
BIOHAZARD – Engineering the Change Virus 253
Synopsis 253
Who Should Attend? 253
Presenter's Background 254
Workshop History 254
Architecture-Centric Methods and Agile Approaches 255
Overview 255
Objectives 256
Workshop Format 256
References 256
Exploring Agile Coaching 257
Workshop Summary 257
Participation 257
Deliverables 257
Content and Process 257
Timetable 258
Workshop Organizers 258
The Agile Technique Hour 259
Introduction 259
The Aims of the Workshop 259
Overview of the Process 260
References 260
AOSTA: Agile Open Source Tools Academy 261
Workshop Description 261
About the Facilitators 262
There's No Such Thing as Best Practice 263
Culture and Agile: Challenges and Synergies 264
Steven Fraser (panel impresario) 264
Pekka Abrahamsson 265
Robert Biddle 265
Jutta Eckstein 266
Philippe Kruchten 267
Dennis Mancl 267
Werner Wild 268
Architecture and Agility Are Not Mutually Exclusive 269
Author Index 270