Case Study Guidelines
Your application to become a Scrum@Scale Trainer must include a case study documenting your own recent (within the last 2 years) experience scaling Scrum and what you learned from it. Since you’ll have a maximum of 10 minutes to tell your story, your case study should be as focused and concise as possible. We recommend that you focus on:
- A unique challenge you faced while scaling Scrum and how you addressed it;
- A specific pattern/anti-pattern you witnessed, or technique you applied, and the observable impact; or
- How you leveraged a particular component of the Scrum@Scale framework in order to achieve some outcome or result.
You may submit your case study to firstname.lastname@example.org. Once submitted, our team will review your case study and respond with feedback for iteration, or if we decide it’s ready, we’ll invite you to register for an upcoming Train the Trainer course.
During the 5-day Scrum@Scale Train the Trainer course, participants will have a maximum of 10 minutes (6-7 minutes for presentation + 3-4 minutes for Q&A) to present their case studies to the rest of the group. These presentations will be professionally recorded and become part of our growing Case Study Library under the CC4-BY-SA license. As such, please ensure that all content in your case study be content that you are authorized to share, or that it is anonymized appropriately.
What Makes a Great Case Study?
- Begin with the structure and starting state of the organization.
- Focus on what was done (related to Scrum@Scale).
- End with results: provide data & concrete metrics that illustrate the business impact of what was done.
- Fewer words, more images.
- 3-5 slides using this ppt. template.
- 5-10 minute recording of you presenting your case study. Note: the recording can be video (preferable) or audio, and production quality is not important.
- Optionally, you may also submit a written version of the case study in order to provide additional context.
- Avoid vague “hero stories.”
- Focus on concrete learnings and key takeaways.