May 22-26, 2017
Cologne, Pullman Hotel

Call for Contributions

XP2017 will bring together people of all roles dealing with the creation of software. By carefully balancing technical and methodological topics, the conference will provide a space where people "doing it" and people "helping others do it", but also people "needing it" can share their experiences with Agile Software Development in order to uncover better ways of developing software.

For the XP2017 program this means that we are not only looking for what is tried and true, but also for sessions about new and thought-provoking ideas. With the conference attracting delegates from many countries, with varying levels of experience, and from many different occupations, we have the unique chance to collectively advance our craft.

Now it’s your choice to be part of it … by contributing to the longest running agile conference in the world!

Please consider the tickets page and the FAQ for information on compensation for industry & practice speakers and academic discounts.


Please click on the headlines for further details.

Call for Research Papers

We invite original, unpublished high-quality research papers (full papers as well as short papers) related to agile and lean software development and organization. Submissions will be reviewed by at least three members of the international program committee, but we reserve the right to desk reject submissions after a first screening on rigor and relevance.

Topics of interest

The topics of interest to the conference include, but are not restricted to, the following:

  • Agile approaches to requirements gathering, testing, release management and deployment
  • Tools and techniques for agile development
  • Qualitative/quantitative improvement techniques for agile processes and products
  • Empirical studies and evaluations
  • Agile sustainability, evolution and revolution
  • Adopting and adapting agile and lean in large projects and organizations
  • Agile practices in global software development and off-shoring
  • Foundations and conceptual studies of and for agile methods
  • Measurement and metrics for agile projects, agile processes, agile software, agile teams
  • Teaching and using agile methods in education and research

Important Dates

  • January 07, 2017 - Submission deadline
  • February 17, 2017 - Notification of acceptance
  • March 04, 2017 - Camera ready deadline


The XP 2017 conference proceedings will be published by Springer in the Lecture Notes in Business Information Processing (LNBIP). The paper length of at most 15 pages (full papers) and 7 pages (short papers) will be strictly enforced. Papers need to be submitted in the LNBIP format through EasyChair.

Prof. Dr. Hubert Baumeister, Technical University of Denmark (DNK)
Prof. Dr. Horst Lichter, RWTH Aachen University (DEU)
Prof. Dr. Matthias Riebisch, Universität Hamburg (DEU)

Call for Scientific Workshops

We are calling for scientific workshop proposals on all Agile topics, with a special glimpse on innovative fields. Workshops may last half-day or full-day and are expected to pay attention to novelties and potential advances of interest for the Agile community.

Workshops involve small groups of participants to discuss or present results on current topics in Agile software engineering research and practice and to exchange ideas, experiences, hints related to all Agile fields. They can either be presentation-oriented (i.e. concentrating on the presentation of accepted papers) or discussion-oriented (i.e. emphasizing discussions).

Proposals must be 1500-2000 words in length and should include:

  • full contact information for all organisers of the workshop and main contact person
  • desired length of the workshop (i.e., half or full day)
  • desired minimum and maximum number of workshop participants
  • outline of the themes and goals of the workshop (up to 500 words)
  • participant selection process, including whether the workshop will be open or closed
  • structure of the workshop and plans for generating and stimulating discussion
  • any equipment, room capacity, or other logistic constraints
  • 250 word call for participation for the workshop (to go on the XP2017 website)
For workshop paper submission visit the detail page.

Important Dates

  • November 11, 2016 - Workshop submission deadline
  • November 21, 2016 - Workshop decision made
  • December 19, 2016 - Workshop papers call ready
  • March, 2017 - Workshop papers deadline (check detail page)
  • April 28, 2017 - Workshop program ready

Chair: Prof. Roberto Tonelli, University of Cagliari (ITA)

