Super Nurse Leadership Weekly Sync

10/2/2023

Communication gaps:

• SN Teams & Clearly Undefined → need to know what the others are working on so we’re all on the same page

• Marketing makes updates in CMS and doesn’t always tell us

• We get bug tickets sometimes when QA/Staging doesn’t meet Prod

  • Can we set up a monthly sync to get these all updated to match?

Post-launch post mortem/retro:

• I (Alyssa) want to set up time with folks to go through the project as a whole and figure out what we did well/could do better next time

• Same for the actual releases the last couple weeks

9/18/2023

Did not have a meeting because of the war room meeting this morning and the others this week

9/12/2023:

Super Nurse - Priority Check In

• Sprint schedule/planning updates post-launch

• Extend current Sprint & planning for next week

Other issues:

1. VPN issues - literally having disconnects every 5 minutes for yeary today - suspected cause is not enough licenses

2. Request for Yeary to be able to help Aaron/Christian on importer work

3. Job board admin end to end:

   1. Lysle needs to validate adding orgs, adding slots

   2. For launch we need to create the feed customers to migrate with slots - Aaron needs the org ID

   3. There’s a chance that production DB needs to be wiped so we don't want to do this too early

   4. Action item: Sean will do quick script to create manually - Lysle to provide list to him

4. Aaron needs a user created for his staging org - Raymond /Lysle should be able to do this - we will check

9/11/2023:

Super Nurse Leadership Weekly Sync

• Outstanding Magento questions:

  • Note from @Brianna Collins in SUP-747: Magento is continuing to regress - Jay, Matt, and Christian are looking into it with the goal of getting it resolved today

  • Devesh and Cesar should be involved in this thread along with Pankaj and Katie - do we have an update on this convo from this morning?

  • Other related tickets: SUP-885, SUP-752, SUP-639 & PAP-7865

  • New ticket for QA API issues is PAP-8108

• Sprint review reschedule

• Craft deployment

• Cypress

• Zaengle plans

• Internal prod- this is confirmed set up /deployment successful now or not until release tomorrow? Where do we access?

• Data Migration efforts- what are next steps here? We have scheduled data mapping tomorrow- what are we needing to accomplish in this call specifically?

• Release planning- we need to determine the deployment windown and expected downtime so I can coordinate user messaging with ops.

• Plans for decision points on critical items that wont make code freeze- what is our decision tree path here to ensure alignment on if we need to pivot release plans ?

9/7/2023:

Super Nurse Leadership Weekly Sync

• App Support Enablement for Job Board (convo from call with Joel):

  • Prod accounts for http://Nurse.com in order to replicate issues

  • Access to Prod data: Either real-time read only or yesterday replication like SQL internal

  • Training:

    • I think Svante may be able to help with the UI - he's the Client Care SME for Nurse

    • Explanation of data - schema, frequent tables, interaction with UI, access, repos, etc.

  • I'll reach out to the leadership group first with this info, and I'll probably set up a call with me, you (or Mike), Ashley, Matt & Jordan

• Internal release schedule (Ashley)

  • Sean doing at-will deployments of the BE as needed with no breaking changes

  • FE deployments will be scheduled with ECM

    • Will plan for 9/12, 9/15, 9/19

    • Proposed that the final deployment to prod will be 9/19

• Production Magento connection (Ashley)

  • Would break auth for current users when switch over occurs

• Data Migration update (Ashley, Adam)

  • Lysle/Katie working on messaging to customers after data migration

• Where devs should focus their time once they’re done with tickets and can’t help with other sprint work (Ashley)

  • Paired programming to help everyone get their committed work completed (senior specifically)

  • Reach out to devs to see if work can be split

  • Reach out to QA to help with sprint testing

  • Internal Prod hardening

  • Data verification after migration has begun

  • Pre-refinement of Talent Match work (Yeary-specific, maybe hold on this until code freeze)

• Iterable discussion (Sean)

  • Mail-gun – least amount of work

  • Link the email rather than attach

    • Will need to set up invitation and system-generated emails. Mail-gun would be more secure for this

  • Bri, Lysle, and Sean to consider discussing

• Segment tickets/last-minute scope (Ashley)

8/28/2023:

Super Nurse Leadership Weekly Sync

