Thoughts from the trench - by Prakash Muralidharan

August 17, 2008

Nederlands/Dutch Français/French ???????/Russian Deutsch/German Italiano/Italian Português/Portuguese Español/Spanish ????????/Greek 日本語/Japanese 한국어/Korean 中文(简体)/Chinese Simplified 中文(简体)/Chinese Traditional

Buy versus build.

Filed under: Software Services, Outsourcing — Prakash Muralidharan @ 2:01 pm

JP proposes the following mantra for buy versus build technology decisions (building something inhouse versus buying a commercial product:

"If the problem is generic use opensource
If the problem is specific to a market segment use commercial
If the problem is unique to your organisation use your own resources"

Buy versus build decisions are often complex with political ramifications.

If you make a build decision, you often need to decide on whether to outsource and if so, what to outsource. When it comes to outsourcing, I use the following broad pattern of thought:
-Think deeply about the role IT is playing in your business today, and where you see it going tommorrow.
-Look at your application portfolio and your people capabilities in relation to the role you see IT playing.
That will tell you where your crown jewels are and also point out your capability gaps.
-Use outsourcing to fill capability gaps in such a manner that your own people can polish your crown jewels.

Enough said for a Sunday afternoon!


Linking and Sharing

If you found this page useful, consider linking to it.
Simply copy and paste the code below into your web site (Ctrl+C to copy)
It will look like this: Buy versus build.

del.icio.us:Buy versus build.  digg:Buy versus build.  fark:Buy versus build.
Trackback

Trackback URI for this entry:

http://www.prakashonsoftware.org/blog/index.php/2008/08/17/buy-versus-build/trackback/

No Comments »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a comment

Creative Commons LicenseDisclaimer : This blog site is published by and reflects the personal views of Prakash Muralidharan,in his individual capacity. It does not necessarily represent the views of any of his employers, past or present, and is not sponsored or endorsed by any of them. No representation is made about the accuracy of the information contained in this blog.