I laughed out loud when I saw Ken Schwaber titled a passage of his book, The Enterprise and Scrum, “Just Do It”.

Ken describes how a customer can sacrifice quality and sustainable pace in the short term but pay it back at a premium, “$4 to remediate every $1 drop in quality.”

Clearly there are pressing bugs, misses and serendipitous opportunities. There are times to inject work into a sprint backlog. There are even times to “stop the line” and reset a sprint.

But when you manage a self-directed team, “just do it” — and I’ve heard that very phrase — is bullshit.

Just characterizes another person’s work as easy. It is the people performing work that need to estimate it. They are on the hook to execute and are incented to think critically in detail about what they are taking on. The worker grasps the actual effort better than the executive.

Do characterizes the work as physical action. Software development is problem solving and abstract modeling, i.e. knowledge work. “I’m typing as fast as I can?!” Even industrial lean practice relies on workers engaging beyond the boundaries of the immediate task to improve the product and the process of manufacture.

It characterizes the work as a single, clearly defined task. Again, the person doing the work determines whether they clearly understand assignment. Otherwise, you’re not admitting to any ambiguity of language, hidden complexity, or potential misunderstandings.

Just do it is a one way directive that splits responsibility from authority, i.e. YOU just do it. It signals a leader is not willing to do their part to remove obstacles for their team.

Just do it hides inefficiency under a veneer of necessity. Is it a surprise that “just do it” finds companionship with “just the way things are done” and “just the nature of the business”?

All this to say “just do it” in knowledge work is bullshit. The value lies not in the truth or falsity of the statement but the effect it has on the hearer. It dismisses workers’ concerns and excuses management from accountability.

Moving from bulls to birds, if self-directed teams are the goose that lays golden eggs, “just do it” is a pellet blast in the ole’ egg layer.

Short link: http://jkat.me/dQK161

Tag(s): agile, Executive, Ken Schwaber, management, scrum, software development, USD

Comments: 4

These are candid shots from this week’s Sprint review (full size image).

One of our team, Wendy, often works from home. We use webcams, skype, community document formats and remote access. She even has her own build bunny.

As you can see, we’ve developed the habit of giving Wendy a view of the action however absurd or precarious it looks.

Remoting does limit beneficial cross-talk among the pairs (osmotic communication) but word within the team is that pairing goes well. After some practice, we’re also getting the hang of the structured group conversations such as standup, sprint review and planning.

We have a strong, established bond with Wendy and the team is really pulling to make it work. She also comes into the office at least once a week which keeps us close. All and all, it’s about the easiest remote worker scenario I can think of.

The biggest downside is simply that we miss her.

Short link: http://jkat.me/k0tUAU

Tag(s): agile, management, Sprint

Comments: none

My team built an XP practice before introducing Scrum. The desire for change arose within the developers and was about sharing, becoming better at our craft and making our productivity and quality more consistent.

Scrum became necessary when our biggest problems were no longer within the team but in how we took on work from the business.

I started thinking about that at the last XTC-NYC when Mike Roberts wondered aloud if Scrum software development can work when a team doesn’t practice at least some aspects of XP. In a similar vein, Scott Bellware has a post about XP deserving more credit for Scrum’s success.

At XP-Spin, Jeff Sutherland said the success you build on is delivering working code at the end of each iteration. To even begin you need work described in achievable stories with acceptance criteria and daily builds.

Mike and Scott are definitely right when I look at my team.

Our present challenge is aligning our development with a clear and achievable business objective. Scrum is the tool for that. One of the things about Scrum is that you can use it for almost any kind of work requiring cross-functional teams.

But that challenge only exists because we were highly productive at creating quality software. The team’s XP practice with its low formality and high discipline gets the credit for that.

Short link: http://jkat.me/homOi8

Tag(s): agile, Jeff Sutherland, Mike Roberts, quality software, Scott Bellware, scrum, software development, xp

Comments: none

NYC settle a lawsuit to compensate poor families for food stamps they were denied by mistake beginning in 1999…

…as many as 34,000 families could have been affected, with the settlement ranging from $8 million to $71 million depending on how many people were involved. The city has said that it corrected the computer problem several years ago — NY Times

• Make mistake effecting food for poor families.
• Correct mistake approx. 5 years later.
• Acknowledge mistake 8 years later.
• Blame others but retain liability.

WNYC story

Short link: http://jkat.me/l46V1u

Tag(s): agile, food, mistake effecting food, USD

Comments: none

Embracing planning assumptions as more real than what people and products are actually delivering — from Jim Highsmith.

It’s like driving into a river because your GPS tells you to.

Note: Jim Highsmith’s challenge of the CHAOS study and defining success as on time, on budget, and as originally specified.

Short link: http://jkat.me/iMMT3a

Tag(s): agile, GPS, Jim Highsmith, management

Comments: none