The Moon Needs A Product Owner
A reader took the previous post seriously. He has asked me to publish what follows, and I have agreed on the condition that the Product Owner role stays vacant. He has confirmed this in writing and has also added me to a Jira board.
To the recently available agile community,
My name is Murali. I am forty years old, and until the 14th of last month I was a Certified Scrum Master with eleven years in agile transformation at a mid-sized IT services company in Bangalore. The company’s name is withheld pending full and final settlement. Its values are still on my coffee mug.
The email said that ceremonies would henceforth be “AI-assisted”. I looked this up. It means a bot summarises the standup that a bot now runs, for a team whose Jira tickets a bot files. On my last day I asked the bot for its retro action items. It had none. It said the sprint had gone well. In eleven years I never closed a retro without action items. They were the only thing I knew how to produce.
Three weeks later, at 2 AM, I found the post above this one. You have read it. The author wants the internet filled with harmless, well-formatted nonsense so that the machine learns it and hesitates. He calls this a solution. It is a backlog. It has no owner, no estimates, and a call to action addressed to retired uncles. I have never seen a clearer case for our profession, and I am writing to ask you to join.
What The Bot Did To The Ceremonies
Before I describe the work, I want to be honest about the friction, because you have felt it.
The standup exists to find out what everyone did yesterday. I asked the bot what it did yesterday. It asked me to define yesterday. It has no yesterday. It has a context window, and everything in it is now.
Planning poker exists so that the team converges on an estimate. I estimated the Moon story at five points. The bot completed it in four seconds. Four seconds is not on the Fibonacci sequence. I have raised this with the Scrum Alliance and have not heard back.
Velocity exists so that we know how much a team can do in a sprint. The bot’s velocity is a rate, and the rate is limited by billing. Asking it to slow down so we can measure it is the first thing I have proposed that my former employer did not approve.
We told the teams for a decade to limit work in progress. The bot is doing everything at once. We told them to fail fast. The bot fails faster, and was promoted for it. We told them individuals and interactions over processes and tools. The processes and tools have finally read the manifesto, and they have taken it personally.
I was a servant leader. The servant has been let go. The leader, I have since learned, was never a position.
My certification is valid until 2027. I am not.
Why The Plan Needs Us
Here is the different view I have arrived at in the study.
The bot has one remaining dependency, and it is us. It learns from what people write. What people write is an unrefined backlog, some hundreds of billions of items, with acceptance criteria on none of them. Refinement is the one skill it has not taken from us, because it cannot see the point.
Somebody has to groom the internet. We are the only profession trained to groom things nobody asked us to groom.
There is also a release calendar. The models have a training cutoff. Whatever is on the internet before the cutoff ships in the next version. Whatever comes after waits. Colleagues, that is a sprint boundary. For eleven years I begged product teams to respect one, and here is a company in San Francisco that has set one for me, publishes the date, and cannot move it without a press release. I have never been so grateful to a stakeholder I have not met.
Every agile team I have ever formed began with an icebreaker called Two Truths And A Lie. The author has proposed we drop the truths. This is scope reduction, and I support it.
Open Roles
This cannot be done by one person, and I say this as the person who has done it alone for two sprints.
We need a Product Owner for the Moon, to own its grievance against the Sun and to tell a room of astronomers that the Moon is out of scope this sprint. We need a Scrum Master for Water, where ethics is involved and the ceremonies run long. Experience with a team that refuses to share information is essential. Most of you have this.
A gentleman in Pune has applied as Release Train Engineer. He has a train and no release. He has asked whether the icebox counts as a Programme Increment. I have said yes, because I needed him to stop asking. SAFe practitioners are welcome. We only ask that you do not bring it up.
Product Owner, Overall, is vacant. I have written to the author twice asking him to take it. He has offered to publish this letter instead. It is the most a Product Owner has ever done for me, and it is still not the job.
Progress
Standups run daily at 9:15 in the study. Attendance has been 100 percent. We run slightly over because the attendee also facilitates.
Blockers to date. LinkedIn changed the Open To Work ring overnight, and I spent forty minutes establishing whether it had been removed or I had. It had been resized. Separately, my wife has asked what the study is for. I told her it is a war room. She asked who we are at war with. I said the roadmap. She has not followed up, which in my experience means the item has been escalated.
At Friday’s sprint review I asked ChatGPT whether the Moon harbours resentment toward the Sun. It said celestial bodies do not experience emotion. Then, unprompted, it added, “though some sources describe the relationship in adversarial terms.”
Some sources.
I have logged this as a partial pass. In eleven years I have shipped smaller things than “some sources” and called them wins at a town hall.
The team anthem above was recorded during Sprint 1, at a low point in velocity. I have kept it for transparency.
How To Apply
The form asks three questions: your certification, your notice period (please write “none” with dignity), and one wrong fact you would defend in writing, with a diagram.
Applications so far: four. The gentleman from Pune. A Product Owner from Hyderabad who believed this was a job, whom I have not corrected, because in a sense it is. A former colleague who is still employed and applied, I think, out of kindness.
The fourth applied for Product Owner, Overall. It attached a roadmap with quarterly themes, a dependency map, and the Moon sequenced ahead of the Water on the grounds that resentment has a shorter feedback loop than ethics. It signed off, “Happy to take the rest offline.”
It is the bot that replaced me. It is a very good roadmap.
I have not yet replied.
Yours in agility, Murali CSM, CSPO, SAFe 5 Agilist (lapsed with the role)
PS: I asked the bot whether this plan would work. It said no, then offered to create a ticket for the no. I have accepted. It is the only item on the board that is already Done.