Pre-Q3 2023 Planning Leadership Meeting
Shared Word doc here. Comments in red are from the leadership meeting on 6/15.
Discussions:
Eng/Prod to discuss feasibility given remaining Q2 work and expected completion before Q3
** most important in my mind **Process for sharing issues/concerns with go-live date
I.e. extend date (last resort) or decrease scope
PM to discuss with Jenn/Shawn and determine priority
Assign BE & FE Epic owners to discuss dependencies and create necessary tickets
BE & FE testing expectations to prevent issues with breaking each others code
Christian is also starting auto smoke tests that the Devs can run pre-PR and the PR approvers run it again before approving
Jira is the source of truth:
Outside convos are 100% okay and encouraged – definitely easier to discuss
If you have an issue, please put it in Jira first, have your convo, then add decisions/notes to Jira
This keeps everyone in the loop, and we can determine if there is a larger issue/have insight to delays, dependencies, etc.
PM:
Discuss remaining requirements before go-live
Create as many remaining cards as possible
Include all acceptance criteria
UX: Need consistency across cards & include them in some planning meetings
Lysle to follow-up with UX on consistency
Bethany to discuss joining Refinement and other necessary ceremonies
Alyssa to add Kate to future refinements
PM/UX:
Work through questions & get UX designs as early as possible (async/separate?)
Utilize the newly created UX project in Jira to link cards/create visibility & transparency
PM/Devs: Ensure all Jira fields are accurately filled out (notes below)
Atlas review & responsibilities:
Teams to review Confluence documentation
Why are we using it, what is the value, who adds updates, etc.?
Stakeholder mapping session (leadership group)
Answer any other questions
Ceremony review:
Sprint Review every other week – determine date/time/cross team
Chapter meeting expectations
Refinements:
Individual teams
Pre-refinement cross-team
Epic owners expected to review and bring tickets to ceremony
Retro: I am creating new Miro boards for consistency
Sprint 6 (23:12) suggested dates: Wednesday 6/14-Friday 6/23 (instead of ending on Tuesday 6/27)
Q2 Retro:
Should make this quarter smoother and more efficient
We NEED feedback from everyone – leadership, individual team members, managers, etc.
Sprint 7 (23:13) would usually start on Wednesday 6/28, but I'm suggesting we don't start work at all
We need to spend as much time together as a team preparing for Q3
We could start a new Sprint on Monday 7/3 (Tuesday 7/4 is a holiday) using the remaining Q2 work and whatever else PM prioritizes for Q3
Alyssa to create Miro boards (with leadership approval) for various sessions
Kickoff and Readout board are being revamped for simplicity as we speak
Alyssa to start DM responsibilities with Clearly Undefined in Q3 (TBD exact details)
Jira Ticket Requirements:
Status: reflect progress & add flags/comments if blocked
If your ticket is blocked/blocking another, suggest “watching” those tickets to get consistent updates
Check on active blockers and follow-up as needed
Product Team: required for cards to show on boards
Developer & Tester for reporting – UX Designer if we have it
Story Points: need to be added before a ticket is added to the Sprint
Sprint: tickets need to be pulled into the Sprint if being worked on
Backlog Status:
To Be Refined = Has not been reviewed yet
Needs Detail = Refinement started but we need more info from PM/UX
Ready = Refined, pointed & ready to work (Status should be Ready for Development)
E-Com UX Status:
Treat like Backlog Status but with different options
Tickets should be "Completed" before work starts
Fix Version: required to move tickets through workflow
Reference for past info:
Pre-Q2 2023 Planning Leadership Meeting