This event has ended. Visit the official site or create your own event on Sched.

Sign up or log in to bookmark your favorites and sync them to your phone or calendar.

Research Paper [clear filter]
Tuesday, May 23

14:15 CEST

Don't Forget to Breathe: A Controlled Trial of Mindfulness Practices in Agile Project Teams
While the effects of mindfulness are increasingly explored across different fields, little is known about the application of these practices in agile project teams. In this paper we report on a rigorous controlled trial executed to understand the impact of the three-minute breathing exercise on the perceived effectiveness of stand-up meetings. We compare (1) an active group using a three minute breathing exercise, to (2) a placebo, and (3) a control group in 3 organizations and 8 teams with over 152 measurements. Our findings indicate an immediate positive impact on perceived effectiveness, decision-making and improved listening in the active groups compared to the placebo and natural history groups. We provide a preliminary agenda for future research based on our findings and previous evidence from other fields.

Peter den Heijer, Wibo Koole and Christoph Johann Stettina

avatar for  Christoph Johann Stettina

 Christoph Johann Stettina

Research & Innovation, Lab Leader, Leiden University - Centre for Innovation
Dr. Christoph Johann Stettina is the Agile for Excellence lead at Leiden University. He began his professional career in 2004 at Nokia where he worked on mobile phone and automotive connectivity systems. Christoph has a number of scientific contributions in the domain of agile project... Read More →

Tuesday May 23, 2017 14:15 - 14:45 CEST
Ballroom B 1st Floor

14:15 CEST

What Influences the Speed of Prototyping? An Empirical Investigation of Twenty Software Startups
It is essential for startups to quickly experiment business ideas by building tangible prototypes and collecting user feedback on them. As prototyping is an inevitable part of learning for early stage software startups, how fast startups can learn depends on how fast they can prototype. Despite of the importance, there is a lack of research about prototyping in software startups. In this study, we aimed at understanding what are factors influencing different types of prototyping activities. We conducted a multiple case study on twenty European software startups. The results are two folds; firstly we propose a prototype-centric learning model in early stage software startups. Secondly, we identify factors occurring either as barriers or as facilitators for prototyping in early stage software startups. The factors are grouped into
(1) artifacts,
(2) team competence,
(3) collaboration,
(4) customer and
(5) process dimensions.
To speed up a startup’s progress at the early stage, it is important to incorporate the learning objective into a well-defined collaborative approach of prototyping.

Anh Nguyen-Duc, Xiaofeng Wang and Pekka Abrahamsson

avatar for Anh Nguyen-Duc

Anh Nguyen-Duc

Researcher, NTNU
Outsourcing Lean startup Data mining Team coordination

Tuesday May 23, 2017 14:15 - 14:45 CEST
Belvedere 12th Floor

15:15 CEST

Are Daily Stand-Up Meetings Valuable? A Survey of Developers in Software Teams

The daily stand-up meeting is a widely used practice. However, what is more uncertain is how valuable the practice is to team members. We invited professional developers of a programming forum to a survey and obtained 221 responses. Results show that the daily stand-up meeting was used by 87% of those who employ agile methods. We found that even though the respondents on average were neutral towards the practice, the majority were either positive or negative. Junior developers were most positive and senior developers and members of large teams most negative. We argue that the value of the practice should be evaluated according to the team needs. Further, more work is needed to understand why senior developers do not perceive the meetings as valuable and how to apply the practice in large teams.

Viktoria Stray, Nils Brede Moe and Gunnar Bergersen

avatar for Viktoria Stray

Viktoria Stray

