February 4, 2012

BigVisible Blog

Coercive vs. Enabling Bureaucracy

We all know that bureaucracy is bad, right? The tales of insanely complex, rube-golderg-like processes residing within large organizations are too numerous to cite. Most people universally agree that this type of overhead is a negative thing. More process is a hindrance on human creativity, something that should be avoided at all costs. Indeed, many Agile teams see their first big productivity boost from casting aside the detritus of unnecessary rules, roles, and other organizational straight jackets that were keeping a group of individuals from working as a productive team.

If we accept this truth, then does that mean the goal should be to eliminate all bureaucracy? The process rigor seen in most organizations is excessive, but many view it as a necessary evil. Necessary in order to maintain the scale, performance, or consistency required for there particular organization. With this in mind, managers may agree that organizational structure and rules can become stifling, and yet continue to implement it as a necessity for their organization. Quite possibly, they are right. What if the question isn’t about whether or not we have process, but rather what that bureaucracy should look like? Not all processes and organizational structures are created equally.

[Read more...]

The Building Blocks of a Project Pipeline

Scrum is a great framework for building systems, it is simple, elegant and effective. However, it has one limitation that most teams quickly run into: small team size. Invariably, most major initiatives and programs require more than 7, plus or minus 2 people, in order to complete the work in a reasonable amount of time. Or, some organizations face the flip side of this where they run so many projects that the idea of dedicating half a dozen people full time to one initiative is overwhelming. In either case, these organizations are facing the challenge of managing a product pipeline. Let’s take a look at some of the techniques available to manage this within an Agile program.  [Read more...]

Clockware and Swarmware

Swarm of ants on a clockAt times both the Agile and traditional Waterfall camps get hung up in an unproductive game where they start digging through the details of a problem domain, find a specific circumstance and say, “ah ha! A purely [Agile / Waterfall] approach can’t deal with this situation, therefore that approach is wrong”

Indeed, this binary obsession – that you must pick one specific approach and apply it to all dimensions of a project – is entirely unproductive. In fact, it is usually not the reality in an Agile or traditional project, but rather a limit of our own thought process. The challenge being that if we find merit in one approach, the mind can take an absolutist value. Agile is useful for dealing with product visions, therefore we should apply Agile principles to every aspect of our project.

The test of a first-rate intelligence is the ability to hold two opposed ideas in the mind at the same time, and still retain the ability to function.
F. Scott Fitzgerald, “The Crack-Up” (1936)

Fitzgerald accurately describes the challenge facing us when organizing and executing projects; we must hold two opposing ideas within our head and continue to function. These two opposing ideas well well described by Kevin Kelly when he coined the terms clockware and swarmware as the two different approaches to managing work. They have since been embraced by many complexity theorists and I present them here as my own attempt to hold two opposing ideas and continue to function and show how one builds upon the other, and to argue that a project requires one or the other will inevitably lead to failure. [Read more...]

Effective Daily Meetings

This entry is the first in a series  drawing upon some of the practical experience of BigVisible coaches in the field. In support of consultants, individual coaches may bring forward questions and challenges they face. We have edited and distilled one or more conversations on a topic into a format outlining a specific challenge, concrete recommendations, and lessons learned from the discussion. We hope you enjoy, and would welcome feedback on this particular challenge, as well as requests for future topics.

Objective:

The Daily Scrum (or daily standup meeting) is a critical meeting for teams to get together and do their daily planning and tracking of work. This meeting is a checkpoint that the team is working together to achieve the goals of each Sprint.  They do this by determining their current progress and identifying anything that is impeding the ability to achieve those goals.

Challenge:

However, it is a challenge to many teams to do this in a shorter meeting.  Scrum recommends that this meeting is no longer than 15 minutes.  Some teams focus on meeting the time but don’t come out of the meeting with a joint understanding of the team’s plan for the day.  Other teams find the meeting valuable but taking much longer to discuss, sometimes taking up to an hour each day for the meeting.  Eventually, the team will start to complain that “Scrum has too many meetings” and is keeping them from accomplishing the work in the Sprint.  We don’t want the Daily Scrum to become THE impediment!   [Read more...]

Greenshifting and Redshifting within Projects

I’ve been thinking recently about the various roles project stakeholders play, and how they may distort the environment around a project until that distortion in turn impacts the reality of the project. Let me offer two key examples. The first, coined by Scott Ambler, is known as greenshifting. In this case, the further information moves from the team, the better – hence “green” on a status report – the project looks. This is a common dynamic, one that most people have experienced first hand. The team members report out numerous challenges, which the project manager – who is there to make sure problems don’t emerge of course – puts as positive a spin on it as he can. This may get filtered up through any number of managers who need to present their work in the best light, such that a project under serious duress will appear to be in perfectly good shape. [Read more...]

Too Many Meetings? Don’t Go!

I often hear complaints about meetings – too many meetings, too many people in meetings, meetings that are too long, meetings that are useless to particular participants, and the list goes on…

[Read more...]

Are the right people getting a chance to lead?

A few months ago I delivered some training and was doing some follow up coaching with a team and I observed something that I thought was pretty fascinating and sparked the thought for this blog.

A team had recently completed a round of basic agile training and was a few sprints into their work. During sprint planning, several members of the team felt organizational pressure to create a sprint plan that was twice the velocity they had established through their first 2 sprints. As I prepared to interrupt the team and ask how they arrived at the notion that they could double their velocity in one sprint, the most junior member of the team (a college student on a work assignment) beat me to it and said: “we can’t do that, it’s double what we’ve done before. Our velocity is x, so we should plan for x.” (I was glad to see that the training had stuck with someone.) There was some discussion, culminating in the more experienced members of the team answering with “well, we have to get all this work done this sprint, so we should tell management we are going to”. [Read more...]