Agile in a Waterfall Culture Is a Trust Problem First
The first time I suggested a retrospective to a team that had never run one, I learned something no Agile course had taught me. The objection was not to me, and it was not really to retros. It was a whole way of working telling me, politely, that this looked like ceremony for its own sake. That happened on one of the high-visibility priority projects, where I was Senior Product Owner. The aim was to give NSW real-time visibility of housing development, tracking residential construction from planning approval through to occupation. Data was fragmented across departments, and councils, utilities and emergency services were working from incomplete information. The delivery setting was about as far from a startup as you can get: three organisations (2- government departments and one overseas digitisation private partner), legacy systems, heavy regulation and a team based in Bathurst with a long history of waterfall delivery. Why the textbook version failed I started by introducing Agi...