Retro: May 13, 2022

Miro Board

What is working well?

Process and Communication

• We are in sync and we know what we are doing
• Collaboration and communication continuing to improve
• Continual improvement and iteration on processes and workflows
• Process iteration has been positive
• v2 processes and support team ramping up and rocking
• Example support flow for summoners is looking awesome

Tools

• Docs and notes
• Filtered Kanban views
• Going through the tickets by project

Tools

• Kanban and wiki are working for me
• Aligning on importance of creating solid foundations (component library/pattern library, SDK/data package, etc.)

Onboarding

• Onboarding is getting easier
• I was able to pretty quickly get local dev environment set up for v2
• Ad hoc meeting re: backend services was very helpful to get a lay of the land

Issues

• Identifying issues earlier and earlier
• Tickets are getting made faster
• Tickets being ready and prioritized

Discovery

• New discovery step for specs is helpful to ensure alignment at the beginning of the cycle
• discovery cards
• tag team ticket writing

Design

• design work unblocked, starting to get patterns settled

Specification

• Getting more accurate in our feature speccing

Development

• Pairing sessions
• Swarming to blocking issues
• Incremental use of libraries
• Progress across all packages/apps in active design/development
• Boost example by Jord was really interesting

Review

• Review process is improving my output/quality
• Fast review turnaround

What needs improvement?

Product Vision

• Better idea of the product vision (continue this work)
• Product vision and strategy happening during design or implementation
• Deferring challenging discussions/questions

Docs and Onboarding

• Unclear relationship between V3 and V2 dev crossover
• Onboarding- are we ready to add 1 or 2 more dedicated devs or a designer?
• New contributor doc improvements: our stack can be intimidating
• Building out more time for higher level docs
• High level docs (Product Spec)
• Trial by fire, demonstrate skills, prove commitment

Issues

• Stay on top of tickets for work that folks are doing outside of planning
• Ticketing unexpected bugs

Improvement and Integration

• Deferring Horizontal integration
• Test out dedicated time for improvement/refactoring

Speed and Focus

• Could we go 10 mph faster?
• WIP limits?
• Too many distractions
• Are wargames an unnecessary distraction?

What would we like to change?

Onboarding Policy

• Developers start on v2
• Minimum weekly commitment for v3 is 16 hours