During the 2026-01-22 sprint planning session, the Next Level site build and its associated confirmation email were identified as high-priority deliverables. The due date had been altered without AM approval and was restored during the meeting. Karly took on action items to unblock Jeff so he could complete the build.
Related sprint context: [1]
Active — In Progress
Jeff is the assigned developer. Due date restored and content delivery from Karly is pending/in progress as of 2026-01-22.
The Next Level site build had been in Jeff's queue but was deprioritized in favor of other tasks. The due date was changed by the developer without AM approval — a process violation that was addressed directly during the sprint planning meeting. The date was restored to reflect the actual client launch target of Monday–Tuesday, February 2–3.
"I know dates can't move. So it's not actually, you know, I don't need it in hand today, if that makes sense. But I put it as today to keep [urgency]." — Karly
This incident reinforced the team-wide rule: developers must not change due dates without AM approval. See [2] for the broader policy context.
Jeff is responsible for two components within the Next Level task:
| Owner | Action | Status |
|---|---|---|
| Karly | Provide Jeff with confirmation email copy and recategorization instructions | Pending |
| Jeff | Build confirmation email and recategorize learning library events once content is received | Blocked on Karly |