February 4, 2012

BigVisible Blog

Organizational Agility: Beyond Agile Teams

For years, companies and teams have focused on adopting agile at the team level. Team members and ScrumMasters work to improve their sprint planning and collaboration techniques—the things they do on a day-to-day basis to execute work. Product owners, ScrumMasters, and team members also focus heavily on delivering projects—learning how to use a product backlog, do release planning, and deliver more, faster. The problem is, being good at executing Scrum or Kanban is not the goal. Organizational agility is the goal.

Suppose, for example, you reach a point in your agile implementation where teams are delivering and executing in a much more productive and efficient way. That begs the question, are they delivering the right things? Now that teams can deliver faster with better quality, how does an organization leverage these newly acquired super-skills?  [Read more...]

If You Want To Stop Becoming More Agile, Start Focusing on Standards

Change is difficult.  Improving is difficult.   Many managers see improvement and change as temporary things that cause confusion and misdirection until a steady state is achieved and the improvement is completed. They approach change with a model of “unfreeze – change – refreeze”.  Only when things are frozen again – a standard established, a checklist and diagram provided – will workers know what to do, and will it be safe to “roll out” changes to others.

This way of thinking and approach to change may drastically limit the success of your journey to becoming an agile organization.

[Read more...]

Beyond Functional Silos with Communities of Practice

Stop me if you’ve heard this one before… An organization decides to align its operation around business products. It organizes all of its product development into cross-functional teams with each team focused exclusively on one product. The business likes the focus, but soon people start to complain. Functional experts feel isolated and aren’t able to tap into their technical peers who are now isolated in other teams. Common practices and standards become difficult. Functional managers feel left out, as they don’t have much of a role now that their people are permanently assigned to specific business units and are dedicated members of a cross-functional team. Overall, the organization certainly sees advantages to the re-alignment, but they can’t help but feel they are neglecting their institutional knowledge and have reduced some of their technical capacity to solve problems. You might think I’m talking about an Agile development team, but actually I’m talking about Chrysler in the 1990′s when they re-organized their engineering around auto lines. (Wenger et al, Cultivating Communities of Practice 1)

Indeed, the challenges that agile organizations have been facing as they embrace team centric work have actually been confronted by numerous organizations prior to Agile. Automobile companies, professional consultancies, oil companies, and even the world bank have encountered this challenge where their technical experts have become ensconced in cross-functional project silos. Looking at how these organizations have addressed this challenge offers us some interesting insights. The successful organizations didn’t try to bolster their functional silos or build standards groups, but rather they embraced a more informal and organic model for sharing knowledge, solving problems and even making strategic investments: communities of practice.
[Read more...]

Faces of Power in the Organization

Faces of PowerThe lines between political science and organizational culture continue to blur. Those who venture into organizations need to become well versed in the dynamics of power. One such explanation of these dynamics is Steven Lukes’ the “Three Faces of Power”.

Three Faces of Power

1. Decision Making – The power to make and implement decisions

2. Non-Decision Making – The power to set agendas and therefore limit what is even being discussed

3. Shaping Desires – The power to manipulate what people think they want

Lukes’ work is an extension of Max Weber’s Three Types of Authority, in which Lukes argues that Weber only focused on the first face of power, Decision Making.
[Read more...]

A coach’s moral dilemma

A fellow coach recently asked me for my opinion on an ethical dilemma — was it morally right for us to show people a new way of doing things knowing fully well that we were setting the group for eventual disappointment. Disappointment in his case is inevitable and will start setting in as soon as the parent company begins assimilating the subdivision and mandating that the latter operate under the parent organization’s restrictive rules and policies. My simple and somewhat glib answer was that we were doing the right thing by helping people get better and were providing them the wherewithal to make informed decisions about their future career. And, if in the end, the employees were unhappy they could take their knowledge elsewhere to an employer who would value their expertise. [Read more...]

Agile Doesn’t Work For…

Ever run across these guys?  People whose lack of experience or fear of change cause them conjure up all kinds of reasons why agile won’t work for their project?

Let’s bust those myths!

 

Myth: Agile Doesn’t Work for Projects in the Highly Regulated Medical Environment.  (The reason usually given is that FDA regulations require detailed requirements prior to project approval; hence, waterfall.  However, in reality, you can develop in phases, with small incremental sets of requirements and the FDA requires only enough documentation to demonstrate your process.)

Truth: Abbott Labs overcame medical device regulation and stringent Class 3 certification and developed the m2000 Real-time PCR Diagnostics System, a human blood analysis tool, with four agile teams.  Compared to the prior methodology in use, this project resulted in a less cumbersome process, fewer defects, a reduction in costs of 43%, and a reduction in cycle time of 25%.

(Rasmussen, R., Hughes, T., Jenks, J. R., & Skach, J. (2009). Adopting agile in an FDA regulated environment. Proceedings of the Agile 2009 Conference (Agile 2009), Chicago, Illinois, USA, 151-155)

 

Myth: Agile Doesn’t Work in Government

Truth: The FBI overcame a CMMI level 3, ISO 9001, government-mandated document-driven waterfall life cycle and developed the Domestic Terrorist Database & Data Warehouse with three agile teams.  Compared to the prior methodology in use, this project resulted in significant improvements in release planning, developer satisfaction, and a focus on the true goal: “to catch bad guys.” [Read more...]

Top 10 Ways to Help Your Clients

Top 10 Ways to Help Your Clients – adapted for Agile coaches from Edgar Schein’s 10 Consulting Principles

Edgar Schein is a former MIT professor at the Sloan School of Management and author of numerous books on organizational development, the consulting process as well as other subjects. Schein’s work is based on over forty years of consulting experience. He is also generally regarded as the originator of the term ‘organizational culture’.

Schein views the consulting process as essentially a ‘helping’ relationship between the consultant and the client. He gauged each interaction with a client by the degree that the relationship had been helpful and whether or not the client felt helped.

I found Schein’s list of ten tips on creating and maintaining a helpful client relationship to be directly applicable to our work as coaches and essential to helping us create and maintain great relationships with our clients. I have included Schein’s list below along with one additional tip and a bit of personal commentary.

1. Always try to be helpful – Coaches have to know when to help, how to help and learn to see what the client is really asking.
2. Always stay in touch with the current reality – this could be the most important principle because it is really about being mindful. Staying present and aware of what is happening here and now is one of the most fundamental skills that a coach should develop and the key to performing well with all of the other principles listed here.
3. Access your ignorance – asking ourselves what we really know vs. what we think we know is an important exercise for coaches and one that can help keep us grounded and in touch with what is happening now. In other words, question your assumptions.
4. Everything you do is an intervention
5. It is the client who owns the problem and the solution
6. Go with the flow – if you remember principles one through three you should have not trouble with this one
7. Timing is crucial –Finding the proper moment to bring up a sensitive subject is crucial to building and maintaining a helpful relationship with your client.
8. Be constructively opportunistic with confrontational interventions – there are times when clients are more likely to respond to intervention. Be patient and wait for the right time. Any questions see principles two and seven.
9. Everything is a source of data; errors are inevitable – as Schein says, we all make mistakes. We, as coaches, have to accept the fact that we make mistakes and do what we tell our clients to do – learn from them.
10.  When in doubt share the problem – this one is about coaches helping each other, which is something that we do continuously at Big Visible.

I really like this list and find it helpful to refer back to it occasionally. However, I would like to add one of my own…

11) Set expectations up-front and adjust as necessary – your personal preferences and coaching style and that of your client’s will contribute to the specifics of this conversation, but suffice it to say that open, authentic, conversation about expectations is essential at startup and throughout the process.