We will sanity check / confirm which components need focus style updates with Eugene.
Backlog grooming
Is there anything from design that’s ready for engineering that can be prioritized for Raccoon Gang?
===
We will start creating/grooming at least 1 sprint (2 weeks) in advance.
Better surfacing engineering roadmap for Paragon
Lise’s team picked up Pagination component updates when it was already slated for Raccoon Gang, and ultimately had somewhat duplicative work.
This was surfaced at Monthly Arch Hour.
Kelly Buchanan and I are discussing in more depth on 3/7 at 3pm.
===
Sprint idea from above might help
More visible roadmap for engineers
===
Some initial questions:
How did the duplicative Paragon work originate? At what point was it decided that a component needed to be updated in Paragon since it didn’t match the spec? Did this come from design or engineering?
How can the Paragon backlog better be surfaced?
How can we encourage teams to pose more questions in Slack to ask about current state of components and whether it’s already resourced for an update?
Are there things from the Maintainers OEP that Paragon does well or could do better?