Finalize ETOR retro board

[dylansmith-Nava]

User story

As a teammate on ReportStream, I want to finalize and lead the ETOR retro, so that we can promote continual learning from our initiatives and understand where we can improve future partnerships. **Note, this retro is ReportStream INTERNAL ONLY. No non-ReportStream contacts are invited to this retro.

Background

As we have engaged on the ETOR initiative with outside partnerships for over a year, ReportStream stakeholders considered it wise to run an INTERNAL retrospective to understand our collective thoughts on our partnerships, where we succeeded, where we hit roadblocks and delays, and how we'd like to invest in opportunities to improve our ways of working in the future.

Risks/Impacts/Considerations

• This information, while potentially insightful for future engagements with other partnerships, may not help the current engagement as much as expected
• The material generated at this retro will be HIGHLY sensitive and cannot be shared out at all
• Time schedule (30min) is too short to run this retro // follow-up meetings may be required

Open questions

• Is the ETOR timeline accurate and detailed enough to spark engagement?
• Which retro questions will resonate with folks the most? Which questions should not be used?
• How shall we synthesize this retro for learning purposes?

Links

• ReportStream_ETOR Retro_INTERNAL mural
• RS_TI Product Sync meeting notes

Acceptance criteria

• [x] Finalize retro structure and question list
• [x] Finalize meeting time and schedule

Out of Scope

• [ ] Synthesizing retro (next sprint)
• Creating any new documentation or ways of working for the ETOR initiative
• Running a consistently scheduled ETOR retro
• Develop product recommendations

[dylansmith-Nava]

Retro board is here and is in final review with @mxk0 and @jillian-hammer. cc @Andrey-Glazkv