If you choose to submit a proposal to this track, please! please! refer to our FAQs for important additional information about the expectations for this track, the kinds of information the reviewers need to see in your proposal and where to place it.
We invite you to submit an Experience Report about what happened when you applied agile principles and practices in the real world. Your stories help us understand where agile works and what can go wrong. We are interested in both stories told by experienced agilists, recounting the most interesting chapter of their agile journey, as well from reporters who are newer to agile practices, sharing their fresh insights.
The Experience Report track requires that you write a six-to-eight page paper in addition to presenting the report. Folks whose proposals are accepted write their papers under the guidance of an Experience Report “shepherd.” You do not need to start the paper unless your proposal is accepted.
A good experience report tells a story. It explains what happened, why it happened, who it happened to, and why we should care. What makes an experience report unique and compelling is that it is also a personal story. One powerful way that people learn is by relating to the dilemmas, thought processes and successes and failures of others. Experience report authors come from different countries, business, and work contexts. By reading about diverse experiences, agile teams and individuals can come to realize the similar challenges they share and be inspired by how others continue to find ways to improve their work environment and practices. Written copies of experience reports from previous conferences can be found at https://www.agilealliance.org/resources/experience-reports/
Experience reports topics may include, but are not limited to, the stories of how:
• Agile approaches transformed your business.
• You uniquely adopted, adapted, evolved, blended or scaled agile practices.
• You tackled technical domains such as DevOps, testing, architecture, development, and design.
• You approached business and produced domains such as usability, quality assurance, requirements or documentation, deployment, marketing, product definition or management.
• Your application of other disciplines that align with agile principles and practices.
• You introduced agile practices to your organization and manage the transition to an agile culture.
• Your values or ways of working changed over time. What are you doing now and why?
• Your personal journey in IT and business has been influenced by agile principles and practices.
Other ways that you can approach your Experience Report is by asking and answering questions such as:
• What were 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 need to know about?
The Experience Report Team is always glad to provide guidance to those who submit proposals to the track. Please do not hesitate to move your proposal from the Draft State to the Feedback Requested State to find out whether your have provided enough information for the team to evaluate your proposal. We look forward to your proposals!!
Written experience reports with additional details can be found at https://www.agilealliance.org/resources/experience-reports/ . But there’s nothing like hearing stories in person, as a starting point.