Agile software development is a mainstream approach in software engineering. Therefore, software engineering research is and should be involved in understanding and improving agile practices. We can now look back at an impressive amount of work on agile software development, empirical and methodological. Yet, there are still many open questions out there and agile software development has not stood still. Newer practices and approaches need to investigated scientifically. Yet, choosing the right research methods and strategies can be a difficult endeavour.

This doctoral symposium should be a help to PhD students who already or plan to conduct research in the wider area of agile software development. Experienced researchers from the board of advisors will review the research plans from PhD students and give them detailed feedback and guidance. The most promising research plans will be invited to be presented at the symposium where the students can get more direct feedback in the discussion. Furthermore, we will have an interactive session at the doctoral symposium with all present PhD students and advisors to work on their abilities to develop research plans.

Participation in the symposium is being solicited at three levels:

Participants are doctoral students, preferably at a mid-point in their dissertation work (i.e. are at least 12 months from defending their dissertation, but have at least a preliminary research design), who will present their work at the symposium and receive feedback from a dedicated mentor from the board of advisors, the other symposium advisors and other attendees.

Those wishing to be participants are asked to submit a paper (up to 6 pages following the LNBIP template) on their research plan including:

  • Title and abstract
  • Introduction (motivation, rationale, background) to the research
  • Description of issues or points on which the author would like to get the most advice on
  • Relevant prior work (foundations, relevant research results, research gap this work tries to fill)
  • Research objectives, questions and hypotheses (with rationale)
  • Research approach, study design and arrangements
  • Data analysis methods and techniques
  • Validity threats and their control
  • Summary of the current status of the research and planned next steps

Participants in the symposium are required to:

  • submit and present a research plan,
  • review and comment on up to two other research plans, and
  • act as a scribe in one review session.

All papers must be submitted through the submission system in PDF format. Papers are limited to 6 pages, must be written in English and be formatted according to the LNBIP templates. Papers not following the formatting guidelines will be rejected without review.

Apprentices are also doctoral students, but at an earlier stage in their studies. Apprentices will attend the symposium and are encouraged to ask questions of the presenters, and will benefit from the feedback given to other students.

Observers are any other members of the agile software engineering research community who would like to attend the symposium. NOTE: Any observer or symposium advisor who is serving as a dissertation advisor to one of the participants is "kindly requested" to not speaking during the presentation and discussion of their student's work.

Important Dates

  • January 23, 2017 - Deadline for research plan submission
  • February 15, 2017 - Notification of acceptance
  • February 28, 2017 - Camera ready copy due
  • May 22, 2017 - Symposium
  • May 26, 2017 - Session notes sent to participants

Board of Advisors

Stefan Wagner, University of Stuttgart (chair)
Daniel Méndéz Fernandéz, TU Munich
Darja Smite, Blekinge Institute of Technology
Laurie Williams, NC State
Davide Taibi, Free University of Bolzano/Bozen

Call for Posters (2nd Phase)

You didn’t submit your poster in the first phase? This second call is for you.

We invite poster submissions to XP 2017, the 18th International Conference on Agile Software Development. We mainly encourage poster proposals on new research ideas, research that is in an early state, or industrial experiences. The main goal of the poster session is to trigger discussions and collaborations with the participants of XP 2017, to get feedback, to disseminate, or validate work in different states.

In XP2017, all accepted posters will be exhibited during the whole conference and presented during the conference poster session. Accepted posters and the related abstracts will be published on the conference web pages. Authors of the accepted posters will also have the opportunity to give a lightning talk on the topic of their poster. Details of the lightning talks will be posted later on.

Important Dates

  • February 18, 2017 - Submission deadline (1st phase)
  • February 25, 2017 - Notification of acceptance (1st phase)
  • March 4, 2017 - Camera Ready deadline
  • April 22, 2017 - Submission deadline (2nd phase)
  • April 29, 2017 - Notification of acceptance (2nd phase)
  • May 5, 2017 - Author registration deadline (2nd phase)


