Page Comparison

Alyssa Grissom (both)

•  Ensure understand of MVP phases & priorities.
•  Leadership team (headed by PM) to look through open tickets to ensure requirements are complete, statuses are accurate, etc.
•  Consistency of requirements and style guides for tickets from Q2 on.
•  Discussion on priority of fixing things that have already been done but don’t affect functionality/DoD for launch.
•  Address any questions, concerns, blockers, etc.

•  TBD
•  Confirmed: Follow Figma guidelines as is. Unless you immediately know that something is really wrong, you are not expected to audit the differences between Figma and the official Style Guide. We will spend time after the initial MVP launch to address these updates.

Ashley(but Alyssa is subbing for me while I’m out)/both teams

•  QA Team Regression during Q2 planning – QA team will use some of Q2 planning time to complete a full regression of the QA env in its current state. See below for details.
•  FE Leadership team (Jasmine, Isaac, Christian) will spend some of Q2 time going through current code repo, finding all code comments, removing them from code and capturing issues in tech debt tickets.

•  Create regression testing tracking spreadsheet
•  Discuss tech debt meeting objective with front end team

Lakshmi/Krypton

•  TextKernal-specific Refinement during Q2 time

Surya/Krypton

•  Sharing limited backend resources for competing priorities and choosing the top items

Qiyi/Krypton

•  Q2-Epic and Q1-unfinished epic move should be done before the planning meeting so that we know how much is carry over work and how much can we accommodate

Alyssa Grissom (Deactivated) this maybe a pre-work for quarterly planning, a great callout