FY22-Q3 Manage:Optimize FE OKRs

Parent OKRs: Engineering | Development | Dev | Manage Stage OKRs | Manage Product OKRs

Adoption & confidence in our product

• Key Result: Increase community contributions to 10 => 35%
• Key Result: Decrease number of open S3/S4 bugs by 50% for reliability => 80%.

Support each other and ourselves

• Key Result: Increase Manage retrospective engagement to 60% per milestone => 100%
• Key Result: One frontend engineer becomes technical interviewer => 100%
• Key Result: 100% Feedback to team members (Mid year reviews & 360 surveys) => 100%
• Key Result: All FE team members complete technical writing training => 100%

---

Retrospective

Good

• All team members completed the technical writing training early in the milestone. Their feedback was very positive. @ekigbo even made a small checklist of things to look out for. These takeaways might also be useful for others who didn't take the training or team members who are looking to refresh their knowledge.
• We could significantly reduce the number of S3/S4 bugs (4/5) and managed to keep the number of new/incoming bugs to a minimum.
• @blabuschagne became a technical interviewer and @ekigbo has almost completed his interview training issue 🎉
• Even though we did not reach our anticipated goal of 10 community contributions per months, we significantly increased our community contributions and maintained a minimum of 3 community contributions/months. Given that we didn't have any community contributions prior to %14.1, this is still a great achievement on a very ambitious goal. Moreover, we documented our findings on problems with community contributions and improvement ideas here.
• Participation in the monthly retro increased after the initial experiment (dropping a reminder in Slack) and we found a way to automate the reminder. Thank you @blabuschagne for driving this.

Bad

• One issue that was part of our OKR about reducing the number of S3/S4 bugs, was lacking a clear solution proposal and shouldn't have been added to that list. There was a discussions around a bigger UI refactoring that hasn't been resolved yet and prevented us from executing the issue in Q3.
• The team is in a little bit of a weird space with team members moving around, this made it slightly more difficult to determine who exactly we'd expect to participate in the monthly retrospective.

Try

• Again, we missed out on adding retro feedback during the quarter. Let's try to contribute to the retro earlier next quarter.
• As for the retro participation, we can experiment with different the reminder dates and also add reminders to the team call agenda as well as to 1:1s
• Some improvement ideas on how we could increase the number of community contributions:
  • Maybe we need to start out by migrating more legacy code components to lower the entry barrier? (e.g., migrating components to Vue/Pajamas on the frontend)
  • We should provide all the necessary information in the issue description. We cannot expect community contributors to pick up issues that only contain information like The following discussion from _MR_ should be addressed without providing additional context
  • We should try to brake down issue into easily digestible pieces (weight of 1), this could become something that we do periodically
  • Ideally, we can add an implementation plan to the issue description