The submission must contain an extended abstract (up to 4 pages LNBIP) describing the contents of the poster AND a draft of the poster. The draft should give a general idea of the poster’s structure and contents, but does not need to contain finalised graphics or text. The draft poster must be in the PDF format. If the poster is related to a presentation or demonstration given in XP2017 or a co-located event, please state this in the abstract.

The maximum size of the posters is a vertical A1. Each accepted poster has one side of a poster stand reserved for it. Smaller posters can be presented if necessary, but we recommend the size minimum of a vertical A2.

Posters need to be submitted in the LNBIP format by email.
All submissions will be reviewed by the posters committee.

Posters Committee

Ademar Aguiar, University of Porto, Portugal (chair)
Hubert Baumeister, Technical University of Denmark
Stefan Wagner, University of Stuttgart, Germany
Rebecca Wirfs-Brock, Wirfs-Brock Associates, USA


For further information please send an email to


Authors of accepted posters will benefit from the 40% academic discount.

Industry & Practice

Please click on the headlines for further details.

The submission deadline for Industry & Practice proposals was January 22, 2017.

Proposals are welcome that build on our theme of "Uncovering better ways of developing software". Both technical and non-technical sessions are welcome. The sessions should be oriented toward industry practitioners and welcoming to interested academics.

Proposals can be either of the following types:

  • Tutorial Sessions present fairly established material on topics of interest to agile practitioners and may involve presentation of material, discussions and group activities.
  • Workshop Sessions provide a valuable hands-on learning experience, achieved primarily through activities attendees perform. Workshops may have more of a peer-to-peer nature, and may be about exploring a topic further (rather than be based on knowledge transfer by the presenter to the attendees).

Proposals will be evaluated based on these criteria

  • Should present concepts or practices that are grounded in experience
  • Actively involves participants in their own learning
  • Describe (for reviewers) how you will use the time period to meet the objectives you’ve stated for your session
  • Give a clear description of what new learning or abilities attendees will take away

Additional audiences may be identified by roles (e.g., manager, coach, developer, tester, etc.) or interests (e.g., team development, test automation, programming practices, enterprise adoption, etc.). The audience you target and how you organize your industrial session is completely up to you, but should be made clear.

Chair: Nancy Van Schooender­woert, Lean-Agile Partners, Inc.

Building on our theme of "Uncovering Better Ways of Developing Software", we seek proposals for session topics that explore the ways individuals and teams interact effectively, in person and remotely, within the team and with external parties.

Proposal topics could include: peer-to-peer collaboration practices, coaching practices, management practices, meeting practices, effective communication practices like feedback or conflict, games to promote team work and healthy interaction, and other similar areas. In this track, we also expect to see topics that examine the role of helpful work processes and choosing minimal, yet sufficient, use of tools.

The sessions will be oriented toward industry practitioners and welcoming to interested academics.

Proposals will be evaluated based on these criteria:

  • Presents concepts or practices grounded in the proposers’ experiences
  • Clearly states the audience it will address
  • Actively involves participants in their own learning
  • Learner focused outcomes and process
  • Fresh approach to or interpretation of topic
  • Clear content and process that fits well within the sixty or ninety minute time box the proposer chooses

Across the track sessions, we will attempt to strike a balance between introducing new ideas for experienced practitioners and solid foundational topics for those newer to Agile. Please feel free to propose topics that are new as well as those that are more familiar to the reviewers.

Chair: Diana Larsen, FutureWorks Consulting, LLC.

For the "Working software" track we are looking for sessions that can educate attendees about how to create software that is valuable, verifiable, adaptable.

  • Valuable. Continuously build confidence that the software enables end-users to meet valuable goals, for example using specification, design and modelling techniques that involve customers, developers and testers
  • Verifiable. Build software with an architecture that makes it easy to write quick, automated tests
  • Adaptable. Build software that can be quickly adapted and delivered to accommodate for new requirements

This is the most technical track of the conference, and we are primarily interested in sessions that describe technical practices. While we still believe TDD and Continuous Integration are crucial practices for working software, we’re looking for novel techniques that have been tried, but might still be unfamiliar to a larger audience.

Proposals will be evaluated based on the following criteria:

  • Presents techniques that the proposer has experienced on a real project
  • Documents measurable effects (for example reduced defect counts or improved productivity)
  • Actively involves participants in learning the technique(s)
  • Novelty

Chair: Aslak Hellesøy, Cucumber Ltd.

Since their inception, agile and lean approaches have emphasised the need to focus on customer value, and take a customer perspective in the work that we do.

The Customer Collaboration track is interested in the following questions:

  • How do we collaborate with customers on any combination of innovation, quality, prioritization, architecture, continuous delivery, DevOps, and more?
  • How do we create contracts that promote collaboration and agility?
  • How do we cater for our customers’ customers?
  • What is different when our customers are internal to the same company as us?
  • Rather than just a generic role of "customer", what are the different roles we collaborate with? What does each role need?
  • How do we balance the needs of multiple, perhaps even competing, customers?
  • How do we assess customer satisfaction, and how do we collaborate to achieve win-win scenarios?
  • What metrics are useful to support customer collaboration?

Take these as examples. Feel free to propose sessions that address other questions that you think our participants would benefit from.

For the Customer Collaboration track we are looking for sessions that showcase examples of effective collaboration between customers and teams. Proposals will be evaluated based on the following criteria:

  • Reflects real experience on the part of the session proposer
  • Presents established techniques that can help participants establish a strong foundation
  • Presents new or novel ideas that might not yet be proven, but offer potential for new ideas that participants can try
  • Sessions that can demonstrate collaboration through invlolving participants
  • The session proposal should clearly artiuclate the level of audience that is being addressed, from beginner to advanced
  • Bring a customer: special attention will be given to session proposals that include co-presenting with customers, where together you can highlight examples, challenges and lessons learned

Chair: Ken Power, Cisco Systems Inc.

Changes can be small or huge, even disruptive. They may have a small or a big impact on our team structure, existing processes, established business models or current organizational structures. In all situations where software is explicitly or implicitly involved we need to be prepared for change.

  • We need to be able to respond quickly to changed requirements.
  • In the moment of changing code we become aware of unwanted side effects.
  • It is desirable to have highly valuable features available as fast as possible.
  • A well-designed code base enables us to have a high responsiveness and adaptability to change.
  • We are not hindered by long-lasting processes with high overhead costs.

In this situation it is key that all our decisions, processes and actions fully acknowledge that change is inevitable and likely imminent.

Share your experience and thoughts on

  • what methods have been proven "successful"
  • which disruptive ideas could enhance software development in a world of short product lifecycles and changing business models
  • what approaches may help in proactively prepare for change instead of simply responding to it
  • and in what situations you became aware of sth. “missing”.

We appreciate proposals that establish best-practices in our community but even more aim for concepts that motivate indeep discussions and new insights uncovering new methodologies for handling change.

Chair: Dr. Jan Coupette, codecentric AG

Experience Reports

The Experience Report Track provides the opportunity for you to share observations, hard fought wisdom, and practical advice through a paper and accompanying talk at the conference. An experience report is a firsthand description of challenges faced, approaches taken, observations and reflections. We invite you to submit an abstract and a proposal (up to 2 pages) that describes in more detail your original, unpublished experience related to agile and lean software development and what you intend to focus on in your paper. If your proposal is accepted, you will then be shepherded as you write your report. Experience reports are short papers (maximum 8 pages) that will be published on the conference website in ACM full-page format (authors will be provided a file template). Authors retain the copyright to their work.

The submission deadline for Experience Reports was January 22, 2017.

Questions to consider