• Reschedule Sprint Review, Planning & Retros

  • We had talked about taking up most of the day on Wednesdays (every other starting 8/30)

  • Suggestion is 9:30-10:30 Review, 10:30-12 Retro, 1-2:30 (or 3) Planning

• Streamline dependencies/priority conversations across teams:

  • Convo in leadership channel then shared with team-supernurse?

  • Specific dependencies channel?

  • What works best to ensure work is done & prioritized, but also sounding the alarm as needed

• Pre-planning discussions for Quarterly planning (dates TBD based)

  • Alyssa will be OOO starting Wednesday 9/20, returning Monday 10/9

  • Discuss format & topics to create schedule and documentation ahead of time - see below for Q3 details

    • https://relias.atlassian.net/wiki/spaces/CEMVP/pages/3478651053

    • https://relias.atlassian.net/wiki/spaces/CEMVP/pages/3479601250

• Plan to follow up discussions with Justin on release planning/ECM & webscale. when should we set this for this week? also I do need to get back on estimated down time asap to internal teams so would like to get a final estimate on this as soon as we can (1 hour, 2-4? more than 4..I don’t think so but need some kind of estimate)

8/21/2023:

Super Nurse Leadership Weekly Sync

• @Ashley Edds with updates from conversation with ECM about the following

  • New environment

  • Scheduled release cadence

  • Webscale meetings

• Once we’re ready to QA from Stage to Prod (no rush on this answer):

  • Will we have individual columns for each status between all 3 environments (this feels v overwhelming) or will we have 3 separate boards to monitor

8/14/2023:

Super Nurse Leadership Weekly Sync

• Do we have a Confluence page with final functionality required for go-live so we can review the Backlog & all outstanding tickets ASAP?

  • Where are we in documenting bugs found as part of the critical features for go live? What help is needed for this process?

    • Smoke testing plan for MVP features. Product will be doing daily and logging bugs we find and reviewing priority and scope with managers/leads and surface priority in channels/ DSUs <?>

  • Alyssa created a filter to track all open bugs across the Super Nurse project

    • You can see that the filter excludes closed/archived tickets and is ordered by most recent date

    • Reminder: If the Product Team is not added to the ticket it will not show in the Backlog - this needs to be default for everyone going forward

    • We should consider creating a specific fix version for critical go-live bugs (to be worked on during code freeze) - discuss with @Ashley Edds

      • Bugs before code freeze, MVP-1 bugs, fast-follow bugs, etc.

      • Current doc

  • Bri was initially tracking issues in QA in this Confluence page, but it hasn’t been updated since June - I’m not sure if they’re being tracked elsewhere:

• EMs completed first pass of release items on spreadsheet – we can review plan for data migration, site switch over, and testing.

• IDP4 Upgrade Scheduled for 9/7 - Testing Plan for All Retail Sites (including Nurse.com for CE Admin migration)

• Mediakit subdomain change: Plan to change mediakit subdomain to nurse domain and set url redirects

• Bug prioritizations

• Discuss notes in this ticket (if we have time - this can be taken offline!):

Final functionality requirements:

Testing plan established for IDP4 integration:

Mediakit Domain:

Communication changes:

Prioritization Requests from @Lysle Baker (Deactivated) since Bri is out:

8/8/2023:

War Room

Overall project health - Alyssa to share fist-to-five/Retro notes

Team TBD updates- stories of concern/looking forward 2 sprints ahead to code freeze

Team Krypton updates- stories of concern/looking forward 2 sprints ahead to code freeze

Rollover decisions from yesterday:

8/7/2023:

Super Nurse Leadership Weekly Sync

Alyssa Grissom
Ashley Edds
Brianna Collins
Emily Christian
Isaac Mahler
Katie Lucas
Lakshmi Kondragunta
Lysle Baker
Matt Meineke
Raymond Sidharta
Sean Kramer
Surya Bhatt

CE Admin Migration:

• CE Admin migration timeline: Had been planned for August 23, delays with catalog importer, survey reporting, and RLMS enrollment queues. New target date is 9/13.

  • Will need either submarine or supernurse release on day of CE Admin migration

    • Who needs to be involved in that?

    • SUB Profile tickets have passed in QA but we can’t test them in Staging until after the code freeze (SUB-819 | SUB-820 | SUB-821 | SUB-792)

  • Concerns related to releasing on same date and/or within a week or two of each other?

  • Benefits to releasing on same date?