Associate Professor, Department of Informatics, University of Oslo
Associate Professor in Software Engineering (University of Oslo), Research Scientist (SINTEF Digital). MSc in Computer Science (Norwegian University of Science and Technology and University of California, Santa Barbara), PhD (University of Oslo and University of New South Wales... Read More →

Tuesday May 23, 2017 15:15 - 15:30 CEST
Ballroom B 1st Floor

15:30 CEST

Exploring Workflow Mechanisms and Task Allocation Strategies in Agile Software Teams

Task allocation is considered to be an important activity in project management, independent of the method used for software development. However, the process of allocating tasks in agile software development teams has not been a focus of empirical research. This research used case study research method and involved semi-structured interviews with 12 agile software practitioners working within a software development organization in India. The results explain the process of task allocation including four different mechanisms of workflow across teams: team independent, team dependent, skillset/module dependent and hybrid workflow. These include some common set of practices whereas others are team-specific factors. Furthermore, five different types of task allocation strategies were identified based on increasing levels of team and individual autonomy: individual-driven, manager-driven, team-driven, manager assisted and team assisted. Knowing these workflow mechanisms and task allocation strategies will help software teams and project managers to make effective distribution and allocation of tasks for smooth agile software development. Future research can suggest alternative methods to overcome the hurdles faced by agile teams during allocation of tasks.

Zainab Masood, Rashina Hoda and Kelly Blincoe

avatar for Zainab Masood

Zainab Masood

PHD Student, University of Auckland
Agile Software Development, Software Engineering, Software Testing , Agile Practices, Self-Assignment as Task Allocation Agile Practice

Tuesday May 23, 2017 15:30 - 15:45 CEST
Ballroom B 1st Floor

16:15 CEST

Adopting Test Automation on Agile Development Projects: A Grounded Theory Study of Indian Software Organizations

The role of test automation in Agile Software Development projects is of paramount importance. It is absolutely necessary to automate tests in agile development projects as the number of test cases will continue to grow with each successive sprint. Through a Grounded Theory study involving 38 agile practitioners from 18 different software organizations in India, we identified five key challenges faced by agile practitioners and different strategies to overcome those challenges while practicing test automation. Understanding these challenges and strategies would help agile teams in streamlining their test automation practices.

Sulabh Tyagi, Dr. Ritu Sibal and Dr. Bharti Suri

avatar for Sulabh Tyagi

Sulabh Tyagi

Teaching Research Fellow, NSIT, Delhi University
I am true Agilist at heart, I see myself as an agile change agent whose job is to help agile teams in streamlining their engineering as well as management practices in sync with agile principles and values.

Tuesday May 23, 2017 16:15 - 16:45 CEST
Ballroom C 1st Floor
Wednesday, May 24

12:00 CEST

Comparing Requirements Decomposition Within the Scrum, Scrum with Kanban, XP, and Banana Development Processes
Context: Eliciting requirements from customers is a complex task. In Agile processes, the customer talks directly with the development team and often reports requirements in an unstructured way. The requirements elicitation process is up to the developers, who split it into user stories by means of different techniques. Objective: We aim to compare the requirements decomposition process of an unstructured process and three Agile processes, namely XP, Scrum, and Scrum with Kanban. Method: We conducted a multiple case study with a replication design, based on the project idea of an entrepreneur, a designer with no experience in soft- ware development. Four teams developed the project independently, using four different development processes. The requirements were elicited by the teams from the entrepreneur, who was available to talk with the four groups during the project. Results: The teams decomposed the requirements using different techniques, based on the selected development process. Conclusion: Scrum with Kanban and XP resulted in the most effective processes from different points of view. Unexpectedly, decomposition techniques commonly adopted in traditional processes are still used in Ag- ile processes, which may reduce project agility and performance. Therefore, we be- lieve that decomposition techniques need to be addressed to a greater extent, both from the practitioners’ and the research points of view.

Davide Taibi, Valentina Lenarduzzi, Andrea Janes, Kari Liukkunen and Muhammad Ovais Ahmad

avatar for Davide Taibi

Davide Taibi

Assistant Professor, University of Bozan/Bolzano
Empirical Studies on Agile Processes, Software Quality, Code Smells, Continuous Integration, Agile Software Architectures and Microservices.

Wednesday May 24, 2017 12:00 - 12:30 CEST
Ballroom D 1st Floor

12:00 CEST

How Is Security Testing Done in Agile Teams? A Cross-Case Analysis of Four Software Teams.
Security testing can broadly be described as (1) the testing of security requirements that concerns confidentiality, integrity, availability, authentication, authorization, nonrepudiation and (2) the testing of the software to validate how much it can withstand an attack. Continuous agile testing, involves immediately integrating changes into the main system, continuously testing all changes and updating test cases to be able to run a regression test at any time to verify that changes have not broken existing functionality. Software companies have a challenge to systematically apply security testing in their processes nowadays. There is a lack of guidelines in practice as well as empirical studies in real-world projects on agile security testing; industry in general needs a more systematic approach to security. The main contribution of this paper is to deepen relevant knowledge and experience on the characterization security testing in an agile context. We related our synthesized findings to relevant literature in security testing in order to sketch state-of-practice on security agile testing and provide recommendations of ways to improve it based on lessons learned/ good practices from the cases.

Daniela S. Cruzes, Michael Felderer, Tosin Daniel Oyetoyan, Matthias Gander and Irdin Pekaric

avatar for Tosin Daniel Oyetoyan

Tosin Daniel Oyetoyan

Tosin Daniel Oyetoyan is a post-doctoral fellow at SINTEF. He received his PhD from NTNU. He has previously worked as a senior software developer and analyst in the banking sector and has developed solutions for both healthcare and automation systems. His research interests are in... Read More →

Wednesday May 24, 2017 12:00 - 12:30 CEST
Ballroom C 1st Floor

14:30 CEST

An Assessment of Avionics Software Development Practice: Justifications for an Agile Development Process
Avionic systems for communication, navigation, and flight control, and many other functions are complex and crucial components of any modern aircraft. Present day avionic systems are increasingly based on computers and a growing percentage of system complexity can be attributed to software. An error in the software of a safety-critical avionic system could lead to a catastrophic event, such as multiple deaths and loss of the aircraft. To demonstrate compliance with airworthiness requirements, certification agencies accept the use of RTCA document DO-178 for the software development. Avionics software development is typically complex and is traditionally reliant on a strict plan-driven development process, characterized by early fixture of detailed requirements and late production of working software. In this process, requirement changes and solving software errors can lead to much rework, and create a risk of budget and schedule overruns. This raises the question whether avionics software development could benefit from the application of agile approaches. Based on the results of three activities: 1) a literature study on industrial experience with the use of agile methods in a DO-178 context, 2) an expert assessment of the DO-178 objectives, and 3) a survey conducted among European avionics industry, an outline is presented of an agile development process, where Scrum is extended to achieve the DO-178 objectives. The application of agile methods is expected to support frequent delivery of working software and ability to respond to changes, resulting in reduced risk of budget and schedule overruns.

