BreakingExpress

Why (some) agile groups fail

Over the previous 12 months, I’ve had many conversations with folks that at all times appear to revolve round two questions (a lot to my dismay and ensuing squinty-eyed look):
  • Where are you going with agile at your organization?
  • What form of standardization (and/or framework) do you present for the corporate?

Before I reply these questions, let’s begin with a narrative. When I used to be first working towards agile in 2006, I used to be requested to doc our scrum course of so the staff would greatest perceive the way it labored for tasks that had an finish or “release” earlier than we moved onto the following mission. We got here up with a visible that appeared like this:

Looking again on this expertise, it made good sense for me to standardize the method. We had been a small staff, and the documentation we produced was what labored for the staff on the time we created it. Twelve years later, my perspective has modified, and I view paperwork like this as ambivalent or chaotic neutral at greatest. At worst, they’re typically used because the holy grail to fixing staff issues. The hazard is at all times in how the knowledge is used.

“Look over here – this team seems to be doing well, we should just copy what they are doing!”

Teams are totally different as a result of they’re made up of various folks with totally different conditions. Certain practices could be simply shared throughout groups, however in my expertise, attempting to standardize processes would not truly work and provides pointless overhead on groups. To make issues worse, the introduction of certifications within the trade has over-emphasized the concept that implementation of agile is the one factor that issues, relatively than the concept that groups experiment and study collectively what works for them. This is similar hazard we face with capturing metrics on groups and utilizing them with out understanding their intent and function.

“This team over here can do 60 story points a sprint, but this team over here is only doing 40. Clearly, there is a problem.”

Yes, there’s a drawback, however it could truly be “jumping to conclusions.” Comparing what one staff can do vs. one other is a shorthand administration method to agile at its worst. It’s a symptom of each a lack of awareness of the intent behind self-organization and steady staff enchancment and in addition an indicator that the trade of agile has spent quite a lot of time targeted on the efficiency of small engineering groups. The onerous work of addressing how the remainder of the group will get work performed stays largely unfinished.

So, when confronted with the query: What form of standardization (and/or framework) do you present for the corporate? My opinion has at all times been at first primarily based on this assertion:

Do not do what works for one more staff. Do what is true on your staff.

And the more durable query: Where are you going with agile at your organization? My reply is just a little squirrely, however it’s an sincere one. We go nowhere collectively if we do not keep true to the foundational reality of what agile was asking us to give attention to in 2001: constructing belief and transparency in groups to allow them to work collectively to speed up their studying in a secure and open atmosphere. We go nowhere collectively if we glance to push course of onto others with out striving first to know why and what’s wanted.

One would possibly suppose after seeing the above image, “Get that cat off the router before it overheats,” with out first asking, “Why the cat is sitting there?” I can assault the issue by eradicating the cat, or as a substitute, I can remove the issue by offering the cat with a heated mattress within the winter so the arthritis in his again legs would not really feel fairly as dangerous when it’s chilly.

three information rails for groups

I am certain you might be considering at this level, “OK, Jen, that’s not really solving the reason we asked the question in the first place.” Many folks I discuss with concerning the topic of agile typically really feel trapped by the established order, like this cat. I perceive that—I’ve additionally felt that means. Sometimes, I nonetheless do. In an effort to assist with this drawback, I ask groups I work with to comply with some information rails, and I advocate others groups embrace these practices as nicely.

Track and share your work so others in your group can perceive what it’s you might be doing.

The key right here is not that you’re monitoring the work (though that is a bonus!), it’s that others past you can perceive why you might be doing the work. If you possibly can’t talk the shopper worth to somebody who is not concerned within the particulars, do you actually perceive it your self? Additionally, there’s vital worth in with the ability to empirically clarify how you’re going to measure the influence of the work you might be finishing. This follows the easy person story format of: As a buyer, I would like this piece of performance, in order that I can obtain this outcome. This is adopted by: We know we may have delivered this outcome by these units of qualitative vs. quantitative measurements.

There is reality within the phrase, “Begin with the end in mind.”

Continuously work on enhancing your observe as a person and staff.

This consists of the method by which your staff and product get work performed and what your job perform is. If you might be an engineer, study one thing new about coding and observe it. If you’re a mission supervisor, check out a brand new facilitation approach you examine. Process would not solely discuss with how you progress playing cards round in a monitoring system. Make certain you might be overtly speaking along with your staff concerning the issues that are not working—whether or not it’s associated to folks course of or technical course of. Without that dedication, course of and expertise will grow to be stale.

Perhaps the perfect we will do on this area is comply with standardize on routinely sharing with the entire group how we’re constantly working to enhance and the metrics we use to display that.

Note: If you come to me and sheepishly confess that your staff has stopped doing standups as a result of the staff would not see the worth in spending the time, and your complete staff is delivering measurable and clear worth to your prospects when it’s wanted, do not anticipate me to be upset. I’m possible going to ask some questions, congratulate you, and ship you in your means with encouragement to proceed having good conversations about what works.

I am not speaking concerning the particulars behind implementing a expertise. I am speaking about defining everybody’s roles within the work, defining the place conversations will happen, and defining how necessities will cross backwards and forwards from staff to staff—establishing as a lot concord as doable earlier than work begins and you discover yourselves counting on one another to share area collectively—and not using a catfight erupting. As expertise continues to innovate at a speedy tempo, groups with heavy cross-functional dependencies will discover that the issue will worsen. In my thoughts, it’s the single greatest purpose why tasks fail. This is the place standardization is most wanted as a result of, with out standardization, it’s onerous to automate.

Do the precise factor

I need to shut by re-emphasizing this assertion: Do not do what works for one more staff. Do what is true on your staff. Every failed agile adoption story I’ve heard in my profession is constructed on high of the failure to comply with that mantra. I encourage everybody to embrace that concept and search assist out of your native agile consultants when the staff wants it.

Finally, when approached with a “you must do this because so-and-so is and it works for them…” look again on the information rails I’ve outlined above. Most groups are put into that place as a result of they’re perceived to not share why they’re doing one thing, they don’t constantly enhance their course of, nor do they make sure that dependency-riddled work is dealt with with minimal day-to-day battle. My name to motion for groups which are in that area is to consider why they’re in that place, and what they need to do to interrupt freed from that notion.

Most importantly to my fellow coworkers, technologists, and agilists: If you do not agree with what I’m sharing, you are able to do what my cats do… or you possibly can share what works on your staff.

Exit mobile version