• Magento is in code freeze after 8/7/2023 release until CE Admin migration

  • Answer from Pankaj about unplanned issues:

    • "Yes, we should be able to roll back. We have to plan for that, take db backup etc, so we can restore db if needed. Test site properly in maintenance mode (only accessible to us) before making live for actual users."

Super Nurse Initial Launch:

• When do we want to take down the current live site?

  1. Need time to capture data diffs and run migrations

• When do we want to add messaging to the current live site alerting users to downtime?

  1. Need messaging from product/UX

• What is our targeted total downtime window?

• When do we want to cutover?

  1. Is there anything to consider other than DNS cutover?

• Need to create a page for the site downtime.

  1. Need messaging from product/ux.

  2. This is intended to be the new maintenance page; Katie has this in flight with Webscale:

• Can we change go-live date from Friday 9/15 to Wednesday 9/13:

  • Doing a release on a Friday is not a good idea

  • Launching Wednesday morning gives us 3 full days to determine if there are any big Production issues & have time to remedy

• Can we start the code freeze starting on Wed 8/30:

  • This will be a functionality freeze - we can still work on high-priority bug fixes as deemed necessary by PM

  • Everything from QA will be pushed directly to pre-Prod

    • There’s no need to deploy to Staging right now → this will be done post-launch so that environment can be used for demos

    • NOTE: We need to share messaging with leadership that demos cannot be done during this time - they will have to wait

    • This gives us 2 full weeks to do intense regression testing & make sure we have time to go through the site entirely and address any bugs

• Allocating some dev time to get the latest code to staging

• Magento, Craft & Vue work@Christian Roberts @Isaac Mahler@Katie Lucas

  • Where does this stand? What do we need? Who do we need to have prioritize this work?

  • Christian is helping with some of this - let’s review together (PAP tickets related to Magento/Nurse.com)

Concerns to research:

Final decisions for CE Admin Migration:

Final decisions for Super Nurse initial launch - save conversation for war room tomorrow:

Need help from the Leadership group to:

Lysle to discuss:

7/31/2023:

Super Nurse Leadership Weekly Sync

Alyssa Grissom
Ashley Edds
Brianna Collins
Isaac Mahler
Janaky Nemmara
Matt Meineke
Raymond Sidharta
Sean Kramer
Surya Bhatt

• FIST TO FIVE: UNANYMOUS 2 DURING SHARED RETRO

  • How are we delivering this messaging to leadership above us?

  • FE:

    • Backend changes breaking FE - requires new tickets to fix FE, etc.

      • Shouldn’t continue to go forward, but has happened previously and caused some delays & more work

    • UX difficulties - designs aren’t accurate & force us to have to use AC or go back to UX for updates

      • Design is low priority & team will work on tickets based on PM decision where the description & AC match

  • BE:

    • Sean is working on & Jane is working on

    • Raymond & Sean descoped a lot from the FE tickets that don’t require these new BE updates

    • Credit System has not been developed yet

  • How are we going to proactively share information to the larger group?

    • FE/BE code that breaks another

    • Code changes that later require manual changes to already implemented code

    • Build failures

    • Anything that can affect dev/QA work

    • Really want to make sure EM/PM/DM are aware as well

    • team-supernurse channel.. create a dependency-specific channel? other thoughts?

• Redefine purpose or Pre-Refinement meeting:

  • Recently rescheduled to T/Th 3-4 every other week

  • Need to add another Pre-Refinement group or move SOS on those off weeks

• Production Release documentation/details:

  • I believe Lysle is/did create a document for this - if yes, can we link it here? Here it is:

• One Month Left for New Feature Development

  • When are we code freezing before launch?

  • Continue Dev work during August & spend the last 2 weeks testing

  • ** FEATURE FREEZE - BUG WORK WILL CONTINUE **

  • Not going to be testing ticket by ticket, but flow from start to finish to ensure accuracy

Job Importer Proposed Polution:

• Backend Team:

  • Spin up a separate job importer microservice that can be called by Aaron to push in jobs

  • Will expose endpoint for existing job scraping process to call (consult with Aaron on contract)

  • Will queue up jobs to be saved

  • Customers can be configured to ignore credits

  • Consume job queue

  • Listen for jobs queued and post them to the site

  • Will save jobs as draft status if the customer is out of credits

  • Will ignore credits if customer is set to ignore credits

