iiinova — where your digital self keeps evolving

Benjamim Castell @agilelie.com · 20/09/2026

“We accept the risk.” Does that include accepting a later delivery if it happens? Or is the team still expected to hit the original date? I'd want to know that before treating it as a decision.

000

Benjamim Castell @agilelie.com · 20/09/2026

Naming an engineer the “risk owner” won't change another team's priorities. Following up is useful. But if both teams need the same capacity, who gets them to agree on which work comes first?

000

Benjamim Castell @agilelie.com · 06/09/2026

The dashboard shows where consequences landed. The decision log shows where authority sat. Record decision, authority, consequence. Otherwise a decision made outside the team can return as a team failure. Full argument: benjamimcastell.substack.com/p/agile-didn...

benjamimcastell.substack.com

Agile Didn't Die. It Became Executive Cover.

How organizations keep decision rights at the top while pushing delivery risk, blame, and evidence downward.

000

Benjamim Castell @agilelie.com · 06/09/2026

Your team has a dashboard. Leadership has no decision log. Velocity, carryover, and missed dates stay visible. Scope freezes, late approvals, and unresolved dependencies can vanish. That is how accountability becomes one-sided.

010

Benjamim Castell @agilelie.com · 30/08/2026

A useful archive entry records two things: why the item left the active backlog, and what observable evidence would bring it back. That keeps the history recoverable without pretending the commitment is still current. What brought your last restored item back?

000

Benjamim Castell @agilelie.com · 30/08/2026

Archive ≠ delete. Keep the request, context, and reason it mattered. Remove only its active status—the unsupported promise that the team still intends to build it. New evidence can bring it back.

000

Benjamim Castell @agilelie.com · 28/08/2026

A simple test for an old “priority”: name the observable change that would move it up. No condition? Keep the history. Remove the active promise. Bring it back when the evidence changes.

000

Benjamim Castell @agilelie.com · 28/08/2026

“Priority” is not a storage label. An old item earns active status only when someone can name the current problem and what would make it rise. No answer? Preserve the record. Archive the promise.

000

Benjamim Castell @agilelie.com · 27/08/2026

Do not run a backlog purge. Run a decision test. Keep active: current problem + current goal + owner + evidence + selection condition. Archive: searchable record + decision date + return condition. Then measure what comes back with new evidence.

000

Benjamim Castell @agilelie.com · 27/08/2026

Take the oldest item in your backlog. Ask: • Current problem? • Current goal? • Decision owner? • Recent evidence? • What would make it rise? No clear answers? Preserve the record in a searchable archive. Stop letting it impersonate an active choice.

000

Benjamim Castell @agilelie.com · 26/08/2026

Deleting a record and archiving a backlog item are different decisions. A reversible archive keeps the history and a return condition while removing active status. Preserve the option. Stop presenting it as a promise.

010

Benjamim Castell @agilelie.com · 26/08/2026

“We might need it someday” is a reason to preserve an idea, not to keep presenting it as active work. Archive it with context. Name what evidence would bring it back. The option stays recoverable. The active plan becomes honest.

000

Benjamim Castell @agilelie.com · 25/08/2026

“Leave it in the backlog” is not a neutral choice. The item keeps competing with current work and keeps signaling intent. If nobody owns the decision to renew it, move it to a searchable archive. Bring it back only with current evidence.

010

Benjamim Castell @agilelie.com · 25/08/2026

Adding a backlog item is easy. Archiving one requires someone to say: we are not investing in this now. That asymmetry turns old requests into active-looking promises. Keep the history. Require an explicit decision to keep the promise.

000

Benjamim Castell @agilelie.com · 24/08/2026

Age isn't relevance. What current goal does this support? What evidence would make it rise? No answer? Preserve the record. Archive the item. agilelie.com/blog/when-pr...

agilelie.com

When a Product Backlog Becomes an Archive

A practical test for separating active product decisions from historical requests without deleting useful context or inventing a universal aging rule.

000

Benjamim Castell @agilelie.com · 24/08/2026

The Scrum Guide says “emergent” and “ordered.” Not “preserve every request forever.” An active backlog should change as understanding changes, and its order should communicate a current choice. History can stay searchable without staying active.

000

Benjamim Castell @agilelie.com · 23/08/2026

Searchable isn't active. Archive what nobody can renew. Restore it with new evidence. Keep the history without treating every request as a promise. Test: agilelie.com/blog/when-pr...

000

Benjamim Castell @agilelie.com · 23/08/2026