Geir Hanssen, Gosse Wedzinga and Martijn Stuip

avatar for Geir Kjetil Hanssen

Geir Kjetil Hanssen

Senior Research Scientist, SINTEF
Geir Kjetil Hanssen is a senior research scientist at SINTEF Digital, Norway. He has a PhD in software engineering from the Norwegian University of Science and Technology (NTNU). His main areas of interest are software engineering methodologies – in particular agile methods, software... Read More →

Wednesday May 24, 2017 14:30 - 15:00 CEST
Belvedere 12th Floor

14:30 CEST

Are Software Startups Really Using Agile? The State of the Practice from a Large Survey
Software startups operate under various uncertainties and the demand on their ability to deal with change is high. Agile methods are considered a suitable and viable development approach for them. However the competing needs for speed and quality may render certain agile practices less suitable than others in the startup context. The adoption of agile practices can be further complicated in software startups that adopt the Lean Startup approach. To make the best of agile practices, it is necessary to first understand whether and how they are used in software startups. This study targets at a better understanding of the use of agile practices in software startups, with a particular focus on lean startups. Based on a large survey of 1526 software startups, we examined the use of five agile practices, including quality related (regular refactoring and test first), speed related (frequent release and agile planning) and communication practice (daily standup meeting). The findings show that speed related agile practices are used to a greater extent in comparison to quality practices. Daily standup meeting is least used. Software startups who adopt the Lean Startup approach do not sacrifice quality for speed more than other startups do.

Jevgenija Pantiuchina, Marco Mondini, Dron Khanna, Xiaofeng Wang and Pekka Abrahamsson

avatar for Xiaofeng Wang

Xiaofeng Wang

Senior Researcher, Free University of Bozen-Bolzano
Researching and practicing on topics related to startups, agile and lean approach, learning organisations and many more, as long as they are about motivating people intrinsically to be better.

Wednesday May 24, 2017 14:30 - 15:00 CEST
Ballroom B 1st Floor

14:30 CEST

Effects of Technical Debt Awareness: A Classroom Study

Technical Debt is a metaphor that has, in recent years, helped developers to think about and to monitor software quality. The metaphor refers to flaws in software (usually caused by shortcuts to save time) that may affect future maintenance and evolution. We conducted an empirical study in an academic environment, nine teams of graduate and undergraduate students during two offerings of a laboratory course on Extreme Programming (XP Lab). The teams had a comprehensive lecture about several alternative ways to identify and manage Technical Debt. We monitored the teams, performed interviews, did close observations and collected feedbacks. The results show that awareness of Technical Debt influences team behavior. Team members report about thinking and discussing more about software quality after becoming aware of Technical Debt in their projects.

