Implementing Scaled Agile - a though piece

Building on The Scaled Agile Framework- my implementation experience

The Scaled Agile Framework is a framework of a methodology for Agile at Scale. I have seen and worked with it at several companies. Although it is a good guidelines for the ceremonies and basic practices at scale, there are many things that Agile practioners and PMOs need to add to it for a successful implementation.

All implementation projects need a Governance Model to report progress objectively, which includes risks, resource utilization, major milestones, and cost management. The PMO needs to construct a model that measure progress... while the Agile Framework should show delivered value in every sprint and product increment as a working product.

Although the scaled agile process and ceremonies are described in the framework, the actual execution of the ceremonies and the roles will require the Agilist to develop more clarity around them and demonstrate them to others.. Furthermore, the ceremonies have to provide meaning, at the right time. Each ceremony needs to be developed and integrated into the cadence of work at precisely the right time.

Finally, the release train itself has to be comprehensive itself to add meaning to the value delivery. This means that all parties involved in the release are part of PI planning and preparation for the release in a series of parallel sprints. Technical and Functional components of the release, along with the other operational components- including operations, training, and implementation teams should also be involved. Pulling all of these components together is a bit of both art and science. I have more to say on this subject than can fit into this article. So stayed tuned for more !