Collocating for Project Inception: It Costs Too Much NOT To Do It

One reality of modern software development is that teams are not collocated. Not around the same table, not in the same building, not in the same city, and often not in the same time zone.

In some cases, companies are taking advantage of exchange rates or pay rates, and locate teams where they can buy more hours for each unit of their currency.
In other cases, companies cultivate a better work-life balance for their employees, and stop enforcing policies around grueling commutes and time clock punching.

Communications tend to deteriorate even more once you let Briana work from home in Wisconsin and Tad work from his mom's place in Hawaii, and everyone has to get on a conference call with Australia at 4:30pm, CST, since a third of the team isn't even in a time zone which is offset by a full hour from you. Especially if Tad has small barking dogs and a cockatoo.

So here's one incredibly good thing you can do, in the face of this potentially toxic communications cocktail: start every project with a requirements workshop where in-person attendance is mandatory (and funded) for the product owner, leads from analysis, development, QA, and operations teams. Sponsors and subject matter experts should be readily available in person as well.

This get-together will require an initial outlay of funds which will hugely repay itself over time. In her 2004 book, Requirements By Collaboration, Ellen Gottesdiener quotes these helpful statistics from Capers Jones about return on investment for such gatherings. According to Jones's empirical measurements of large-scale software projects, a facilitated workshop of this type will:

Reduce the risk of scope creep from 80 percent to 10 percent, and to 5 percent when combined with prototyping (Patterns of Software Systems Failure and Success, 1996)
Cut requirements creep in half (Software Assessments, Benchmarks and Best Practices, 2000)
Provide a 5 percent to 15 percent overall savings in time and effort for the project as a whole (Patterns)
Reduce defects delivered in software by 20 percent (Patterns)
Reduce project failure and cancellation rates by about 50 percent (Patterns)
Provide a 10-to-1 return on investment ($10 for every $1 invested; Patterns)

If your CFO is still skeptical, you may suggest running an internal experiment on two projects (try just one with an in-person requirements workshop) and measure for yourself!

Comments

How Do You Vote Someone Off of Your Agile Team?

One of the conundrums of agile conversion is that although you are ordered by management to "self-organize," you don't get to pick your own team. You may not have pictured it this way, but your agile team members are going to be the same people you worked with before, when you were all doing waterfall! I know I wasn't picturing it that way for my first agile team, so I thought I should warn you. (I thought I was going to get between six and eight original Agile Manifesto signers. That didn't happen.). Why "warn" you (as opposed to "reassure" you, say)? Because the agile process is going to reveal every wart, mole, quirk, goiter, and flatulence issue on the team within a few hours. In the old days, you could all be eccentric or even unpleasant in your own cube, communicating only by document, wiki, email, and, in extreme situations, by phone. Now you are suddenly forced to interact in real time, perhaps in person, with written messag

A Corporate Agile 10-point Checklist

I'm pretty sure my few remaining friends in the "small, collocated team agile" community are going to desert me after this, but I actually have a checklist of 10 things to think about if you're a product owner at a big company thinking of trying out some agile today. Some of these might even apply to you if you're in a smaller place. So at the risk of inciting an anti-checklist riot (I'm sorry, Pez!), I am putting this out there in case it is helpful to someone else. From http://www.yogawithjohn.com/tag/yoga-class/ Here's what you should think about: 1. Your staffing pattern. A full agile project requires that you have the full team engaged for the whole duration of the project at the right ratios. So as you provision the project, check to see whether you can arrange this staffing pattern. If not, you will encounter risks because of missing people. Concretely it means that: a. You need your user experience people (if a

Your Agile Transformation Needs to Start with a Quiet Phase

From a really great blog post on agile adoption: http://smoovejazz.wordpress.com/2011/02/16/an-agile-approach-for-adopting-agile-practices/ I've observed some different agile transformation patterns, and maybe you have too: Just Do Standups (Shoot, then Aim): some people feel that since you're "agile," you should just start doing stuff, like daily standups, and then build more of the the plan as you go. Find a team and start doing some agile with them! Start a revolution one practice at a time, one team at a time. Pros: you're very busy from the start. Cons: what exactly are you doing and why? KPI-Driven Change (Aim, then Shoot) : some people who have worked in large corporations for a while will tell you that to get the respect of the people, you need to start with a plan, support the plan with awesome printed and online collateral. Then you "kick off," tell teams what to do, and measure them using "Key Productivity Indica

Pragmatic Agilist

Search This Blog