Graziela Simone Tonin, Alfredo Goldman, Carolyn Seaman and Diogo Pina

avatar for Graziela Simone Tonin

Graziela Simone Tonin

Professor/Researcher/Student/Dreamer, UFFS
In 2005 I started working on a team that developed a RPG game. I worked through the roles of developer, analyst, project manager, IT coordinator, consultant ... since 2009 I have been working with​​Technical Debt, starting with the Samsung project In Recife/Brazil. I won a worldwide... Read More →

Wednesday May 24, 2017 14:30 - 15:00 CEST
Ballroom C 1st Floor

14:30 CEST

Key Challenges in Agile Requirements Engineering
Agile Software Development (ASD) is becoming more popular in all fields of industry. For an agile transformation, organizations need to continuously improve their established approaches to Requirements Engineering (RE) as well as their approaches to software development. This is accompanied by some challenges in terms of agile RE. The main objective of this paper is to identify the most important challenges in agile RE industry has to face today. Therefore, we conducted an iterative expert judgement process with 26 experts in the field of ASD, comprising three complementary rounds. In sum, we identified 20 challenges in three rounds. Six of these challenges are defined as key challenges. Based on the results, we provide options for dealing with those key challenges by means of agile techniques and tools. The results show that the identified challenges are often not limited to ASD, but they rather refer to software development in general. Therefore, we can conclude that organizations still struggle with agile transition and understanding agile values, in particular, in terms of stakeholder and user involvement.

Eva-Maria Schön, Dominique Winter, María José Escalona and Jörg Thomaschewski

avatar for Eva-Maria Schön

Eva-Maria Schön

Hamburg, CGI
Eva is a PhD student at the University of Seville (Spain) and also works as a Lead Consultant at CGI (Germany). She focuses on agile coaching, agile product management, and human-centered design. Her research interests are agile software development, requirements engineering, and... Read More →

Wednesday May 24, 2017 14:30 - 15:00 CEST
Ballroom D 1st Floor

16:30 CEST

Inoculating an Agile Company With User-Centred Design: An Empirical Study

In this paper, we present an empirical study on the integration of user-centred design and Agile, with the goal of achieving a development process more considerate of user needs. In particular, we introduced a curated set of lightweight, qualitative design practices in an Agile company through a series of workshops. Our results suggest that the followed approach enhanced internal communication and promoted a concrete shift towards a more user-centred perspective. However, the presence of a predominant non-Agile customer seems to have limited potential benefits.

Silvia Bordin and Antonella De Angeli

avatar for Silvia Bordin

Silvia Bordin

PhD candidate, University of Trento
During my PhD I have collaborated with small Agile companies to help them adopt user-centred design techniques.

Wednesday May 24, 2017 16:30 - 16:45 CEST
Ballroom D 1st Floor

16:30 CEST

Reflection in Agile Retrospectives
A retrospective is a standard agile meeting practice designed for agile software teams to reflect and tune their process. Despite its integral importance, we know little about what aspects are focused upon during retrospectives and how reflection occurs in this practice. We conducted Case Study research involving data collected from interviews of sixteen software practitioners from four agile teams and observations of their retrospective meetings. We found that the important aspects focused on during the retrospective meeting include obstacles, feelings, previous action points, background reasons, areas of improvement, different ideas and perspectives and generating a plan. Reflection occurs when the agile teams embody these aspects within three levels of reflection: reporting and responding, relating and reasoning, and reconstructing. Critically, we show that agile teams may not achieve all levels of reflection simply by performing retrospective meetings. One of the key contributions of our work is to present a reflection framework for agile retrospective meetings that explains and embeds three levels of reflection within the five steps of a standard agile retrospective. Agile teams can use this framework to achieve better focus and higher levels of reflection in their retrospective meetings.

Yanti Andriyani, Rashina Hoda and Robert Amor

avatar for Yanti Andriyani

Yanti Andriyani

PhD Student, University of Auckland
“Learning is a process where knowledge is presented to us, then shaped through understanding, discussion and reflection.” – Paulo Freire I am currently pursuing my Ph.D. degree at Department of Electrical and Computer Engineering, the University of Auckland. My research focuses... Read More →

Wednesday May 24, 2017 16:30 - 17:00 CEST
Belvedere 12th Floor

16:45 CEST

