Patterns for Agile Change: Blog 6, People Tools

-

Opening Story: 
The company has been adopting agile practices for a while in a few different areas. We’ve had a few people in to help us with the change, but we seem to regress when key people or sponsors leave, or when we cannot fund an Agile coach or change agent. Any behaviour advances we make seem transient and are not sustained over the longer term. The behaviour of individuals and general culture of the company seems to revert to 'norm' rather than to continue on our agile vision. 

Summary:
Behaviour follows structure, (i.e. our behaviour is strongly influenced by the working environment, structures, policies & governance of the company) and so the structures within the company (e.g. governance, policies, practices) need to change in order to provide an environment where new behaviour can thrive.  

Context:
You are part of a team of people passionate about Agile, wanting to ensure it becomes a long-term part of how the company works, but are struggling to embed the changes into the company.

Problem:
Unable to embed the desired Agile mindset, behaviour and culture into the business for the sustainable long-term. It is a challenge to sustainably improve and grow the right behaviour across the business. 

Forces:
Executive & leadership behaviour
Existing cultural norms
HR Law
Existing recognition & reward systems
Existing organisation structures
Existing roles & responsibilities

Essence of the Solution:
Identify, adjust and exploit the existing people tools within the business to drive the change and embed the change into the fabric of the company.

More about the Solution:
The HR policies and structures of a company are integral to the DNA of the company. Reward mechanisms (pay, bonuses, appraisals), recognition systems (employee awards, promotion structures), communication channels, organisational structure, role definitions, competency frameworks, education, personal development and training all contribute to define how people work and interact within the company.
If you want to embed Agile roles, practices and behaviours within the company, you have to use the ‘People Tools’. 
Identify all the ‘tools’ the company uses to organise its workforce, encourage and motivate people, and recruit, develop and retain people, and then, based on the content from the 'Murmuration' pattern, adjust and embed Agile artifacts into these ‘People Tools’.

Related patterns: Murmuration, Call a CoP, 2 Structures

Resulting Context:
Then the reward & recognition systems and learning & development frameworks have been adjusted to reward Agile behaviour, Agile roles are the default roles within the company, and the organisational structure has been changed to align to Scrum teams and Product ownership, over time (12-18 months) the entire behaviour and ultimately culture shifts to the new dynamic.
It is essential that the executive and leadership teams, model to new behaviours and ensure they encourage the new behaviours by providing a working environment that recognises, rewards and nurtures those behaviours.

Known Uses:
SME Software Department c30 FTE
Financial Services Software Company c220 FTE
Online Digital Company c200 FTE

Comments

Post a Comment

Popular posts from this blog

Starting Out

-
I left Conchango and started in my new role at the beginning of March this year. I'd been working as Scrum Master ( www.controlchaos.com ) with the likes of Howard van Rooijen ( http://blogs.conchango.com/howardvanrooijen/default.aspx ) and Ian Shimmings ( http://blogs.conchango.com/ianshimmings/default.aspx ), and fundamentally wanted to take agile practices to an organisational level. Moving a development team of 25 from traditional methods to agile practices is an exercise in change management. But even the word change management implies a clear direction, manipulation or cohersion and "management" of the process. I knew straight away that in order to encourage adoption of agile practices I would need to capture hearts and minds rather than direct a change programme. My previous blogs discuss transformational leadership and emotional intelligence, and I recognised that this is how I want to lead development. Even writing (I want to lead development) seems to go against...
Read more

Breaking the Iron Triangle: Project Manager v Scrum Master

-
Image
As a PM my general approach to initiating projects has been to build a Project Initiation Document (PID – Prince). A PID details the project objectives, initial scope, organisational structure, roles & responsibilities, deliverables, project processes (lines of communications, risk management, issue management, change control), plans, costs and timelines. And starting an agile project I would still identify most of the above and ensure it is clearly communicated to all stakeholders. But… I have learnt that adopting a scrum approach changes two fundamental things for a project manager: · The Iron Triangle · The Role of Project Manager The iron triangle of cost, time and scope (or quality) is typically the responsibility of the project manager to manage. Hopefully tolerance levels have been set for each element of the triangle, and if the tolerance level is about to be breached or is broken, the project manager escalates their issues to the project board or steering group. Previously...
Read more

Lost in Translation

-
Enterprise Scrum - Tactics for Implementing Agile Practices If you are implementing agile practices, methodologies and organisational changes within the company without full executive support, you are probably facing an uphill struggle. I was watching a TV documentary on the space race the other day, and one of the interviewees stated that in today's world nobody takes any real risk... This is fundamentally the problem you face, agile is perceived as high risk and difficult to manage. From a traditional management perspective, it is! Agile is about recognising there is a limit to control, that all things are not predictable, and that although we have clear objectives and a general direction, the detail of functionality and architecture is unknown at the beginning of a project. Managers need to learn an empirical approach to work and ensure that feedback loops and frequent communication are embedded within the fabric of the organisation. So with so much risk... cost, direction, cont...
Read more