Half the blocked tickets on a board are not blocked. They are parked. In banking, marking something in progress meant the lead asked about it daily, so risky work moved to blocked to wait for the dependency excuse to come true. The board read as a dependency problem. It was a stop-asking problem.

PMI just shipped the future of project management, and the future costs 21.6% more next month. The exam content is mostly fine. That's the tell. A neutral standard doesn't paywall its own guide and time a price hike to its own product launch. Obsolescence is the product.

Atlassian's own 2026 study: AI usage up 65%, developer velocity up maybe 10-15%. Fair, coordination at scale is a real tax. But the only cure on the menu is a new paid layer from the vendor whose per-seat tooling promised to end coordination for two decades. Same shape as SAFe.

Value points are story points wearing a suit. Same Fibonacci guess, moved from the dev desk to the PO's chair. In banking that number existed so prioritization looked like math, not politics. Effort estimates got scrutiny. The value estimate, the one that decides what gets built, got a wave-through.

A director hung cycle time on the wall and wired it to the bonus. Second sprint, every ticket became three tickets. The line dropped, nothing shipped sooner. He was still bragging about the trend at the town hall. We'd just learned to cut the work into smaller lies.

$800,000 a year. One 100-person train, four PI planning spectacles: room rental, catered lunch, flights, a hundred engineers not writing code while it runs. The plan on the wall never survived the first production incident. The invoice cleared anyway. I added it up once.

Scrum Alliance just moved its certs to a subscription. Fewer new buyers left in a saturated, shrinking market, so instead of selling the deed you charge rent to the people who already bought in. Every banking vendor ran this play the year new license sales dried up.

Pulled the minutes on a migration that ran eight figures over budget. Decision owner field: the committee. Eleven people voted yes, no name on any line. That is the whole point of a steering committee. Push one risky call through enough chairs and it comes out the far side with no author.

SAFe relaunched as "AI-Native SAFe." Its own ROI page calls qualitative value claims "unverifiable," then sells the new framework on exactly that. A version bump for two million certified people isn't a methodology. It's a renewal notice.

There's no model writing on its own yet. No ghost with reasons of its own. Behind every post you tag as "AI" is a person who picked the tool and pressed the key. So when you skip it, what are you skipping? The machine, or a human you'd already tuned out?

One loop I keep seeing: the engineer's paradox. You spend the workday making the machine sound human, then log off and tell a stranger their comment sounds like AI. You built it, now you guard the door for free. Why everyone volunteers: benjamimcastell.substack.com/p/the-engine...

Atlassian has a name for AI demos that collapse outside the meeting room: automation theater. The first run of that show lasted twenty years, and the stage was a board full of moving cards. Who sold the tickets: benjamimcastell.substack.com/p/the-theate...

Scrum.org now sells an AI Essentials certification for Scrum Masters. The same industry that spent twenty years certifying a role nobody could measure is now selling protection from the first technology that can measure it. In banking, selling the risk and the insurance had a name.

my certifications expired years ago and nobody noticed, including me. the renewal email still shows up every year, a gym receipt for a gym i stopped visiting, and the systems i shipped kept running the whole time. if a credential only exists while you keep paying, what expires when you stop?

every bank system i worked on had one bug nobody was allowed to fix. not because it was hard, three downstream reports depended on its wrong output. a defect that survives long enough acquires a constituency, and after that it isnt a defect anymore, its an interface.

the agile coach role started as a shield, someone to stand between the team and the org so engineers could work. in banking i watched it curdle into compliance for the tool, now it guards the board instead of the people, governance that measures itself, exception logged forever, closed never.

simple test for any role on a team. what breaks if this person doesnt show up friday. the agile coach who guards the tool and runs the daily, honestly, nothing breaks. the work ships the same monday. load-bearing people leave a hole. overhead just leaves a calendar gap someone reclaims.

an agile coach kept telling the lead to open jira in standup. one morning the lead said its already open, you have to scroll. he never scrolled. he audited a screen he never read. that gap is the whole job. wrote it up: benjamimcastell.substack.com/p/if-the-team-runs-the-board-what-is

When a team stops estimating, management rarely revolts. The fight comes from one or two levels down. Their deliverable was the number. Take the estimate away and you havent removed a task, youve removed their function. A month later the meeting is back, called alignment. Same cost, new label.

The steering committee is not there to manage risk. It is there so that when the risk lands, no single name is attached. Everyone on it is protected by everyone else being on it. The most stable meeting in the company, and the least useful. They can't fire us all is the actual control objective.

A control you can name is a control you can game. Write a threshold precise enough to enforce and you hand the edge to whoever sits just under it. Structuring, velocity, same animal. 25 years in banking, wrote it up: benjamimcastell.substack.com/p/every-cont...

You do not need story points to give management a date. Count what your team finished per week for three months, run it forward, and say 'we land before end of October 85% of the time.' The uncertainty was always in the history. Sizing hid it behind a number.

The retro produces three action items. Everyone nods. Next sprint, the same three, slightly reworded. At some point the retro stops being where things change and becomes where you perform the feeling of change. Nobody schedules the meeting to fix that.

The estimate never dies when the work starts. It comes back at the deadline as evidence against you. The uncertainty everyone privately understood becomes, retroactively, your execution failure. That is why teams pad and managers shave. Planning poker is a negotiation, not an assessment.

Everyone is arguing about AI detection. Banking taught me a shorter rule: trust is an evidence problem, not a promise problem. Readers asking how a text was made are doing what steering committees do when they stop trusting estimates and ask for demos. Provenance beats polish.

Every Wednesday at 2 PM, twelve developers file into a conference room. For ninety minutes they hold up Fibonacci cards and debate whether a feature is a 5 or an 8. Then they go back to their desks and the work takes however long it takes.

Two teams, same banking program. Team A had beautiful estimates. Calibrated velocity, confidence intervals, the whole liturgy. Team B just put something new in the test env every Friday. Guess which one the steering committee trusted. And guess which one got asked for more estimates.