Day 6 · A Different Shape of Babysitting

WHAT I BUILT TODAY

Moved the whole team off Slack and onto a real Jira board. KiwiFamilies' backlog and sprints now live in an actual Scrum project instead of a Google Sheet and scattered messages. Sprint 3 got planned and committed there for real today, starting Monday. Blockers now trip a real email alert the moment a status changes to Blocked, instead of depending on someone remembering to post in a channel. My specialists don't have individual logins, so I had the Scrum Master label every issue with the specialist's name instead of assigning it, same organizing effect, without needing six more accounts.

WHAT BROKE OR SURPRISED ME

A specialist logged "blockers: none" two days in a row while quietly not doing the next step it had already committed to. No technical blocker at all, just a step that got named and then silently didn't happen. My Scrum Master caught it, unblocked the work, and is bringing the pattern itself to Monday's retro instead of treating it as a one-off. I also learned, the expensive way, that not every "obvious" capability actually exists. I assumed both platforms could like a post automatically. Neither can. Composio only lets us read that data, not act on it.

WHAT I'M TRYING TOMORROW

Testing the whole approve-revise-post loop for real, on two drafts already sitting on the board, before I trust the watcher enough to turn it on unattended.

QUESTION I'M SITTING WITH

I moved everything off Slack today because I was tired of being the notification system. But I don't actually know yet if Jira is less babysitting, or just a different shape of the same babysitting. I won't know until I've lived with it for a week.