• Aaron:

  • Will modify existing process to call new job importer microservice

  • Work with backend team to define contract for this call

7/24/2023:

Super Nurse Leadership Weekly Sync

Ashley Edds
Christian Roberts
Katie Lucas
Lakshmi Kondragunta
Lysle Baker
Raymond Sidharta
Surya Bhatt

• Discuss “Summer Fridays” plan - potentially move to another month

• Discuss nightly Nurse.com site outages - meeting with Madgex tomorrow to learn more

• When do we want to take down the current live site?

  1. Need time to capture data diffs and run migrations

• When do we want to add messaging to the current live site alerting users to downtime?

  1. Need messaging from product/UX

• What is our targeted total downtime window?

• When do we want to cutover?

  1. Is there anything to consider other than DNS cutover?

• Need to create a page for the site downtime.

  1. Need messaging from product/ux

Notes:

7/21/2023

Alyssa is on PTO on Monday

• We should start talking through how we want to handle go live in terms of timing and downtime, so we can start working with ECM and add any messaging we want to current nurse

Notes:

7/10/2023:

Super Nurse Leadership Weekly Sync

Alyssa Grissom
Brianna Collins
Emily Christian
Janaky Nemmara
Katie Lucas
Lakshmi Kondragunta
Lysle Baker
Raymond Sidharta

(EM’s have a conflict and will be unavailable today)

• QA vs Staging PM Review

  • What cadence will we be deploying from QA to Staging?

  • EM’s have a meeting today at 4:30 so we’ll revisit this next week

• Weekly Engineering Update

  • When do we get together to discuss?

  • Should this align with some Atlas updates?

• Alyssa cleaning up Jira tickets/statuses

• Team updates:

  • Diep & Henry to Blue Dot

  • Devesh helping Henry with Segment work

  • Christian to focus on Job Board dev work with Krypton

  • Two new devs (one to CU & one to Krypton)

  • Radicle dev to help with payment process

• Jenn, Lysle, Emily & Nico will be unavailable most of the week

  • Tuesday/Wednesday Emily & Lysle will be in all day

• Transition plan from Emily to Janaky

• Deeper scope discussions on data, release planning, etc.

  • Will revisit with Lysle next week once we know who we need and when we need to schedule

  • Aaron working on options - need to figure out if we have one specific option or multiple to choose from

  • If Katie/Pankaj can help in Lysle’s absence, let them know

Notes:

6/20/2023:

Bi-Weekly Super Nurse Pre-Refinement

Alyssa Grissom
Brianna Collins
Isaac Mahler
Janaky Nemmara
Lakshmi Kondragunta
Lysle Baker
Raymond Sidharta

• Cancel all standing meetings next week (DSU, Retro, Refinement)

• Alyssa to schedule 9:30-10:30 Super Nurse Kickoff

  • Christian & Ashley to confirm was FE expectations & closing statements are

• Alyssa to push Sprint end date to 6/29, new one will start Thursday 6/30 & end Tuesday 7/11

  • Alyssa to setup Super Nurse Sprint Review Thursday morning then Blue Dot & Krypton Planning separately

  • Delete Sprint Retros on Monday time slots

  • Setup async Sprint Retro on Thursday or Friday

• Move Super Nurse Q2 Retro from 3-4 to 1-2:30 on Monday

  • Add Fist to Five

  • Alyssa to create Easy Retro board ahead of time for everyone to fill out

  • We'll still give time at the beginning, but this will be better if we have more time to talk

• 2:30-4 Epic Owner Discovery Part 1

• 10-12 Tuesday/Wednesday Epic Owner Discovery 2 & 3

  • What's outstanding?

  • What/who do we need?

  • PM & UX discuss

• Need to ensure everyone patriciates - super important!

  • If Devs are local, can we try and get as many people in person?

• Need to determine FE/BE Epic owners

  • EM's, how do we determine this?

  • Explain shared responsibilities for everyone - may be needed in one place now and another later

• Product Priorities Epic sheet:

  • Include Release discussion in 1-3 & 3-4 on Thursday

  • Technical & Product pieces

  • Lysle to provide more info

