Call for sessions

Create your session using our online tool. You can submit any (draft) idea and improve it later using the ‘perfection game’ with the community’s help. See the guidelines on how to submit a session.

What are you looking for?

What would make it a WOW session for you and our participants?

We’re interested in:

  • Hardcore tech sessions: It’s called Extreme Programming (XP)days for a reason. So we welcome hands-on sessions on new programming languages like Rust, Julia or Elixir and tips and tricks on tried and tested languages like C++, Java or PHP.
  • Cases from organisations: You introduced Agile in your organisation. How did you do that? What happened? What made it a succes? Which challenges did you face?
  • Experiences with new and old techniques like backlog refinement, Mob Programming or NoEstimates. What worked, what didn’t? Why? What have you learned?
  • Unexpected ideas from other disciplines and sciences like HR or Healthcare. How can we cross borders? What lessons have we missed? How can we collaborate better with other disciplines?
  • Ask for help from other participants. Any challenges, technical or social, affecting you at work that you would like to get some advice on. At XPDays there are plenty of people struggling with the same issues willing to help.
  • Pushing the limits of techniques and organisations, doing the impossible. What did you try to challenge commonly accepted assumptions?
  • Back to basics. What happens for example if we really take Extreme Programming values of Simplicity, Commmunication, Feedback, Courage and Respect seriously? Or if we do Scrum the way it was meant to be.
  • Taking back agile. What does agile really mean to you and why is it important?
  • Questioning agile. Where, when and why would you not use agile methods? Why? What can we learn about context and applicability?
  • What is next? Is agile nearing its end, do we need to look beyond? What do we see at the horizon?

The XP Days community loves highly interactive sessions where everyone participates and learns from each other. And sometimes, we love sinking into a chair and listening to someone telling a captivating story.

Selection process

We intend to create an attractive program with high-quality sessions. During review and selection, your session will get bonus points when:

  • You use no slidedeck. Think outside the box and sharpen your story telling skills.
  • It appeals to both technical and functional people. Involve the geeks, challenge the managers.
  • It has the XP Factor. Is it entertaining and crazy? Does it take people out of their comfort zone?
  • You’ve done a session dry run. Did we join one of our try-outs? Did you send a video introduction?
  • Your subject is fresh and original. Maybe something outside the domain of IT?
  • It has an original format. Doing something with fruit? Are there any sports involved? Great!
  • Your session poses a question instead of giving an answer.
  • If you’re new to presenting at XP Days. First timers receive a warm welcome! PS, if you need help as a first timer, reach out to us, we’ll help you extra!
  • You’ve participated in the perfection game for at least 3 other sessions

Session review criteria

Keep in mind the following review criteria, and remember that the best way to get to a high-quality session is by trying it out and improving based on the honest feedback.

  • Who will be interested in this topic? Would you go to this session?
  • Is the description clear and inviting? Will it attract its intended audience?
  • What value will this session bring to participants and organizers?
  • Why is this subject relevant to agile & beyond?
  • How does this session fit the conference?
  • What’s innovative and unusual about the session? topic, format, …
  • Does the session also address why things (don’t) work, and not just ‘what’ and ‘how’?
  • Is the session structured in such a way that its objectives can be reached?
  • Is the timetable realistic?
  • How does the session format facilitate learning?
  • What are the expected results and outputs? Can these be communicated to people who were not at the session

We strive to make the process open and transparent by involving the community. There’s, however, no such thing as a completely objective selection process. As a program committee, we will also apply some other criteria:

  • Diversity of presenters; balance between experienced and new presenters; presenters from different countries; presenters of different gender
  • Diversity of session formats
  • Diversity of topics: hands-on technical stuff, process related, management, coaching…
  • Diversity of prerequisite knowledge or experience needed from the participants
  • Balance between real world experiences, tools & techniques, innovative ideas
  • A maximum of 2 sessions per presenter and no more than 1 session per presenter per day
  • The involvement of the presenter in the perfection game (to review sessions of other presenters)

Session voting

About two months before the session selection for the conference programme, presenters get the opportunity to vote for sessions to take part in the programme.

Rules of the game:

  • You can cast one vote per session
  • You can cast 10 votes (or less)
  • You can vote for your own session(s)
  • The order of the votes is not important
  • Your votes will not be visible to the other submitters, only to the program committee

Follow us on linkedin to keep track of our program dates!

Selected sessions

The presenters of the sessions selected for the program will receive one free ticket to the conference. If you have already bought a ticket, it will be refunded.

If you are not selected

Presenters whose session(s) have not been selected will be able to buy an entrance ticket at Early Bird rate if they meet the following criteria:

  • They filled out a complete proposal
  • They processed other peoples review comments
  • They reviewed at least 3 other sessions

Perfection Game

The Perfection Game is a way to give constructive feedback whenever you want to improve something. Jim & Michele McCarthy developed it as part of the Core Protocols.

The Perfection Game works as follows:

  • Someone presents their work (e.g. a session proposal) and asks for feedback
  • You rate the work on a scale of 1 to 10, based on how much value you can add:
    I will for example give a 9 out of 10 if I see little value that can be added, a 5 out of 10 if I can double the value of the work, and 1 out of 10 if I can make the work worth 10 times more valuable.
  • Explain what you liked about it: what justifies the score? What should be kept?
  • Explain what you would do to make the work perfect: What concrete actions should be taken to make it a 10 out of 10?

When you give feedback:

  • Think deeply when you explain how to make a work perfect. It’s tempting to make negative remarks, yet make them constructive
  • Explain your reasoning – e.g. “I would do X because of Y”
  • Don’t skimp on the “What I liked section”; the good parts should be kept and reinforced
  • Make sure that your score reflects the contribution you think you can make
  • Follow up and give updated feedback when the session proposal has been changed. Iteration leads to perfection.

When you receive feedback:

  • Thank the person giving the feedback
  • Don’t argue with the person giving feedback, but ask questions to clarify the input
  • You are responsible for the quality of the work, you decide if you apply the feedback you received