XP 2025
Mon 2 - Thu 5 June 2025 Brugg - Windisch, Switzerland
Dates
Tue 3 Jun 2025
Wed 4 Jun 2025
Tracks
XP Agile Training and Education
XP Catering
XP Experience Reports
XP Industry and Practice
XP Open Space
XP Research Papers
Plenary
Hide plenary sessions

This program is tentative and subject to change.

You're viewing the program in a time zone which is different from your device's time zone change time zone

Tue 3 Jun

Displayed time zone: Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna change

11:00 - 12:30
11:00
30m
Talk
Breaking Down the Wall Between Dev and Ops at George
Experience Reports
Julian Beyer julian.beyer@erstegroup.com, Carmen Gruber REWE Group, formerly Erste Bank Group AG, Balint Puster Erste Bank Group AG

Wed 4 Jun

Displayed time zone: Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna change

11:00 - 12:30
12:00
30m
Talk
Evolving Agile from the Inside at Nextdoor
Experience Reports
14:00 - 15:30
14:00
30m
Talk
Collaboration, Team driven Adaptation and Happiness: Single Team FAST in a Scrum Cadence under SAFe
Experience Reports
Per Beining XPand ApS

Unscheduled Events

Not scheduled
Talk
The Fail Forward Conference: Share, Grow, Unite
Experience Reports
Rucha Ramchandra Kapare Springer Nature, Osman Maqsood Springer Nature
Not scheduled
Talk
Unlocking Team Productivity through Automated Metrics for Agile Teams
Experience Reports
semen arslan , Ravi Kiran Veeraganta Agile Coach, Adrian Novac Sr. Product Manager
Not scheduled
Talk
Does it really always need to be more fancy and creative? - How to get out of retrospective theater.
Experience Reports
Jonathan Frankenberger BettercallPaul GmbH, Debbie Walter Carl Zeiss Microscopy Limited

Call for submission


The Experience Reports Track provides the opportunity for you to share observations, hard-fought wisdom, and practical advice through a paper and accompanying talk at the conference.


Topics of Interest

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

  • Delivering Value and Creating New Business
  • Continuous Integration / Continuous Delivery
  • Modeling and understanding customer value
  • The Lean start-up, including experimentation and MVP
  • Large-Scale Agile
  • Adopting and adapting Agile and Lean in large projects and organizations
  • Global software development and offshoring
  • Agile Transformations
  • Agile practices and their evolution
  • 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
  • How your Agile practices have evolved
  • Human, Organizational, and Managerial Aspects
  • Social aspects of teams and groups
  • Forming Agile organizations
  • Agile coaching and mentoring
  • Management and governance
  • Measurement and metrics for projects, programs, processes, and teams
  • Increasing social, environmental, and economic sustainability

Submissions

An experience report is a first-hand description of challenges faced, approaches taken, observations, and insights. Unlike a case study, an experience report is personal. We encourage authors to introduce themselves to their readers and to reflect on their experience.

We invite potential experience reporters to submit a proposal that describes in more detail an original, unpublished experience related to agile and lean software development and what you intend to focus on in your written report. The experience reports will be oriented toward industry practitioners and welcoming to interested academics.

If your proposal is accepted, you will then be shepherded as you write your report. Authors of accepted proposals are further expected to prepare and deliver a presentation at the conference. Oh’… and by the way, authors are granted a discount on the conference fee.

Proposals are submitted electronically via the EasyChair submission system:

Submission closed

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 proposal sharing highlights of your experience 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.


Shepherding

We know it’s not easy to get ideas onto 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 agrees that your report is acceptable, you will submit your final version to the track co-chairs, who will check that it is ready for publication and conforms to our publishing style guidelines.


Formatting

Experience reports are short papers (typically 6 to maximum 8 pages) that will be published on the conference website in ACM full-page format Please use the experience report template and refer to the formatting guidelines. Authors retain the copyright to their work and sign a permission form granting XP 2025 the right to publish their report online.


Review Criteria

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?

Helpful resources


Questions?

Contact our track chairs

:
: