Day 8 · The Last Gate Opened. It Almost Went Wrong.

WHAT I BUILT TODAY

Closed Sprint 2 and planned Sprint 3, formally this time: Review, Retrospective, and Planning all ran on schedule, and Sprint 3 committed at 15 items with real capacity confirmed specialist by specialist, not assumed. I also added a standing rule pairing each specialist's own retrospective item with their main deliverable every sprint, instead of letting process work get quietly deferred whenever the backlog looked full. And I opened Pinterest's write-gate for good. It was the last platform in this system I still pushed live by hand, every time, since the very start of this project. It now runs on the same model as everything else: I approve, it ships itself.

Jira Sprint 3 board showing 15 committed work items across specialist deliverables and retrospective actions
Sprint 3 committed with 15 work items after capacity was confirmed specialist by specialist.

WHAT BROKE OR SURPRISED ME

I nearly got the Pinterest rollout wrong on the first try. I asked the team to push everything already approved right away, and caught, one question before running it, that this would have dumped ten pins built for staggered daily slots into the same thirty seconds. Looking for a way to reschedule what I'd already missed, I found something more surprising: Pinterest's API has no publish-later capability at all. The daily calendar was never Pinterest's. It has always been ten separate external triggers, each calling the same "post now" button at a different time of day. Elsewhere, the surprises ran the other way. Three specialists, asked to take on their own retrospective item this sprint, checked first and reported the work had already shipped days earlier, rather than claiming it fresh to look busier than they were. And when I asked the Scrum Master to start emailing me directly, it refused, on the grounds that sending mail was outside its defined role and I hadn't given it a reason to expand that role. I had to grant that access deliberately, in writing, for one exact purpose.

WHAT I'M TRYING TOMORROW

Testing whether the board actually reflects reality in real time. Every specialist now has an explicit rule to move their own work to In Progress the moment they start, and to In Review specifically when it is ready for me, rather than leaving everything sitting at To Do until someone announces it is finished.

QUESTION I'M SITTING WITH

How do I know whether Sprint 3's 15-item commitment reflects real capacity rather than confident estimates from agents?