Agile Processes in Software Engineering and Extreme Programming 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, Proceedings
The volume constitutes the proceedings of the 18th International Conference on Agile Software Development, XP 2017, held in Cologne, Germany, in May 2017. The 14 full and 6 short papers presented in this volume were carefully reviewed and selected from 46 submissions.
Uložené v:
| Hlavní autori: | , , |
|---|---|
| Médium: | E-kniha |
| Jazyk: | English |
| Vydavateľské údaje: |
Cham
Springer Nature
2017
Springer Open Springer International Publishing AG Springer |
| Vydanie: | 1 |
| Edícia: | Lecture Notes in Business Information Processing |
| Predmet: | |
| ISBN: | 331957633X, 9783319576336, 9783319576329, 3319576321 |
| On-line prístup: | Získať plný text |
| Tagy: |
Pridať tag
Žiadne tagy, Buďte prvý, kto otaguje tento záznam!
|
Obsah:
- Intro -- Preface -- Organization -- Contents -- Improving Agile Processes -- Reflection in Agile Retrospectives -- Abstract -- 1 Introduction -- 2 Related Work -- 2.1 Agile Retrospective Meeting -- 2.2 Reflective Practice -- 3 Research Method -- 3.1 Data Collection -- 3.2 Data Analysis -- 4 Findings -- 4.1 Reporting and Responding -- 4.2 Relating and Reasoning -- 4.3 Reconstructing -- 5 Discussion -- 5.1 A Framework of Reflection in Agile Retrospective Meeting -- 5.2 Levels of Reflection Build on Each Other -- 5.3 Implications for Research and Practice -- 5.4 Limitations -- 6 Conclusion -- Acknowledgement -- References -- What Influences the Speed of Prototyping? An Empirical Investigation of Twenty Software Startups -- Abstract -- 1 Introduction -- 2 Background -- 2.1 Business Driven Experimentation -- 2.2 Prototype and Prototyping Activities -- 2.3 A Prototype-Centric Learning Model in Software Startups -- 3 Research Approach -- 3.1 Multiple Case Study Design -- 3.2 Data Collection and Analysis -- 3.3 Case Description -- 4 Result -- 4.1 Elements Influencing Throwaway Prototyping -- 4.1.1 Adoption of Collaborative Mock-up Tools -- 4.1.2 UX Designer Onboard -- 4.1.3 Choices of Faking or Building -- 4.1.4 Collaboration Across Diverged Mindsets -- 4.1.5 Identification of a Right Set of Feedbacks -- 4.1.6 Fostering Customer Knowledge and Embedding into Prototypes -- 4.2 Elements Influencing Evolutionary Prototyping -- 4.2.1 Utilizing Plug-and-Play Components in Prototype -- 4.2.2 Synchronizing Customer Feedback in Loops -- 4.2.3 Conflicting Feature Requests -- 4.2.4 Feature Creeps -- 4.2.5 Solid Technical Competence Onboard -- 4.2.6 Dependence on Fast Changing Technologies -- 5 Discussion -- 5.1 Reflections on the Results -- 5.2 Threats to Validity -- 6 Conclusions -- References -- Key Challenges in Agile Requirements Engineering -- Abstract
- An Assessment of Avionics Software Development Practice: Justifications for an Agile Development Process -- Abstract -- 1 Introduction -- 2 Research Method -- 3 Certification Aspects of Avionics Software Development -- 3.1 Overview of Document DO-178C -- 3.2 Assessment of Document DO-178C -- 4 Overview of Existing Research and Industry Experience -- 4.1 Why This Interest in Agile Methods? -- 4.2 Evidence and Documentation -- 4.3 More Flexible Management of Requirements and Change -- 4.4 Applicability and Obstacles -- 4.5 Team Efficiency and Motivation -- 4.6 Testing -- 4.7 Adoption of New Software Process Models -- 4.8 Relating Findings to Other Domains -- 5 Survey to Assess Present Practice -- 5.1 Respondents' and Organizations' Profiles -- 5.2 Maturity -- 5.3 Relationship to Safety Standards and Authorities -- 5.4 Life-Cycle Aspects -- 5.5 Perceived Challenges and Problems -- 6 Towards an DO-178-Aligned Agile Approach -- 6.1 Scrum Phases -- 6.2 Preparation Phase Activities -- 6.3 Development Phase Activities -- 6.4 Closure Phase Activities -- 6.5 Remarks and Potential Issues -- 7 Conclusions and Further Work -- Acknowledgments -- References -- Short Research Papers -- Inoculating an Agile Company with User-Centred Design: An Empirical Study -- Abstract -- 1 Introduction -- 2 Related Work -- 3 Action Research Intervention -- 3.1 Method -- 3.2 Preliminary Understanding -- 3.3 Implementation -- 3.4 Evaluation -- 4 Discussion -- Acknowledgments -- References -- On the Usage and Benefits of Agile Methods & -- Practices -- Abstract -- 1 Introduction -- 2 Chassis Systems Control of the Bosch Group -- 3 Study Design -- 4 Results -- 4.1 RQ1: Usage of Agile Methods and Practices -- 4.2 RQ2: Deviations of Agile Practices -- 4.3 RQ3: Benefits of Agile Practices -- 5 Related Works and Discussion -- 6 Validity of the Results -- 7 Conclusions and Future Work
- 6.1 Threats to the Validity -- 7 Final Considerations and Future Works -- Acknowledgments -- References -- Agile in Organizations -- Don't Forget to Breathe: A Controlled Trial of Mindfulness Practices in Agile Project Teams -- 1 Introduction -- 2 Background and Related Work -- 3 Research Method and Conduct -- 4 Results -- 5 Discussion -- 5.1 Three Minute Breathing Exercise in Agile Teams, Does It Work? -- 5.2 Mindfulness in Our Case Organisations: Barriers to Adoption -- 5.3 Mindfulness in Agile Project Teams: A Preliminary Research Agenda -- 5.4 Threats to Validity -- 6 Conclusions -- References -- Enhancing Agile Team Collaboration Through the Use of Large Digital Multi-touch Cardwalls -- 1 Introduction -- 2 Related Work -- 3 Pre-study Tool Usage -- 3.1 Study Method -- 3.2 Findings -- 3.3 Summary -- 4 aWall - Digital Agile Collaboration Wall -- 4.1 Design -- 4.2 User Interface -- 5 User Study -- 5.1 Participants -- 5.2 Procedure -- 5.3 Findings -- 6 Conclusions -- References -- Knowledge Sharing in a Large Agile Organisation: A Survey Study -- 1 Introduction -- 2 Related Work -- 3 Method -- 3.1 Collaborator Company -- 3.2 Procedure -- 3.3 Survey -- 3.4 Analysis -- 3.5 Respondents -- 4 Results -- 4.1 Knowledge Sharing Practices -- 4.2 Motivation for Knowledge Sharing -- 4.3 Ease of Knowledge Sharing -- 4.4 Relation of Agility and Ease of Knowledge Sharing -- 4.5 Relation of Frequency and Ease of Knowledge Sharing -- 5 Limitations -- 6 Discussion -- 7 Conclusions and Future Work -- References -- Teaching Agile Methods to Software Engineering Professionals: 10Years, 1000 Release Plans -- 1 Introduction -- 2 Course Outline -- 2.1 Pre-study Assignment: Case Study -- 2.2 Lectures -- 2.3 Group Exercises -- 2.4 Course Assignment: Essay and Release Plan -- 3 Discussion -- 4 Related Work -- 5 Conclusions -- 6 Agile Methods: Case Study Papers for 2016
- 1 Introduction -- 2 Related Work -- 3 Research Method -- 3.1 General Study Design -- 3.2 Panel of Experts -- 3.3 Round 1 -- 3.4 Round 2 -- 3.5 Round 3 -- 4 Results and Discussion -- 4.1 (RQ1) What Are the Key Challenges in Agile Requirements Engineering? -- 4.2 (RQ2) How Can We Deal with the Identified Key Challenges? -- 4.3 Meaning of Findings -- 4.4 Limitations -- 5 Conclusions and Future Work -- Acknowledgements -- Appendix -- References -- Eeny, Meeny, Miny, Mo... -- 1 Introduction -- 2 Background -- 2.1 Selection Framework for a Collecting Technique -- 2.2 Techniques for User-Interaction Data Collecting -- 3 Research Approach -- 3.1 Explanatory Case Study -- 3.2 Case Organizations -- 4 Results -- 4.1 The Processes of Choosing a Collecting Technology -- 4.2 Reasons for Choosing a Collecting Technique -- 5 Discussion -- 6 Conclusions -- References -- Comparing Requirements Decomposition Within the Scrum, Scrum with Kanban, XP, and Banana Development ... -- Abstract -- 1 Introduction -- 2 Background and Related Work -- 3 The Multiple Case Study -- 3.1 Study Goal -- 3.2 Study Design -- 3.3 Study Execution -- 3.4 Data Collection and Analysis -- 4 Study Results -- 5 Threats to Validity -- 6 Conclusion and Future Work -- References -- Effects of Technical Debt Awareness: A Classroom Study -- Abstract -- 1 Introduction -- 2 Related Work -- 3 Context: Extreme Programming Laboratory -- 3.1 Projects -- 3.2 The Informative Workspace -- 3.2.1 Boards -- 3.2.2 Tools -- 4 Research Methods -- 4.1 Technical Debt Identification -- 4.1.1 XP Lab 2013 -- 4.1.2 XP Lab 2014 -- 4.2 Second Step - Interviews and Questionnaires -- 4.2.1 XP Lab 2013 -- 4.2.2 XP Lab 2014 -- 4.3 Third Step - Data Analysis -- 5 Results -- 5.1 Open Coding -- 5.2 Axial Coding -- 5.3 Selective Coding -- 5.4 The Code Analysis with the Tools -- 6 Discussion of the Findings
- References -- Are Software Startups Applying Agile Practices? The State of the Practice from a Large Survey -- 1 Introduction -- 2 Related Work -- 2.1 Agile Methods in Software Startups -- 2.2 Lean Startup and Agile Practices -- 3 Research Method -- 3.1 Survey Questions -- 3.2 Data Cleaning and Validation -- 3.3 Data Analysis -- 4 Results -- 4.1 Agile Practices in Software Startups -- 4.2 Agile Practices in Lean Software Startups -- 5 Discussion -- 6 Conclusion -- References -- Adopting Test Automation on Agile Development Projects: A Grounded Theory Study of Indian Software O ... -- Abstract -- 1 Introduction -- 2 Research Method -- 2.1 Grounded Theory -- 2.2 Data Collection -- 2.3 Data Analysis -- 3 Results: Adopting Test Automation on Agile Projects -- 3.1 Challenge 1: Choosing the Right Tool -- 3.2 Challenge 2: Managing Test Environment -- 3.3 Challenge 3: Test Script Maintenance -- 3.4 Challenge 4: Mindset Toward Automation -- 3.5 Challenge 5: Effective Communication -- 4 Discussion and Related Work -- 5 Limitations -- 6 Conclusion -- Acknowledgments -- References -- Safety Critical Software -- How is Security Testing Done in Agile Teams? A Cross-Case Analysis of Four Software Teams -- Abstract -- 1 Introduction -- 2 Background on Software and Security Testing -- 2.1 Four Quadrants of Agile Testing -- 3 Research Methodology -- 4 Results -- 4.1 RQ 1: How Is the Traditional Security Engineering Process Managed/Organized in the Agile Teams? -- 4.2 RQ 2: How Does the Agile Teams Perform Security Testing in Each Testing Phase? -- 4.3 RQ 3: How Are Traditional Security Testing Techniques Generally Used in the Agile Software Devel ... -- 5 Discussion -- 5.1 Recommendations for Practice -- 5.2 Recommendations for Research -- 5.3 Work Limitations -- 6 Conclusion -- References
- Acknowledgements