Pre-Q2 2023 Planning Notes/Action Items (3/30)

Meeting Notes:

1. Alignment of MVP Phase 1 vs Phase 2 is extremely important.

   1. To achieve understanding between Engineering, Product and UX, Emily and Lysle will be providing a high-level understanding of the goals, phases, timelines, and expectations of all Nurse projects and how they affect each other and the business.

   2. Discuss MoSCoW prioritization for Super Nurse with the smaller leadership group.

2. As we all know, there are many eyes on these projects from the entire organization. In order to accurately reflect our progress toward the final goal, we are going to make updates to our Jira process

   1. All open Epics and completed tickets before the end of the current Sprint (on 4/4) will have the Epic name appended with “Q1” to decipher tickets that we were trying to complete during Q1 vs the following quarters.

   2. Alyssa will export data on 4/4 to show completion percentage of Q1 tickets. Alyssa will create new Epics with the same names as before but add “Q2” and move any outstanding tickets to the new Epics.

   3. This makes it easier to view the total number of tickets we plan to complete during Q2 and how we’re progressing toward that goal throughout the quarter.

3. We are going to continue creating separate Front End & Back End tickets to decipher between the required work.

   1. PM is going to create each ticket based on the FE requirements, and the Dev team will create the BE ticket based on what needs to be completed before the FE ticket can be started.

   2. We will flag the FE ticket as blocked by the BE ticket to ensure the FE ticket isn’t started/pulled into a Sprint until the BE work is done.

4. In order to ensure prioritization of each piece of functionality, we will be continuously checking/updating the Backlog to reflect those priorities.

   1. PM is planning to create as many remaining tickets as they can before planning begins to ensure we have a full understanding of requirements to complete before the end of the quarter.

   2. Alyssa will work with the Product Managers to label all open Jira tickets with the correct phase and statuses.

   3. If a new ticket is created (bug, story, etc.) by anyone other than PM, discuss it with them so we can determine priority.

   4. If there are any design questions or dependencies identified, please surface to EM’s & PM’s and we can work with design on unblocking.

5. We need to call out all outstanding dependencies before Quarterly Planning. This will give us a better idea of what we’re blocked on, what priority is, and when we can start working on the ticket.

   1. Once the teams have determined all dependencies, Alyssa, EM’s and PM’s will work on addressing those dependencies with the responsible parties.

   2. Jordan Watson is our main point of contact for ECM related dependencies. We should include him in any meetings/conversations where he and his team may be of assistance.

6. We will have a combination of full team meetings as well as meetings with individual teams. This includes subsets of individual teams as well.

   1. We need to discuss this before Tuesday - I’d love input from the EM’s and PM’s.

   2. Pointing & T-Shirt exercise:

      1. We will review pointing with each team to ensure consistency across its members.

      2. After PM creates remaining tickets and prioritizes the backlog, the team will spend time refining as much as we can (this will be in multiple sessions).

      3. After we’ve refined as many tickets as we can, we will review all tickets within each Epic to estimate T-Shirt size. **

      4. These will be completely open discussions, and we encourage healthy debate so everyone has their voices and opinions heard.

7. Kickoff & Readout:

   1. Emily & Lysle will provide a team overview on Tuesday. They will be providing the full organization overview during Kickoff on Wednesday as well.

   2. We’ll have one Readout after planning where we discuss what each team is doing, and how it affects the overall goal of the Nurse.com project. Will Emily & Lysle be doing this as well?

8. The team will continue to work on high priority functionality during Quarterly Planning.

   1. The team will operate at a 40% capacity and pull in tickets that we feel we can commit to during the Sprint.

9. You can access the meeting recording here.

** Team Blue Dot will function differently than Krypton as part of the team will be lead by Janaky and the other by Raymond. We are going to order the Backlog and priority by Epic (under the same MVP Phase) so each team knows priority and we don’t have to worry about confusion within the Backlog.

Action items: