A team can run the stand-up, keep the board tidy and still have the same piece of work waiting on Friday that was waiting last Friday. The ceremonies are real. The person who needed the thing cannot use it. If you are about to book a workshop on top of that week, the test is whether the day will change that piece of work, or add another meeting in which people talk about it.
The authors of the Agile Manifesto put the test in the principles behind the manifesto. The highest priority is to satisfy the customer through early and continuous delivery of valuable software. Working software is the primary measure of progress. Changing requirements are welcome, even late, because the change is supposed to serve the customer. Business people and developers work together through the project. At regular intervals the team reflects and adjusts. Simplicity, which they describe as maximising the amount of work not done, is one of the principles. Sponsors, developers and users should be able to keep a constant pace.
What the day has to change
Bring one live piece of work a real user is waiting on. A customer, a colleague in another function or a person who has to operate the thing after it ships. The day is worth running when that slice gets smaller, a named business partner agrees to look at it and the team writes down what it will drop so the slice can move. If the proposal cannot name the slice, the partner and the drop, it is a tour of vocabulary.
The reflection in the principles is a tune-up, not a mood. Ask what the team last changed because a user reacted, or because a requirement moved. If the answer is that the board was updated and the plan was not, the ceremonies are recording the stall. A workshop that rehearses the update, and never rehearses the change to the plan, will leave Monday identical.
Constant pace is the principle a busy team skips when the workshop is framed as a push to clear the board. The authors say sponsors, developers and users should be able to keep going indefinitely. A day that adds a ceremony, and leaves the late work where it was, makes the week heavier. Judge the booking by what came off the list.
How a ceremony tour gives itself away
In a weak proposal the facilitator owns the examples. The work on the wall belongs to a fictional team. The argument is about which framework to adopt. Nobody is asked to cut scope on something the organisation is already late on. The follow-up is a poster of roles. You can hear this in the first pass of the agenda. If the hours are named for rituals, and the live work appears only as an optional discussion at the end, you are buying a ceremony.
A useful session is less tidy. The business partner disagrees with the team's guess about what the user needs. Someone defends a task that should be cut, and the room cuts it anyway, with a name next to the cut. The slice that remains is small enough that a user could react to it. Progress, on the manifesto's own terms, is that reaction, not a fuller backlog. Leaders have to stay for the cut. A delegate cannot retire a task their boss still expects.
Collective Campus is building high-performance culture and teams for the AI world. The agile workshop is for a team that already runs the ceremonies and has one live piece of work a user is waiting on. What changes when the meeting stops standing in for the work is in agile without the theatre. What a corporate team should put under test, once the slice is a bet, is in a lean startup workshop for corporate teams. A bet that never ends is the subject of pilot purgatory.
What to bring
Bring the live slice, the name of the user or business partner who will look at it and the list of tasks you are willing to drop. If you cannot point at something you would stop, the workshop has nothing to decide.