These questions might help you decide how to focus your experience report:

  • How did you uniquely adopt, adapt, evolve, blend or scale agile practices?
  • How have you uniquely tackled architecture, development, design, usability, quality assurance, deployment, marketing, product definition, requirements or documentation?
  • How did you introduce agile practices to your organization and manage the transition to an agile culture?
  • What were the challenges you faced? How successful were you in overcoming them? What challenges remain?
  • What mistakes did you make? What insights have you gained that others could learn from?
  • If you’ve been doing agile development for a long time, how have your values or ways of working changed? What are you doing now and why?

Shepherding of experience reports

We know it’s not easy to get an idea on to paper. Whether you’re a first-time author or you already have some publications under your belt, we can all benefit from some guidance and help. ‘Shepherding’ is a process where more experienced authors guide and coach you through writing your experience report paper. If your proposal is accepted you will be assigned a shepherd to work with you to help you shape your paper and get it ready for publication.

Shepherds work closely with authors, reviewing drafts and freely giving advice. Shepherds ask clarifying questions and suggest improvements. But ultimately, it is you, the author, who decides what to tell and how to tell it. A shepherd is not an editor, although they may generously make detailed comments on how to revise your paper. Once the shepherd and the program committee agree that your report is acceptable, you will have time to make final revisions before the paper is published.

Review, feedback, acceptance

Those who submit early (before the December 11 deadline) and who provide us with timely answers to our questions are likely to receive the greatest level of assistance and increase their chance for getting accepted. While we would like to comment on every submission and offer advice so that potential authors can improve their proposals, time is short. Those who submit proposals well before the deadline are more likely to receive feedback than those who wait until the last minute.

Areas of interest

Consider these areas if you are looking for ideas to focus your experience report. Topics of particular interest to the conference include, but are not limited to the following:

  • Delivering Value and Creating New Business
    • Continuous Integration
    • Continuous Delivery
    • Modeling and understanding customer value
    • Experimentation
    • The lean startup
  • Large-Scale Agile
    • Adopting and adapting agile and lean in large projects and organizations
    • Global software development and off-shoring
    • Agile evolution and revolution
  • Agile foundations
    • Novel practices and techniques related to requirements, testing, architecture, development, deployment, UX design, marketing, product definition
    • Experiments in software development and their relation to agile methods
    • Tools for agile development
  • Human, Organizational and Managerial Aspects
    • Social and human aspects including teams
    • Forming agile organizations and its implications
    • Agile coaching
    • Management and governance aspects
    • Measurement and metrics for agile projects, programs, processes, software, teams
    • Organizational culture
    • Agile contracting
  • How to submit your proposal

    Proposals should be submitted through the conference submission site. You do not need to upload a full paper as part of your initial submission but you are encouraged to write an extensive abstract and submit a detailed two page proposal sharing highlights of your experience and what you intend to focus on.

    Important Dates

    • December 11, 2016 - Deadline for Early Submissions
      In addition to entering information about your proposal in the submission system, you should also upload a file that contains more details about your proposal. The proposal file should be at most two pages and should outline what your experience is and what you intend to focus on. We encourage you to give us enough information so we can make an informed decision and ask you clarifying questions. There will be an opportunity for chairs to ask questions and for submitters to revise their proposals before selections are made.
    • January 22, 2016 - Final Deadline for all submissions
    • January 31, 2017 - Conditional acceptance notification. Shepherding process begins.
    • March 15, 2017 - Go/no-go decision based on whether paper is progressing.
      We will make a call whether to continue based on the quality of the paper at this date, and the shepherd’s judgment of the paper’s progress. Writing continues. Get paper ready for publication.
    • April 21, 2017 - Deadline for final copy of paper

    Program Committee Chairs

    Rebecca Wirfs-Brock, Wirfs-Brock Associates, US
    Avraham Poupko, Cisco, IL

    If you have any questions or comments, please contact the Experience Report program chairs.

    40% compensation of the conference fee for 1 speaker.

Copyright © 2016-2017 · All Rights Reserved · codecentric AG