Discovering Software Process Deviations Using Visualizations
Modern software development is supported by a rich set of tools that accumulate data from the software process automatically. That data can be used for understanding and improving software processes without any manual data collection. In this paper we introduce two cases where data visualization of issue management system was used to investigate software projects. We studied if this kind of visualization aids stakeholders of software process to keep the process on track. The results of the study show that visualization of issue management system data can really reveal deviations between planned process and executed process. Furthermore, the visualization can be used as a common ground for discussions and aiding the project managers in their work.

Anna-Liisa Mattila, Kari Systä, Outi Sievi-Korte, Marko Leppänen and Tommi Mikkonen

avatar for Anna-Liisa Mattila

Anna-Liisa Mattila

Doctoral Student, Tampere University of Technology
Interests: Software visualization, software repository mining, software process improvement, programming languages, real-time 3D graphics, virtual reality technology, etc.

Wednesday May 24, 2017 16:45 - 17:00 CEST
Ballroom D 1st Floor
Thursday, May 25

12:00 CEST

Teaching Agile Methods to Software Engineering Professionals: 10 Years, 1000 Release Plans
Agile methods are an essential resource for software engineers, where the Agile movement evolved out of and is applied by industry, often expected as a standard practice today. Teaching Agile methods challenges students' working attitudes, where putting Agile into practice is not possible through simply applying methods prescriptively, but by having an Agile mindset. In this paper we present and discuss our experiences over the last decade of teaching an intensive Agile methods week long course as part of a professional Masters of Software Engineering degree programme at the University of Oxford. We describe the typical shape of the course, discuss how students experience Agile values and management practices to foster an Agile mindset, and provide student feedback indicating a consistently positive response to our approach to teaching Agile methods to software engineering professionals. Our reported experiences and material can help other educators who want to run similar courses and adapt where required.

Angela Martin, Craig Anslow, David Johnson and Robert Biddle

avatar for Craig Anslow

Craig Anslow

Lecturer (Assistant Professor), Victoria University of Wellington
Teach and research Agile methods at Victoria University of Wellington, New Zealand and University of Oxford, UK. Develop innovative novel software tools for Agile developers. Conduct studies on software practitioners. PhD in software engineering.
avatar for David Johnson

David Johnson

Senior Researcher, University of Oxford

Thursday May 25, 2017 12:00 - 12:30 CEST
Belvedere 12th Floor

14:30 CEST

Eeny, Meeny, Miny, Mo... A Multiple Case Study on Selecting a Technique for User-Interaction Data Collecting
Today, software teams can deploy new software versions to users at an increasing speed -- even continuously. Although this has enabled faster responding to changing customer needs than ever before, the speed of automated customer feedback gathering has not yet blossomed out at the same level. For these purposes, the automated collecting of quantitative data about how users interact with systems can provide software teams with an interesting alternative. When starting such a process, however, teams are faced immediately with difficult decision making: What kind of technique should be used for collecting user-interaction data? In this paper, we describe the reasons for choosing specific collecting techniques in three cases and refine a previously designed selection framework based on their data. The study is a part of on-going design science research and was conducted using case study methods. A few distinct criteria which practitioners valued the most arose from the results.

Sampo Suonsyrjä

avatar for Sampo Suonsyrjä

Sampo Suonsyrjä

Doctoral Student, Tampere University of Technology
Sampo is a software startup ethusiast currently working as a doctoral student at TUT. His research interests include software engineering and especially software development methods and software analytics. He received his MSc degree at TUT, Department of Information Management and... Read More →

Thursday May 25, 2017 14:30 - 15:00 CEST
Ballroom B 1st Floor

16:30 CEST

On the Usage and Benefits of Agile Methods & Practices

Within the automotive domain, agile methods and practices cannot always be applied following the pure doctrine, due to e.g. automotive standards, supplier-contractor-relationship or organizational characteristics.

Since software became a major part of the car, we were interested in identifying which agile practices (and methods) are used and adapted in an automotive domain at Bosch. Furthermore, we were interested in the reasons for using them.

Therefore, we conducted a multi-case study with nine interviews from five different Bosch projects. Results: Similar to common agile surveys, our results showed a strong focus on Scrum. However, most of the Scrum practices are adapted and deviate from the original ones due to the specific project context. Practices from other agile methods, e.g. XP or Lean Development are used as well to extend Scrum. We were further able to collect the benefits of the single practices, most often resulting in improved transparency and planning.

The results show a widespread usage, but also adaptation of agile development in the automotive domain, at least in the early project phases that were covered by the case study. The study results will be used to support automotive projects in selecting and applying agile practices according to their specific process improvement goals.

