Retrospective
Henrik (Reps Peer) had the great idea to run a retrospective in this Council meeting. A retrospective is used in agile development to review a team’s work from a given past time period. We spend the whole time of our meeting discussing the following topics:
- What should we stop doing?
- What should we start doing?
- What should we continue doing?
Everyone could add their ideas and then we voted on those and discussed measures to fix identified problems or ideas for the future.
We identified the following measurements:
Issue: Stop saying “no” or “we’re not convinced” and not providing constructive feedback to Reps. Turns into very long back and forths and a lot of frustration.
- Measure: Identify “Template bugs” to help mentors understand acceptable/rejectable bugs
- Measure: Mentor training about changed/updated SOPs
- Measure: Leverage regional mobilizers (coaches) to reach out to Reps more often
Issue: Start providing more guidance on Mozilla’s goals to Reps - Measure: Create Wiki page for 2016 goals
With a “Return on Time Invested” value of 4.7 out of 5, we think we should run this session more regularly to review where we need to focus and to see what we need to stop doing to improve our work. For the next time, this should not be taking up our Council meeting time, but instead scheduled independently to make sure we can still discuss important matters on a weekly basis.
Reps Issues on GitHub
We still have all our tasks in the Reps GitHub repository, have a look there to get involved and keep up to date with what we’re up to.