Seamless Page Build — Priority Task

Overview

The Seamless page build was identified as a critical priority item during the ^[1]. The task had sat untouched in Jeff's queue for two full weeks while other projects took precedence. Compounding the issue, Jeff unilaterally changed the due date without AM approval — a process violation that was addressed directly.

The due date was restored and the build was re-prioritized as Jeff's top focus for the sprint, with a client meeting scheduled for the 26th and a hard delivery target of January 28, 2026.

Status

Background & Issue

• The Seamless page build had been in Jeff's queue for two full weeks with no progress.
• Other incoming tasks were allowed to take precedence without AM consultation.
• Jeff changed the due date on his own initiative, pushing it to end of month — discovered by Melissa on Monday, January 20.
• Melissa had a client meeting on the 26th requiring deliverable pages, making the original timeline non-negotiable.

"He updated the due dates without talking to me or us... you can't do that. I have a meeting on Monday."
— Melissa Cusumano, sprint planning meeting

Resolution

• Due date was restored to align with the client commitment (January 28).
• Jeff was directed to treat Seamless and ^[2] as his top two priorities for the sprint.
• Melissa communicated directly with Jeff that developers cannot change due dates without AM approval.
• Sebastian is also on the Seamless account in a supporting role, though not driving the build.

Process Note: Due Date Policy

This incident reinforced a standing rule that should be documented and communicated to all developers:

Developers must not change task due dates without explicit approval from the Account Manager. If a deadline cannot be met, the developer must flag it to the AM immediately so the client relationship can be managed appropriately.

See also: ^[3]

Key Contacts

Related

• ^[4]
• ^[2] — co-priority with Seamless for Jeff this sprint
• ^[5]