Philipp Diebold and Udo Mayer

avatar for Philipp Diebold

Philipp Diebold

Project Manager, Fraunhofer IESE
I am a researcher at the Fraunhofer Institute for Experimental Software Engineering leading the topic of agile development in the Process Engineering department. Furthermore, I am doing his PhD at the Technical University of Kaiserslautern on the topic of agile development in regulated... Read More →

Thursday May 25, 2017 16:30 - 16:45 CEST
Ballroom C 1st Floor

16:30 CEST

Enhancing Agile Team Collaboration Through the Use of Large Digital Multi-Touch Cardwalls
Agile software development has become mainstream, and with it many tools have been developed to support Agile software development. Nonetheless, studies show, that most Agile software teams still also use physical cardboards for their daily work. This is error prone and causes a lot of extra effort to keep both in sync. In our research project we analyzed what the reason for this media break is, and developed concepts and the software prototype, aWall, which provides agile teams a digital collaborative workspace based on large multi-touch walls, and avoids the media break. To evaluate the usability and effectiveness of the aWall in the daily work, we conducted a user study with 11 software practitioners. Our findings indicate that the practitioners valued aWall as it enabled and encouraged team work due to the large size of the wall, accessibility and visibility of the needed information, the possibility of customization of the interface, and the integration with existing issue tracking tools. Based on this work, we suggest that augmenting digital cardwalls with large interactive touch technology and integration with task tracking systems is a useful way to support effective collaborative Agile software development processes.

Martin Kropp, Craig Anslow and Magdalena Mateescu

avatar for Martin Kroop

Martin Kroop

Professor for Software Engineering, University of Applied Sciences Northwestern Switzerland
Martin is professor for Software Engineering at the Institute of Mobile and Distributed Systems at the University of Applied Sciences and Arts Northwestern Switzerland. His main interest is in everything that makes software development more efficient, including build automation, testing... Read More →

Thursday May 25, 2017 16:30 - 17:00 CEST
Ballroom B 1st Floor

16:30 CEST

Knowledge Sharing in a Large Agile Organisation: A Survey Study
Knowledge is a core resource for agile organisations that is transformed into products and services during the development process. Although sharing of knowledge is essential across any organisation, it has been claimed that the software industry requires more knowledge management than any other sector. However, agile methodologies concentrate on team level collaboration, making it challenging to share learning beyond teams. This paper presents the results of a survey with 81 responses on organisational knowledge sharing in a multinational agile company. The survey focusses on three aspects of knowledge sharing: within agile teams, beyond the team with company colleagues, and with customers. It concentrates on knowledge sharing practices, ease of knowledge sharing and motivation for knowledge sharing. Summary statistics, regression, and test of equity are used as analysis techniques. Results show that knowledge sharing with team members is significantly easier than with customers or company colleagues beyond the team. In addition, using agile practices improves ease of knowledge sharing within teams but not with customers or colleagues. We conclude that to improve knowledge sharing the organisation needs to establish knowledge sharing practices beyond the team, enhance employees motivation to share, and develop a knowledge sharing culture.

Kati Kuusinen, Peggy Gregory, Helen Sharp, Leonor Barroca, Katie Taylor and Laurence Wood


Thursday May 25, 2017 16:30 - 17:00 CEST
Belvedere 12th Floor

16:45 CEST

Checklists to Support Test Charter Design in Exploratory Testing
During exploratory testing sessions the tester simultaneously learns, designs and executes tests. The activity is iterative and utilizes the skills of the tester and provides flexibility and creativity. Exploratory testing is also an iterative activity. As it aligns well with the agile philosophy of iterative development and learning it is considered an agile testing practice. Test charters are used as a vehicle to support the testers during the testing. The aim of this study is to support practitioners in the design of test charters through checklists. We aimed to identify factors allowing practitioners to critically reflect on their designs and contents of test charters to support practitioners in making informed decisions of what to include in test charters. The factors and contents have been elicited through interviews and a questionnaire. Overall, 30 factors and 35 content elements have been elicited. The most influential factors were client requirements, the test strategy and the knowledge of previous bugs. The most frequently mentioned contents were a description of the test environment, the test focus (part of the system to be tested), and the test level. The paper also discusses how practitioners may make use of the checklists.

Ahmad Nauman Ghazi, Ratna Pranathi Garigapati and Kai Petersen

Thursday May 25, 2017 16:45 - 17:00 CEST
Ballroom C 1st Floor