Call for Experience reports
Experience Reports provide the opportunity for you to share your practical experience through a paper and accompanying talk at the conference. An experience report is a reflection of your own industry experiences (e.g. challenges you have seen, what you tried and approaches you have taken, what worked and what didn’t work). We invite you to submit an abstract in which you briefly explain your own, unpublished experience related to Global Software Engineering. If your proposal is accepted, you will then be shepherded as you write your report. Experience reports are short papers (maximum 5 pages) that will be published in the conference proceedings.
These questions might help you decide how to focus your experience report:
- How did you uniquely adopt, adapt, use global software engineering?
- How have you uniquely tackled architecture, development, design, usability, quality assurance, deployment, marketing, product definition, requirements or documentation in GSE settings?
- 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?
We know it’s not easy to get an idea 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 with our writing. ‘Shepherding’ is a process where more experienced authors guide and coach you as you write 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.
If you are looking for ideas to focus your experience report check a list of topics of particular interest to the conference at the ICGSE 2018 Main Page.
Proposals should be submitted through the conference submission site (see the banner). You do not need to upload a full paper as part of your initial submission but you are encouraged to write an extensive abstract (max 1 page) sharing highlights of your experience and what you intend to focus on in your paper.
Your experience report will be published in the ICGSE proceedings. The papers should be formatted according to ACM formatting guidelines, see ICSE2018 formatting instructions: https://www.icse2018.org/track/icse-2018-Double-blind-review#Formatting. (Note that at ICGSE we do not use double-blind review.) Even though the format is ACM, the proceedings will be produced by IEEE and the papers will appear in the digital libraries of both ACM and IEEE.
- January 15, 2018 - Final Deadline for all submissions (=abstracts)
- January 22, 2018 - Conditional acceptance notification. Shepherding process begins.
- March 5, 2018 - 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.
- March 19, 2018 - Deadline for final copy of paper
Jutta Eckstein, Independent, Germany
Kelly Blincoe, University of Auckland, New Zealand
If you have any questions or comments, please contact the Experience Report program chairs, email: ICGSE_ExperienceReports@itu.dk