Technologist. Leader. Ironman.

Managing Offshore Software Development

clock January 29, 2010 07:15 by author Mike Schubert

3d person and globe
Originally uploaded by 姒儿喵喵

Over the last decade, many lessons have been learned about sending software development work overseas. These lessons have been documented in books, magazines and blogs the world over. Many lessons are similar to those that you would face if you chose a consultancy down the street from you. Others are simply lessons of doing business with cultures foreign to your own.

For those who have been working with offshore partners for a number of years, what I write here on the subject will be a "no duh" moment. Others looking to embark on a pilot of sending work overseas may think "this won't happen to me." Regardless - what I write over the coming weeks and years will be my observations and a sort of record of my experiences.

My thought for today is this -> It can be more challenging than it might appear. On the surface, the idea sounds great. You do the customer interactions, the requirements definition and design work - then turn it over to your partners to implement. But what if there are issues? When the work is done within 3 timezones of yourself, getting people together to discuss the issue is very straightforward. Even emailing back and forth is possible when the timezones are close.

But the problem with sending work 12 timezones away is the lag in time. If there is an issue that impacts delivery dates, resolving it via email is a guaranteed way to miss your deadline. One model that has worked well is to use an "onshore coordinator" - a technical individual that works for your offshore partner whose job is to interface with you and the offshore team and work across time boundaries to get issues resolved. 

One final thought on this matter is this -> no matter which of the above options you take, whether you have an onshore coordinator or you are up at midnight on the phone - YOU are the bottleneck. It may be that the team overseas is incompetent, but it's your job to make them competent (or take some other action). If systems are unreachable, requirements are unclear, or deliverables are of poor quality it is your responsibility to remove the obstacles and rectify the situation. If you execute well, your chances for a successful program are higher.


The Year Ahead in Sport and Career

clock January 2, 2010 12:05 by author Mike Schubert

My focus this year is on nutrition and quality events. For the first time since 2007, there is no full distance Ironman triathlon on my race calendar. I am hoping this will allow me to focus on shedding more weight and building my capacity rather than focusing on getting ready to "get through" a 140.6 mile race. I have picked a handful of triathlons including 2 half-iron distance endeavors. I have also set my sights on 4 or 5 marathons with the goal of going under the 4 hour mark for the first time.

On the work front, my responsibilities are slowly increasing. I have a small portfolio of projects that I'm slated to deliver by the end of March and it is giving me a good taste of the rigors of resource, risk, and plan management at that level. The budget and scope are smaller than the largest project I managed, but has been a good way to get my feet wet in this arena that I hope to fully move into one day. During the 2nd half of 2010, I will likely be involved with revamping either our dot com or intranet platform (or both!). I'm looking forward to the opportunity to continue to grow. I'll yap more about this in March when I look back on my tenure at McKesson.


2010 Resolution Run 10K Race Report

clock January 1, 2010 21:04 by author Mike Schubert

Happy 2k10 to ya! This year has started off in much the same tradition as the past 5, with a 10k run at high noon.

This year's Atlanta Track Club Resolution Run marked a major departure from years past. This used to be a low-key event where you registered only on race day, it was free to members ($5 to non-members) and maybe 400 people or so ran it. This year, pre-registration was mandatory, it was chip timed, and around 1700 people signed up between the 5k and 10k.

The temperature at race start was somewhere between 35 and 40, with 10mph winds. It was very difficult to dress for this event. There were times I felt overdressed (no wind and in the sun) and times that I froze my ass off (shade and wind). I simply couldn't win. In the end, I ran my best for the day and turned in a reasonable 56 minute time. That's a full minute per mile slower than when I turned in a 49:xx time in 2008. Most importantly, I had a good time and started the new year off right.


Atlanta New Years Day Resolution Run - New Entry Procedures

clock November 26, 2009 19:04 by author Mike Schubert

In previous years, the Atlanta Track Club has hosted a 5k / 10k "Resolution Run" at high noon on New Years Day. It was a no-frills event where you walked up, paid $5, registered, got a t-shirt, and ran. That's it. This has changed for the 2010 event.

For 2010, you will be required to register before 11:59 pm on December 29th. And it will no longer be $5, but between $22 - 25 depending on when you sign up. Long sleeve technical shirts will be given out this year instead of the cotton ones from years past. Rumor has it that it will be chip timed using those D-tags, though I can't find anything to back that up at the moment. I'll gladly pay $25 for a chip timed 10k. 

Here are the links to the Resolution Run event information page and the event registration page.


Six Qualities that Correlate with Feelings of Confidence in Leaders

clock November 23, 2009 09:13 by author Mike Schubert

You are only a leader if people want to follow you. That is a somewhat loaded statement as incentives can encourage anyone to "want to follow you". Just look at the current President of the United States. Politics aside, whether you are organizing a community or leading a Fortune 1000 company, there are certain qualities that individuals exist that give people confidence in their leaders. According to the National Leadership Index for 2009, they are:

  • Trust in what the leaders say
  • Competence to do the job
  • Working for the greater good of society
  • Share my values
  • Get good results
  • In touch with people’s needs and concerns
  •  

    Take these qualities and apply them to your leadership. I have run several people through my head mentally and find these traits to be accurate measures of what my gut reaction would be. For a couple, it's "yes, they are solid". For a few others "yes, they're good, but I'm not quite sure." Finally, for others I'm asking "who put this guy in charge" and they are failing in all of these traits.

    I hope people nod their head when they think of me and say "yes, Mike is solid". I simply see these traits as black and white and, for the most part, things that cannot be learned.