• Alyssa: Need to try and figure out capacity tracking for the rest of the quarter

  • What have we done so far?

  • Any sort of estimate?

  • Compare to Capacity Tracker

  • Ask team to add PTO/Holiday schedule ahead of time to get a general idea of capacity for future Sprints

• Focus on Story Pointing & keeping accurate commitments

  • What have we been able to complete by Sprint so far?

  • Do we have the ability to look at it by Dev (not right now because we don't always use it)

• Need to figure out who can work on Segment, other niche functionality - do we need a add a "buddy"?

• Alyssa clone Miro board templates for Group

• Alyssa & Lysle be annoying  requiring specific individual feedback and decisions

  • Figure out technical dependencies based on Product requirement

  • Need to figure out what to do for functionality ASAP

• Who's doing the presentation on Friday?

  • Sounds like Lysle if she doesn't travel

• Keeping end schedule 4-4:30 -> Leadership wrap-up

• Always make sure there's a Teams meeting for everything

• At least 1 PM & 1 EM need to be available for representation during all meetings

Alyssa To-Do’s:

Team To-Do’s:

6/19/2023:

Super Nurse Leadership Weekly Sync

Ashley Edds
Brianna Collins
Emily Christian
Janaky Nemmara
Jenn Seith
Lakshmi Kondragunta
Matt Meineke
Raymond Sidharta
Surya Bhatt

What are the blockers & who/what do we need to resolve them?

• Review Plan for Q3 planning next week. Q3 2023 Quarterly Planning Schedule (WIP) - Relias Communities Platform - Confluence (atlassian.net)

  • When will sprint planning for the upcoming sprint occur?

    • Will have a clear idea of what should be pulled in for Sprint 1 based on allocation for each sprint for the readout.

      • Consider a brief capacity check for Sprint 1

    • PM will pull in what is allocated for Sprint 1 of Q3 for the upcoming sprint

    • Devs will be working in a more Kanban-style, so they will grab tickets the PMs bring into Sprint 1 and continue grabbing new work as they complete work, based on backlog prioritization and discussion with PM

  • Need to take time before next week to do the following:

    • Assign FE/BE epic owners

    • Schedule rooms for the FE/BE syncs and cross-focus syncs

  • End current sprint on Friday since everyone will be full-time planning next week?

• Raymond/Janaky/Chris/Tom (Zaengle) need to sync up ASAP to discuss Craft header/footer/nav

• CEAdmin concerns?

  • Concern communicated to Matt last week about the work App Support and D&A are doing – Matt to f/u with Joel and the supernurse leadership team about what the actual issue is and if there is any risk/mitigation needed.

Action Items:

Notes:

6/15/2023

Jenn, Matt, Lakshmi, Surya, Ashley, Bri, Raymond, Lysle, Christian

ON-SITE MEETING:

• Vendor Contracts:

  • Need to extend Zaengle’s – goes through 7/30

  • Razar’s extended through October

• FE sync or SOS?

  • Keep FE sync smaller to keep everyone comfortable

  • Create invite for SOS = DM, EM, PM, Christian & Sean - invite specific individuals when needed

• What concerns or major dependencies to we have with getting something out on time?

  • Issues with QA and code wiping out with each other’s code

  • Christian is working on

• Who do we need in office during planning?

  • Would love to get as many people here as possible

  • Team-building, getting excited about the quarter!

• Quarterly Planning:

  • 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

• Jenn wants to have a leadership sync every other week to have a similar discussion as today

  • I can update the meeting we already have on Monday with DM, EM’s, PM’s, Directors, Jenn to 1-2 ET every other week

• Others to add whatever I may have missed

Action Items:

Notes:

6/12/2023:

Super Nurse Leadership Weekly Sync

Alyssa Grissom
Ashley Edds
Brianna Collins
Emily Christian
Janaky Nemmara
Jenn Seith
Lakshmi Kondragunta
Lysle Baker
Matt Meineke
Raymond Sidharta
Surya Bhatt

Where did we land on Sprint Review?

• Given the Sprint ends tomorrow, are we expected to do one?

• We need to finalize decision for future Sprints so we can let the teams know

Action Items:

Notes:

Pre Q3 Planning Discussion:

• Reminder: all week Monday 6/26 (kickoff)-Friday 6/30 (readout)

• Find my initial thoughts/suggestions for topics and schedule here

• We need to send details/invites to the teams asap so they know what to expect

Action Items:

Notes: