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