FRAMINGHAM, Mass. — About four years ago, Medidata Solutions decided to switch from its traditional “waterfall” method of software development to an agile methodology. Medidata provides clinical testing solutions in a software-as-a-service model. “We made the change for all the usual reasons,” says Andrew Newbigging, senior vice president of research and development. “We wanted to be more responsive to customer needs.” At the same time, Medidata’s IT leaders explored the possibility of outsourcing some of the company’s software development. Though that might have made sense in the traditional waterfall world, they concluded that it was the wrong way to do agile.
“We do an iteration, get feedback, and iterate again,” Newbigging says. “That works well for us, and we were concerned that in any sort of outsourcing approach we would lose that ability to be responsive — and end up with a product our customers wouldn’t want to buy.”
It’s an opinion that many industry experts share. “We have seen cases where folks were successful outsourcing agile development. But they were the exception, not the rule,” says Sean Kenefick, an analyst at Gartner.
He and many other experts believe that the best way to create a pure agile methodology is to keep all development work in-house. Companies that do outsource agile development will inevitably face tough tradeoffs: They’ll likely have to give up some agile principles, as well as some of the cost savings typically associated with outsourcing. And managing an outsourced agile project is likely to be more difficult than managing that same project in-house.
Nonetheless, a growing number of companies will have to face the challenge of outsourcing agile development. In a survey of more than 6,000 software developers conducted by VersionOne, which makes a tool for managing agile projects, more than 80% of the respondents reported that their companies had adopted agile development.
Meanwhile, the trend of outsourcing more and more IT functions continues. According to Gartner’s IT Outsourcing Forecast, outsourcing expenditures worldwide grew 8% from 2008 to 2011, and will grow an additional 6.6% in the next two years. Judging from those statistics, it’s clear that at least some agile development projects will be outsourced.
The Case Against Outsourcing Agile
Why is it so rare for an outsourcer to successfully deliver agile development? Consider that agile development is always challenging, even in-house, with everyone at the same location. “It requires a huge amount of discipline and cultural change, and a lot of buy-in from the group, from the lowest-level person to the highest executive,” Kenefick says.
Even a company that is successfully using agile may find it hard to maintain, he adds. “It’s a very delicate balance. I’ve seen a situation where everyone was working in a bullpen and the developers wanted their own offices. That change was enough to disrupt the agile process. Just by moving a function from one side of a room to another, you make something difficult even more difficult. If you outsource it and take it to another company, you’ve made it that much harder.”
Can We Talk?
When people on the East Coast arrive at their offices at 9 a.m., it’s already 7:30 p.m. in Bangalore. That might not be a big problem in the old-fashioned world of waterfall software development, but if you’re using agile, which requires constant communication among developers, testers and the business users of the software, having team members in different time zones poses a serious challenge. What can you do? Here are some tactics that have proved effective for successful outsourced agile projects:
1. Write detailed requirements. “When we need to exchange information about detailed requirements, the time difference is a challenge,” notes Rene Rosendahl, senior manager in the project management office at Kelley Blue Book. “We’re mitigating that by providing more detailed written information than would be needed if it weren’t offshore. The goal is to minimize the questions that come back to us.”
2. Use collaboration technology. Kelley Blue Book uses a tool called VersionOne to manage agile projects and keep the lines of communication open within its agile teams. And that’s not all. “We are heavy users of instant messaging and email,” Rosendahl says. “So if someone’s gone home for the evening and offshore team members need information from that person, they might get it via email or IM.”
3. Ask offshore workers to match your time zone. Many developers in other parts of the world approach agile development for U.S. companies by working hours that, to them, are odd. “Most of our team based near New Delhi are operating on Eastern time. That helps a lot,” says Shane Aubel, CIO of the outsourcing company Tarika Technologies. The Indian workers are at their jobs from around 11 a.m. their time to 7 or 8 p.m., he adds.
It helps to not keep anyone on the late shift for too long, notes Kevin Quick, North America testing lead for Capgemini. “It’s a rotational thing, so our people can manage their lives well,” he says. “We learned the hard way that if we leave people on the late shift for too long, we tend to lose them.”
4. Keep some team members onshore. “My biggest recommendation is to make sure that the designers, architects and engineers are located onshore,” Aubel says. “We do a lot of the architecture, design and requirements, and then the specifications we send to the team are pretty well defined. It’s just a matter of coding. The challenge arises when you try to start offshoring design and architecture.”
But some industry experts are skeptical about this sort of approach for a truly agile methodology. “If you’re doing waterfall development, it’s OK to have a Java person who only knows J2EE,” says Max Rayner, executive-in-residence at Hudson Crossing. “In agile, you want developers who think like business people. It’s not enough that they can program. They have to be engaged and challenge the demands, thinking of the outcome rather than the process. So a lot of the outsourcing companies that are coder mills have a problem because they don’t have talent that is able to engage with core business matters, just on how well their code is written.”
5. Buy lots of plane tickets. Videoconferencing, instant messaging, document-sharing and remote scrum meetings all help, but in the end, nothing compares to meeting face to face. So IT leaders who’ve successfully managed offshore agile projects recommend frequent visits — in both directions. “You may have parts of your onshore team going offshore to meet the offshore scrum team in person and introduce them to your technology,” Rosendahl advises. “And you might also plan for offshore resources to come onshore to keep the exchange going and continue building these relationships. It’s not cheap, and it takes effort and time, but it’s well worth it.”
To make matters worse, using an agile methodology runs counter to most outsourcers’ business models. “Every outsourcing company has its own methodology for developing software, which it wants to use for all its clients,” says Alex Adamopoulos, CEO of Emergn, an IT consulting firm focused on agile and lean development. “That’s not necessarily a bad thing — they want to find ways to run their organization most efficiently. But it makes them less likely to adopt whatever methodology a client company is bringing.”
Indeed, embracing an agile methodology is likely to make the outsourcing company’s work considerably less efficient. “One of the benefits of agile is that you can take shortcuts while you develop in order to release more quickly. Then you go back and refactor the code later,” Kenefick says. “But how do you do that when a third party is doing the coding? They want to get it done once, the right way. As an outside vendor, why would I want to rewrite the same code more than once if I didn’t have to?”
Then there’s geography. Many outsourcing arrangements involve working with programmers in parts of the world where labor is cheaper than it is in the U.S. But if moving a function across a room can disturb the agile process, moving it across an ocean is worse.
“A fundamental aspect of agile is really quick feedback,” Kenefick says. “If you’ve got people in different time zones, you won’t have those conversations as often as you need to. I’ll write some code today, but then I won’t get feedback on it for 24 hours.”
That’s one reason why the agile methodology works so well when teams are all in the same place, he adds. “It is very hard to colocate teams, but it’s the first thing I’d put on my list of effective agile practices.”
If outsourcing agile development makes a challenging job even more so, is it a better strategy to keep all agile development in-house? For a growing number of companies, the answer seems to be yes. “We’re seeing a trend toward companies that have outsourced in the past choosing to invest in their own people’s skills and capabilities instead,” Adamopoulos says. “Smart companies are figuring out that the cost savings from outsourcing aren’t that significant. For instance, one insurance company we work with is bringing more of its development for key projects back in-house so as to have better employee retention and less risk. Their view — which has been that of a number of our clients here and in Europe — is that traditional outsourcers aren’t helping them get products to market fast enough or well enough. The change rate is slower on the outsourcer side, so to offset that, they’re building up the capabilities of their own people.”
Outsourcers as Team Members
When SciQuest, which provides software-as-a-service supply chain management tools, decided to switch to an agile software development model about five years ago, the company already had a well-established relationship with an outsourcer in India. “A big chunk of our work was being outsourced,” says Daryl Broddle, vice president of technology. The outsourcing company was a small, entrepreneurial firm that was willing to change its practices to accommodate the new methodology.
So SciQuest began creating teams, as in a classic agile setup. “The entrepreneurial partner augments our teams,” Broddle says. “The teams focus on a strategy, and the developers at the outsourcer participate in our daily standup every two or three days. We’ve integrated them into our process. We don’t write a bunch of stuff down that we send to them.”
SciQuest is based in North Carolina, and the two companies deal with the time difference by adjusting their work schedules, something that Broddle says is very manageable. “They come in at 9 or 10 a.m. and work till 6 or 7 p.m.,” he says. “We wind up with three to five hours of overlap. And if we need to have a meeting where we have to have a long discussion, then we’ll come in at 7 a.m.”
To further aid collaboration, one of the outsourcer’s developers is on-site full time at SciQuest. “He’s one of the four people on one of our four-person teams,” Broddle says. “I treat him as one of my staff, but he’s also our account manager. For instance, if one of the developers in India is not working out well, he handles it.”
This scenario has been working well for more than five years, Broddle notes. “They were pretty small and just starting out when we first started partnering with them,” he says. “They’ve grown along with us, and they are now about four or five times as big as they were when we began.”
Working with the outsourcer lets SciQuest meet its goal of getting new features to customers faster. “We have three major releases a year, but in between we use focus groups,” Broddle says. “We show them new functionality and get their input long before we put a new feature into the production environment. With the outsourcer augmenting our teams, we can get something done and ready to implement in front of our focus groups within a two-week sprint. We’re not showing them screenshots — it’s real code.”
That’s the decision Medidata made last year when the company decided to expand one of its software offerings and once again took a serious look at outsourcing agile development. “We decided to hire and increase the size of our internal development team instead,” Newbigging says. “We feel quite strongly that we’re better off having our own developers building the software, and also being responsible for maintaining it, responding quickly to any issues. They are able to understand the software because they built it in the first place, and that’s harder to achieve if the original development was done elsewhere. You don’t have that same depth of knowledge.”
Outsource for the Right Reasons
While keeping all agile development in-house may top the wish list of many IT leaders, it’s not a realistic plan for every company or every situation. With looming technology skills shortages and pressure on IT budgets, some agile software projects will have to be outsourced.
So how do you decide if it’s right to outsource an agile project? Begin by asking yourself what you hope to gain from working with an outsourcer. “The ideal reason is so as to give immediate response to a business need,” says Max Rayner, executive-in-residence at consulting firm Hudson Crossing. “Can you find ways to also have it lower cost? Yes — but something important enough to be done in an agile way is likely to be worthwhile, whether you’re paying $1,500 a day or $1,000 a day or $750 a day. By going to some of the lowest-cost countries, you can get a very competent programmer for $25,000 a year, including benefits — but that’s not necessarily going to help your project succeed.”
Before joining Hudson Crossing, Rayner was CTO at TravelZoo and oversaw the creation of the travel search site Fly.com, for which he used an outsourcing company based in Lisbon, Portugal. “That was a 100% agile project using scrum,” he says. (In scrum, small teams work on a specified portion of the requirements for a limited amount of time and hold daily meetings to assess progress and address any questions or problems.) “I was in California, so we had hardly any overlap in our work days, but it worked brilliantly. My morning was their evening so I would get to say, ‘OK, yesterday we agreed you were going to do these five things. Did you do them? How’s it going?’ “
There were members of Rayner’s team working on the project in California as well, he adds. “At the end of the workday, each team would hand off to the other shift. That’s more complex than a traditional agile arrangement where everyone is in one location, but I was willing to take responsibility for the time, cost, and feature tradeoffs,” Rayner says.
That factor — having an IT leader take responsibility for the project — is a key differentiator, he adds. “A lot of IT managers make the following mistake: They’re under pressure to reduce costs, so they decide to go to an outsourced company that promises to use agile methodologies. They think that not only will they get lower labor costs, they’ll get the higher productivity of agile.”
That kind of thinking can lead to trouble because using the agile methodology means giving up some of the cost savings traditionally associated with offshore outsourcing. Indeed, Rayner says, Fly.com’s success was due in part to the fact that his company paid a higher price to work with the outsourcer’s most experienced developers. “They were every bit as important in solving business problems as they were in solving coding problems,” he says.
Outsourcing agile development may not save that much time and effort either. “You have to be willing to work as hard with an outsourced partner as you would with your own people,” says Rayner. “And your super users need to be involved to help determine features.”
The worst outsourced agile disasters occur when the client company thinks it can hand off responsibility to the outsourcer. “At one company I worked with, speed of delivery was worse than before the agile outsourcing,” Rayner recalls. “At the root of the problem was this attitude that, ‘now that we have an outsourcing contract, they have to be the ones to do it. They have to be agile and fast, and we don’t have to be in touch every day.’ “
He notes that there’s another reason — usually unspoken — why IT leaders sometimes choose to outsource: So they can deflect responsibility and gain a scapegoat in case things go wrong. “You can’t go to the business sponsor and say, ‘I told them to do what you asked, and it doesn’t work. We’re going to fire this outsourcer and get a new one,’ ” Rayner says. “That’s often what happens when a project fails.”
This kind of thinking can kill an agile project before it even gets started, he says. “The very spirit of agile is to have mutual trust and respect, and a flexible relationship where you know at each decision point exactly what cost, time and feature tradeoffs you’re making. That’s hair-raising to some engineering leaders because they can no longer hide behind the contract.”
Is ‘Partly Agile’ Enough?
If you do decide to outsource an agile project, one question to consider early on is just how much of the traditional agile methodology you want to adhere to. Because working with an outsourcer will almost certainly prevent you from using a completely agile framework.
“In most cases, the outsourcing company would be using scrum as an agile practice,” Adamopoulos says. “While this is fine, more and more companies are figuring out that they can use agile across a whole set of areas in the software life cycle. They might use agile in the early idea-management phase and the vetting of an idea well before requirements are even needed. It might also mean they use agile practices to develop comprehensive business cases and metrics. All of that is usually not a discipline an outsourcing company brings.”
“In principle, the agile methodology says that you have a cross-functional team that is colocated. You can make decisions on the spot and you can look at things together,” adds Rene Rosendahl, senior manager in the project management office at Kelley Blue Book in Irvine, Calif. The company uses an outsourcer in Beijing to provide agile development for its website KBB.com and other products. “With offshoring, you are forced to separate the product owner from the rest of the team, and you need to write things down and expect delays in decision-making. Does that mean you have to compromise some of these agile principles? I think the answer is yes. You cannot apply the principles in the same way you can with in-house teams, but you hold on to them as much as possible.”
Picking the Right Agile Outsourcer
Choosing the right outsourcing company may be the biggest part of the challenge. “Pick a partner that’s really going to be your partner, not someone who’ll just deliver that [statement of work] to you,” advises Daryl Broddle, vice president of technology for SciQuest, an online procurement technology provider. SciQuest has used an outsourcer to do agile development for years. “I have a personal relationship with the CEO of that company,” Broddle says. “He visits me once or twice a year when he’s passing through. Neither company would be where it is without the other.” (See the “Team Augmentation” sidebar.)
Perhaps most important is a willingness to face up to the profound changes that a move to agile requires. “There was one large logistics company in Europe with an outsourcing agreement with a very well-established systems integrator,” Adamopoulos recalls. “The systems integrator’s model wasn’t helping the logistics company. It wasn’t getting new features fast enough and was losing market share. Every time IT executives had a conversation with the outsourcer about agile, the outsourcer would make some minor change, but then things would go back to status quo.”
The logistics company hired Emergn to train both its own team members and its contacts at the outsourcer in using the agile methodology. Once they were trained to employ agile properly, they were able to shorten the average release time for a new feature from 300 days to 47 days, Adamopoulos says. “The logistics company reclaimed about 21 million euros in revenue that year because they were able to move feature releases up 10 months. In the past year, they’ve also regained a fair amount of the market share they’d lost.”
He was especially impressed with the outsourcer’s ability to completely change the way its developers worked. “That was a huge win, and it’s gotten companywide recognition at the outsourcer,” he says. “They’re beginning to use the agile methodology within their own organization as well. They recognized it was something they needed in order to remain competitive.”
Large or small, an outsourcer willing to make changes like these is probably a good bet if you are facing the challenging prospect of outsourcing agile development.