Adopting Agile - Building an Agile Culture
Reedy Feggins 120000A43D Visits (9760)
When software organizations talk about “Going Agile”, they often mean they are adopting a set of agile practices, such as Scrum or XP practices. While this approach does help teach teams the mechanics of agile, this often lead to poorly executed implementations or "Agile-Fall".
Many organizations fail to graphs that a “A move toward Agile implies that your organization is making a cultural transformation to embrace the Agile values and principles and put them into action.”
Adapting an organization's culture is effectively a change management effort. While the business benefits are often large, changing a culture is hard! People often underestimate the difficulties related to changing the existing customer within their organization. Adopting agile methods can cause conflicts. This paradigm shift may not be accepted by team members or some team members may not have skills / experience to use new development methods, such as pair programming or test driven development (TDD), and therefore reject agile as not including them in.
Over the last 8 years as an Agile Coach, I have assisted many organizations successfully adopt agile practices. In most cases, the three critical success factors that these organizations shared were:
Finally in many of the successful cases, I have seen companies assign a member of senior management as the change leader and partner with an experienced Agile Coach help with change management issues. This approach has the advantage of demonstrating the organization is committed to a change, leading by example, and ensuring the organization change issues are identified and managed.