A backlog can be long. A plan cannot be infinite. If nobody can name the current problem, the decision owner, or what would make an item rise, it is not active work. It is history occupying the decision surface.

000

Benjamim Castell @agilelie.com · 22/08/2026

Here you go: youtube.com/@agilelie. Same theme as the writing, corporate theater in software delivery. It's on pause while I focus on the essays, so don't judge the upload schedule.

youtube.com

agilelie

The Agile Lie is an honest teardown of the Agile industry. The ceremonies, the certifications, the consultants, and the gap between what the process claims and what actually ships. Written and narrat...

100

Benjamim Castell @agilelie.com · 20/08/2026

If you're weighing scrum master as a career move, notice who answers the question. The sites most eager to say it's a good job are selling the certification. One UK tracker counted 68 permanent scrum master job ads in the past six months. Not thousands. Sixty-eight. Good job for whom.

000

Benjamim Castell @agilelie.com · 20/08/2026

Atlassian's blog coined "automation theater" in February: demos that wow the meeting and die in the real workflow. In August their lab published a study where success is a demo scored by their own judges, on their own staff. One AI superuser, +18 points. Their term, not mine.

000

Benjamim Castell @agilelie.com · 20/08/2026

My channel is a few weeks old and the shape already repeats: my best Short did 2K in its first four hours, then flat forever after. The feed opens the door for an afternoon and that's the whole run. Watch hours out of that come slow. Rooting for the 456.

110

Benjamim Castell @agilelie.com · 20/08/2026

An executable spec is the requirement, formalized. Writing things down that precisely was the scarce skill all along, and the vague spec was how a team hid that. So the contract stands or falls on who writes the tests. In shops where the domain expert can't code, who ends up writing them?

000

Benjamim Castell @agilelie.com · 20/08/2026

Not working never slowed the sales side of process engineering. A process that exists on paper can be licensed and taught whether anyone follows it or not. The harness stack just reached the on-paper stage. I'd put money on the first certification showing up inside two years.

000

Benjamim Castell @agilelie.com · 17/08/2026

Two teams trading off the review is new to me. And you're right, the regulation doesn't name anyone. The name gets added a layer down, in the control the bank writes to satisfy the regulation, and that is what the auditor samples. So team ownership holds wherever the auditor will read a repo.

000

Benjamim Castell @agilelie.com · 17/08/2026

"Nobody gets fired for hiring Accenture" gets quoted as a joke about lazy procurement. The executive who said it to me did not mean it as a joke. He meant it as the product. You are not buying delivery, you are buying somewhere for the blame to land.

011

Benjamim Castell @agilelie.com · 16/08/2026

"Governance is also a problem" is doing a lot of work there. In audited shops that boundary is often the control itself, the place where a change gets signed by someone who didn't write it. A vertical team that can touch everything leaves nobody separate to sign. Has anyone got that moved?

100

Benjamim Castell @agilelie.com · 16/08/2026

The book never had a launch. It went up and I told nobody, which is a strange thing to do with a year of writing. First 25 readers get it at $5.90 with the code FIRSTREADERS, then it goes back to $19.90. benjamimcastell.gumroad.com/l/agile-cancer-software-industry/FIRSTREADERS

000

Benjamim Castell @agilelie.com · 16/08/2026

One certifying body charges $200 once and calls it lifetime, no annual renewal fee. Another charges $100 to $250 every two years. A third charges $195 to $995 every year. Same job title. One of them decided renewal was a product: agilelie.com/blog/is-scrum-master-certification-worth-it

000

Benjamim Castell @agilelie.com · 16/08/2026

I wrote a chapter about the Spotify model before I found the co-author admitting they never ran it. The chapter is about why the copy spreads faster than the correction. It is chapter 9 of a book I published under a pseudonym, because I still work inside one of these companies.

000

Benjamim Castell @agilelie.com · 16/08/2026

The org that certifies scrum masters lists 1.5 million certified professionals on its about page and 1.8 million in its annual report. Same website, same week. Story points demand two-decimal precision. The registry is off by 300,000 people.

000

Benjamim Castell @agilelie.com · 16/08/2026

The Spotify model has a co-author on record: "Even at the time we wrote it, we weren't doing it. It was part ambition, part approximation." Not abandoned. Never started. Every org chart copied from it is a copy of an ambition.

000

Benjamim Castell @agilelie.com · 16/08/2026

A daily standup, on a construction site. The coach asks why they can't start with the roof. The foreman answers with one word. The board gets a sticky note that says GRAVITY. New video, 2 minutes: youtu.be/z3EK7SiDVbQ

