Assessing Your Organisational Agility
Post Statistics
This post has 696 words.
This post has 4375 characters.
This post will take about 3 minute(s) to read.
Agility is the ability to deliver customer-centered changes, products or increment of work as quickly as possible. It is responding to change and bringing customer centered creativity to the market. It is meeting a need, a culture, mindset and a way of working
Organizational agility simply refers to the adoption of customer-centered delivery techniques from ‘top-down’. Agility is a mindset, a way of working, a different paradigm that is achievable through practice, doing and continuously doing.
The pillars of agile should drive any initiation of agile practices in any organisation. These are Transparency, Adaption and Inspection
Company Vision and strategy
In understanding your organisational vision and strategy, the following questions have to be answered. A discovery of your culture, behaviours and respond to change needs to be assessed, documented and discussed
- What to this company is the goal of improving agility? Why an agile route?
- What are your organizational goals and how does the role you’re trying to fill expected to help to achieve those goals?
- What key results would you expect to happen?
- Who is currently involved with this effort?
- Does management fully support these efforts?
- Who determines your product strategy?
- What are the product and company goals for this year, how do they connect?
- Are company goals being met or on track?
- Is the present culture enabling agility.
- What strategies do you have in place to manage change and resistance to the same.
Customer collaboration
Customers are key to your profit and growth. Developing a continuous relationship with your customers will move you forward as a business
- How involved are the business and stakeholders/customers in product development?
- How are end-users being involved in UAT and others?
- Do you have a fully detailed knowledge of your end-users
Measurements
- Are you measuring impact/value? If yes, how? If no, what are you measuring?
- Do you ever go back to existing features? to see how they perform?
- Do you measure team performance? How?
- What do you expect of me? What is the measurement of my success?
Your Teams
- Are teams trusted to manage their own work/sprint?
- Is there a general trust in people and teams?
- Can teams change the way they work? What would be the limit?
- Do teams have clear goals?
- Are team goals generally being met?
- How are teams created?
- Can each team fully independently get work from todo to done?
- Who decides when something is done?
- How often does extra stress/panic/disruption of work occur?
Technological Solutions
- Do you employ continuous integration or comparable techniques?
- What automated tests do you use?
- What other tests do you use?
- How hard is it to release a change?
- Do developers enjoy the current tech stack?
Agile approaches
- Are you using any frameworks or methodology? Fully? Hybrid? Why?
- How do you determine the right framework or methodology?
Community input
– How do they make decisions? E.g. Is it the highest person in hierarchy vs the expert vs the engagement of impacted
– What is the change model in their heads? E.g. is it A –> B defined process with metrics, sticks, and carrots OR a journey without defined end, but checks for direction and correction course (metrics, carrots, and sticks still) OR is it a model which recognizes personal perspectives and stages of change.
– What they think is a role of management? E.g. managing people, assigning work and controlling work (Tailorism) vs Developing people, servant leadership, changing organisation (e.g. through system thinking, theory of constraints).
“Why do want to implement the Agile way of working and change the organisation to the Agile mindset”
“How will the top of the organisation support/propagate this change?”
“Are they willing to be coached too?”
“How many mandates do I get?”
“Are people going to be or are they Agile trained?”
Can you give an example of non-agile patterns or behaviors in your organization that you want to change, reduce or eliminate?
What is your definition of an Agile Mindset?
Why do you love working here?
Can you talk me through how a piece of code goes through from development to production?
Do devs work directly with customers or do all customer interactions go through the PO?
Agility is the ability to deliver customer centered changes, products or increment of work as quickly as possible.
Organisational agility simply refers to the adoption of customer centered delivery techniques from ‘top down’. Agility is a mindset, a way of working, a different paradigm which is achievable through practice, doing ad continously doing.
The pillars of agile should drive any initiation of agile practices in any organisation. These are Transparency, Adaption and Inspection
Company vision and strategy
- What to this company is the goal of improving agility? Why agile?
- What are the organisational goals and how does the role you’re trying to fill is expected to help to achieve those goals? What key results would you expect to happen?
- Who is currently involved with this effort?
- Does management fully support these efforts?
- Who determines product strategy?
- What are the product and company goals for this year, how do they connect?
- Are company goals being met or on track?
Customer collaboration
- How involved are the business and stakeholders in product development?
- How are end-users being involved?
Measurements
- Are you measuring impact / value? If yes, how? If no, what are you measuring?
- Do you ever go back to existing features to see how they perform?
- Do you measure team performance? How?
- What do you expect of me? What is the measurement of my success?
Teams
- Are teams trusted to manage their own work / sprint?
- General trust in people and teams?
- Can teams change the way they work? What would be the limit?
- Do teams have clear goals?
- Are team goals generally being met?
- How are teams created?
- Can each team fully independently get work from todo to done?
- Who decides when something is done?
- How often does extra stress / panic / disruption of work occur?
- Do team members pair up in doing work?
Tech
- Do you employ continuous integration or comparable techniques?
- What automated tests do you use?
- What other tests do you use?
- How hard is it to release a change?
- Do developers enjoy the current tech stack?
Agile approaches
- Are you using any frameworks or methodology? Fully?
Community input
– How do they make decisions? E.g. Is it the highest person in hierarchy vs the expert vs the engagement of impacted
– What is the change model in their heads? E.g. is it A –> B defined process with metrics, sticks and carrots OR a journey without defined end, but checks for direction and correction course (metrics, carrots and sticks still) OR is it a model which recognises personal perspectives and stages of change.
– What they think is a role of management? E.g. managing people, assigning work and controlling work (Tailorism) vs Developing people, servant leadership, changing organisation (e.g. through system thinking, theory of constraints).
“Why do want to implement the Agile way of working and change the organisation to the Agile mindset”
“How will the top of the organisation support/propagate this change?”
“Are they willing to be coached too?”
“How much mandate do I get?”
“Are people going to be or are they Agile trained?”
Can you give an example of non-agile patterns or behaviours in your organisation that you want to change, reduce or eliminate?
What is your definition of an Agile Mindset?
Why do you love working here?
Can you talk me through how a piece of code goes through from development to production?
Do devs work directly with customers or do all customer interactions go through the PO?