2 Comments
User's avatar
Agile Chris's avatar

Hi Jurgen, some sharp thinking here!

Your move to reject fixed cadences is a powerful challenge to the ‘standard’ way of working. I agree, when the work shifts rapidly, a team needs the freedom to respond immediately rather than waiting for a calendar event to catch up.

However, we shouldn't discard the shared pulse entirely. Just as you share insights to keep your community aligned, teams need a common rhythm to stay in sync. A fluid method is most effective when it tunes an internal heartbeat that provides simplicity, protecting the team from being tossed about by every external signal.

Regarding "the need for speed": while AI allows us to accelerate delivery, our core purpose must remain the driver. Speed without a clear 'why' eventually leads to burnout or a loss of direction. The goal isn't just infinite velocity, but viability—using a fluid pace to stay responsive while ensuring the team’s mission remains the primary governor of that speed.

Overall, great food for thought on moving from managing time-boxes to mastering the actual flow of work.

Jurgen Appelo's avatar

Agreed on each point.

There is a human need for cadence, and also for rest and time off.

Also, not every user experience is improved by delivering faster. There is value in scarcity and anticipation.