Continuing from part 1 of this 2 part series, here are some additional questions based on observed failure patterns which when discussed up front lead to creating agreements, building trust and setting the stage for a successful agile adoption:
Beyond Process Change – Agile is beyond processes. Are we open to changing our practices, mindset, culture, and structures? Most people have a perception that agile is only limited to process change. While the adoption does lead to process improvements but a big part of the improvements needs change across mindset, culture, and structures. To experience the impact of agility, organizations have to be open to changes associated with processes, people, practices, leadership styles, structures, safety, relationships and much more. This is precisely why an incremental approach to agile adoption becomes critical to making the adoption successful.
A common approach to agility that is a recipe for failure is a leader asking the whole organization to adopt agile without a clear understanding of “why”, leading to a siloed local optimization across various functions of the organization with the focus on survival and risk mitigation.
Agile Adoption Strategy and Roadmap – How do you want to roll out the adoption of agile? “All aboard the fail boat”. Because of the reasons mentioned earlier and how agile adoption demands change across multiple aspects in the organization, it becomes imperative that the approach to adopt agile is understood. While a big bang approach is not ideal, organizations might still have reason to pursue the approach which should be analyzed and discussed up front.
Measuring Success – How do you plan to measure success with agile? Once the vision for agile adoption has been established and understood, the next step is to create agreement on how progress towards the vision will be measured. Many aspects contribute to measuring success with agile but most organizations look at agile as a way to get things done faster. While that may be achievable, it will not be possible without effective leadership, business engagement and alignment across leadership, business, and engineering.
Measuring success with agile includes measuring leading measures (team or projects metrics), which when improved should lead to improvements in the lagging metrics (customer satisfaction or increase in revenue etc…). Both engineering/team and business metrics should be accounted for to measure success.
Commitment to Change – Are you willing to have an engaged workforce to impact change? Agile adoption needs a committed workforce that understands the principles of agility and is able to influence change is achieve the vision and objectives of the adoption. This includes organization leaders, senior and middle management, down to the team members. Lack of such commitment results in a conflict of interest for people engaged in the adoption. Additionally, lack of commitment is also a form a resistance which should be discussed and addressed.
Comfortable Being Vulnerable and make Uncomfortable Changes – Are you comfortable with exposing problems, being vulnerable and potential temporary slow down? The biggest reality associated with agile adoption is the fact that it exposes problems before they can be fixed. This can make people at different level very uncomfortable and exhibit behavior which impedes a successful agile adoption. Additionally, changes in multiple levels (roles, people, practices, processes etc…) may also cause a temporary slow down in the amount of work or value that can be produced.
In cases where the environment is not suitable for exposing problems and slow down, there might be a tendency to pursue the change without the commitment of making it successful. These expectations should be set up front and the data may also be used to help decision making about selecting the right products/initiatives/teams for adoption.
Wrap up – Agile adoption in most organizations is taking place for some nonconvincing reasons including “because the new CIO wants it” or because the competition is doing it. While these reasons will not go away, the leaders driving adoption or the consultants impacting the change should ensure that these difficult questions are asked and the emerging data used to assess readiness and willingness to be agile.