Connect your dev tools,
get answers in Slack

☕ Morning, @Sam! 2 things to put on your radar this AM:

• A lengthy exchange between @Liam and @Alex on PR-353. Based on the tone of the conversation they seem blocked
• On Friday a decision was made by @Dave in #project-pluto to move forward with GraphQL instead of REST

Also Sprint 13 is still on track for 98% completion. 💪

Thanks for flagging. What else happened Friday while I was out?

Friday was busy. Here are the highlights:

• 3 tickets were moved to “Done”: LN-487 “API timeout fix”, LN-481 “User Roles Refactor”, and LN-479 “Google SSO”
• ⚠️ There was a minor outage. Very minimal downtime and impact. More details in #EE-15
• 4 PRs were merged, but as of last night PR-41 is still open

Is there dev work from the outage we’ll need to pick up?

Yes, 2 tickets were created related to the outage:

• LN-990 “Load Balancer Optimization” unassigned (1 point)
• LN-991 “Failover System Upgrade” unassigned (3 points)

Should I assign and add them to our next sprint?

Yea, although now that sprint will be over capacity. What can we punt without putting our Q4 goal at risk?

Both tickets added to Sprint 14 and assigned to @Charlie. He had extra capacity and is most familiar with that part of the app.

If our goal is still to have the notification system refactored by EoQ, I’d push LN-488 “Password Reset Flow”. While important, it’s not critical to the notification system work. Should I move that ticket to Sprint 15?

That works. Please nudge the owner of that ticket and let them know why we're shuffling things around

It’s assigned to @Alisha. I’ll Slack her with the context of our decision.

We'll also need to kick off the foundational work for SAML in Sprint 15. Here's a rough pass on what the system will look like.

Based on my diagram, can you put together an action plan, break down the work into milestones, and make suggestions for who should own what pieces of work?

Sure! Here’s a breakdown of work, divided into 3 milestones.

I’ve suggested owners and story points for milestone 1, which we should be able to complete in Sprint 15. Because of Thanksgiving, I’ve assigned everyone 40% less work than a normal sprint. 🦃

Milestone 1: Foundational Setup - 18 tickets, 6 engineers:

Thanks. I’ll review and let you know if I have any feedback

I’ve got 15 minutes until meetings start. Can you link me to that decision thread you mentioned in the Pluto channel? Want to get up to speed before my 1:1s

Nic told the team to move forward with the GraphQL API instead of the REST API. Based on the implications of that for our team’s work, I figured you'd want to weigh in.

The conversation is in #project-pluto. Here’s the thread:

Downstream implications could be an issue. I’ll dive in and get a handle on what they’re thinking

While I’m doing that, can you prep me for my 1:1 with Liam at 9:30? Beyond that blocked PR, what else do we need to discuss?

Here’s a list of highlights for your 1:1 with @Liam:

• 🚧 As mentioned, he appears blocked on PR-353
• The majority of his week was working on LN-482 “Data Sync Patch”, which he moved to “Final QA” on Friday
• He’s picking up LN-484 “Dark Mode Toggle” this week; there's a conversation on that ticket worth viewing with him
• He played an active role in Friday’s outage, which would be great to acknowledge and celebrate 🎉

Perfect! Please set a reminder to send me this kind of update 15 mins before every 1:1 with @Liam

✅ I’ve set a reminder to send you an update at 9:15am PT every Tuesday morning ahead of your weekly 1:1 with @Liam.