Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Good And Bad Of Agile Offshore Development


Published on

Originally presented at Agile 2008 in Toronto

  • Hello Mike, Those insights sound pretty helpful in general but I invite you to analyze the benefits of nearshoring instead. This brings together the best of both worlds, you get to work agile in the same time zones which leads to better communication but you also get way better rates that doing it with stateside developers.
    Are you sure you want to  Yes  No
    Your message goes here
  • Hello

    I would like to share some of my experience for outsourcing IT Projects to India. Initially I was reluctant to give the work to India.I was doubted about the quality and time to complete the project. I thought to give a trial. I contacted the site .Fortunately for me it was the right choice. That was a wonderful experience with them. Now I got the project done in 362 mandays. I saved a lot on the project. If I done it in USA the cost will be double.
    I recommend them for any of these projects. They are into ASP.Net and WCF.

    Are you sure you want to  Yes  No
    Your message goes here

Good And Bad Of Agile Offshore Development

  1. 1. The Good and Bad of Agile Offshore Development
  2. 2. Where to go for the presentation <ul><li>Mike’s blog: </li></ul>
  3. 3. Who is Mike Cottmeyer? <ul><li>Have been on the VersionOne service team for about 8 months </li></ul><ul><li>Prior to joining VersionOne I was a Senior Project Manager for CheckFree Corporation in Atlanta, GA </li></ul><ul><li>This experience report is about a very large initiative I managed a few years ago </li></ul>
  4. 4. Who is CheckFree? <ul><li>CheckFree is the leading provider of online banking and bill payment services to the banking and financial services industry </li></ul><ul><li>We were building services that would enable CheckFree to provision a custom bill payment website for a major customer in less than 90 days </li></ul>
  5. 5. Just how big was that project? <ul><li>The largest of these initiatives was planned to take over a year and half </li></ul><ul><li>The project had over 70 people involved from concept to delivery and was estimated at over 10,000 ideal engineering hours and delivered for about 30,000 real hours </li></ul>
  6. 6. What else could we do to make it hard? <ul><li>And… we were using an Indian offshore development team for a significant part of the work </li></ul>
  7. 7. Take a moment… <ul><li>Imagine you are the leader of a development organization, maybe a senior project manager </li></ul><ul><li>Your senior leader comes to you and says you’ve got to cut costs </li></ul><ul><li>He tells you the company has entered into an agreement with an offshore dev firm </li></ul>
  8. 8. You have to layoff 50% of your staff and those jobs are going to the offshore vendor
  9. 9. The Realization <ul><li>You still have 100% of your projects to complete </li></ul><ul><li>Half of your new team is over 8500 miles away and separated by a 9 or 10 hour time zone difference </li></ul><ul><li>Not a great environment to be Agile </li></ul>
  10. 10. My take… <ul><li>Not a big fan of taking teams offshore </li></ul><ul><li>These projects are very challenging and delivering the right product requires a huge investment of time and money </li></ul><ul><li>Often don’t realize the cost savings you expect going in </li></ul>
  11. 11. Call to Action <ul><li>If you find yourself in this situation, you have to find away to make it work </li></ul><ul><li>Failing to deliver is not an option </li></ul><ul><li>There are too many examples of offshore projects that have failed from poor requirements, lack of management oversight, and failure to communicate </li></ul>
  12. 12. Only go offshore if you have to. If you have to go offshore , you better go Agile .
  13. 13. Our focus for today… <ul><li>Contract negotiation </li></ul><ul><li>Working as one team </li></ul><ul><li>Metrics and tooling </li></ul>
  14. 14. The Agile contract <ul><li>Build Agile processes into the agreement </li></ul>
  15. 15. The Agile contract <ul><li>Only specify what can be specified </li></ul><ul><ul><li>Tooling </li></ul></ul><ul><ul><li>Core competencies </li></ul></ul><ul><ul><li>Key personnel/retention </li></ul></ul><ul><ul><li>Forecasting </li></ul></ul><ul><ul><li>Sprint planning </li></ul></ul><ul><ul><li>Service levels </li></ul></ul>
  16. 16. The Agile contract <ul><li>Maintain room for trust and collaboration </li></ul>
  17. 17. Working as One Team <ul><li>Teamwork </li></ul><ul><ul><li>Mix onshore and offshore people </li></ul></ul><ul><ul><li>Rotate the offshore team members between on shore and offshore </li></ul></ul>
  18. 18. Working as One Team <ul><li>Collaboration </li></ul><ul><ul><li>Tools </li></ul></ul><ul><ul><li>Overlapping work days </li></ul></ul>
  19. 19. Working as One Team <ul><li>Invest in people </li></ul><ul><ul><li>Training </li></ul></ul><ul><ul><li>Mentoring </li></ul></ul>
  20. 20. Metrics and Tooling <ul><li>Use a tracking tool </li></ul><ul><ul><li>Excel and homegrown </li></ul></ul>
  21. 21. Metrics and Tooling <ul><li>Measure everything </li></ul><ul><ul><li>Team velocity </li></ul></ul><ul><ul><li>Individual velocity </li></ul></ul><ul><ul><li>Project burndown </li></ul></ul><ul><ul><li>Major milestones </li></ul></ul>
  22. 22. Metrics and Tooling <ul><li>Define Done </li></ul><ul><ul><li>Very clear backlog items </li></ul></ul><ul><ul><li>Continuous integration </li></ul></ul>
  23. 23. Lessons Learned <ul><li>Offshore required more doc </li></ul><ul><li>Put a greater burden on the onshore team </li></ul><ul><li>Found we had to be more prescriptive </li></ul><ul><li>Yesterday’s weather didn’t work </li></ul><ul><li>Stretch goals and Turnover </li></ul>
  24. 24. Key Takeaways <ul><li>Offshore only if you have to </li></ul><ul><li>Agile can help you be more successful </li></ul><ul><li>Provides an ability to guide the project into an acceptable outcome </li></ul><ul><li>Adapt processes </li></ul>
  25. 25. Be aware of your business drivers
  26. 26. Where to go for the presentation <ul><li>Mike’s blog: </li></ul>
  27. 27. Simplifying Software Delivery