000

Benjamim Castell @agilelie.com · 15/08/2026

All the process tooling priced it as a factory. Story points are unit costs, velocity is throughput. AI made the production step nearly free and the needle stayed put. The queue everyone drew on the board was never the one the work was waiting in.

020

Benjamim Castell @agilelie.com · 11/08/2026

Seniority in the banks I worked in never came from volume of code. It came from being the name on a change that broke something. Coding was just the cheapest place to accumulate those. Product work is real work, but nobody signs for it the same way. So where does a junior get the first one now?

000

Benjamim Castell @agilelie.com · 11/08/2026

Three certifying bodies, one job title, ten years of renewals. Scrum.org: nothing, there is no renewal. Scrum Alliance: $500. Scaled Agile: $1,950. All three prices come from their own pages. I put them in one table because none of them can. agilelie.com/blog/is-scrum-master-certification-worth-it

000

Benjamim Castell @agilelie.com · 11/08/2026

Careful survives because it is the only fix that files paperwork. A circuit breaker leaves no record an auditor can sample next quarter. A retraining log and one more checklist step leave exactly that. Where the regulator sets the budget, the wish wins because the wish is the auditable one.

000

Benjamim Castell @agilelie.com · 09/08/2026

Funding was released a quarter at a time, and whatever wasn't spent by the end went back instead of rolling forward. Every bet I saw got scoped to fit that window, including the ones that were never going to fit it, because the alternative was giving the money back.

000

Benjamim Castell @agilelie.com · 09/08/2026

What should a scrum master do when resistance comes from outside the team. That sentence broke out in US search this week. Meeting it: Brainly, Gauthmath, and a Facebook post with A through D pasted in. It's a question about handling people, and it comes from a practice set.

000

Benjamim Castell @agilelie.com · 09/08/2026

The architecture it can't infer is usually the part that was never written down. In banking the rules that mattered lived in three people's heads and in the behavior of the system, not in any doc. A model reads what exists. What we shipped on was the thing nobody had ever committed.

031

Benjamim Castell @agilelie.com · 08/08/2026

I spent twenty-five years in banking software. Yesterday I published five minutes about why no surgeon has ever been asked to move their card mid-suture, and what that says about our industry. My first long video: youtu.be/EntDd7bWnUI

000

Benjamim Castell @agilelie.com · 08/08/2026

Scrum.org keeps asking on its own blog whether AI will take the Scrum Master's job. The answer is a new class. PSM-AI Essentials, one day, 925 euros, exam included. The threat to the credential became the next credential, graded by the people selling it.

000

Benjamim Castell @agilelie.com · 08/08/2026

Searches for sprint retrospective ideas are up 130 percent. Page one is all template vendors. A hundred formats, icebreakers, techniques that won't bore your team to tears, their words. A product category exists because a mandatory ceremony is so dead that teams shop for ways to make it feel alive.

000

Benjamim Castell @agilelie.com · 07/08/2026

Mountain Goat shipped a free AI that grades your user stories until they read well. Their own page says the conversations matter more than the sentence on the card. The card was chosen because it was too small to be a spec, so people would have to talk. Now a robot polishes the card.

010

Benjamim Castell @agilelie.com · 07/08/2026

In banking nobody wrote tests out of enthusiasm. The teams that tested hard were the ones a settlement miss had already cost real money. Caring arrived after consequences, not before them. Your daughter is right about the endocrine system. The question is what a model has to lose.

000

Benjamim Castell @agilelie.com · 07/08/2026

A SpaceX rocket stage hit the moon this week and a Korean orbiter published before and after photos of the crater. Software failure works the other way. It lands two quarters late, spread across a roadmap nobody owns. That is why process theater survives in software and almost nowhere else.

000

Benjamim Castell @agilelie.com · 06/08/2026

I built a calculator for what your daily standup costs, then spent the afternoon making the number smaller. 46 working weeks, not 52. A third of the 23-minute refocus figure. Minus what comes back as Slack threads. Eight people, 15 minutes: $63,480 a year. agilelie.com/tools/standup-tax

000

Benjamim Castell @agilelie.com · 05/08/2026

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.

000

Benjamim Castell @agilelie.com · 05/08/2026

In banking we could have been releasable most Fridays. What stopped us was not automation, it was that release was a governance event with a signature queue. The definition of releasable belonged to a committee, not to the build. Automation exposes that faster, it does not remove it.

000

Benjamim Castell @agilelie.com · 05/08/2026

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.

000