InfoQ

News

CIO JP Rangaswami on open source in the enterprise & the future of information

Posted by Floyd Marinescu on Mar 08, 2007 01:09 PM

Community
Java,
Architecture,
.NET,
Ruby,
SOA
Topics
Open Source,
Business
In this must-see InfoQ exclusive, CIO JP Rangsawami explains how open source became a corporate IT strategy at investment bank Dresdner Kleinwort Wasserstein and why CIOs of major enterprises should consider open source for software development initiatives. JP also explains his vision of four pillars of the new world if information: Syndication, Search, Fulfillment, and Collaboration/Conversation.

Watch:  JP Rangaswami on open source in the enterprise & the future of information (30 min pres + 20 mins Q&A)

JP Rangaswami was named Top CIO of the Year in 2003 by Waters Financial Magazine for "Deploying disruptive technology, keeping a wary eye on outsourcing and defending IT makes".  JP Rangaswami is CIO of Global Services at BT. At the time of this recording, Mr. Rangaswami was CIO of Dresdner Kleinwort Wasserstein investment bank. JP blogs at www.confusedofcalcutta.com, where he writes about information, IPR and DRM, opensource, agile methods and identity.

3 comments

Reply

"must-see" by John Davies Posted Mar 8, 2007 6:54 PM
qutie enjoyable by Stuart Charlton Posted Mar 12, 2007 5:55 PM
- Unbelivably, a thought provoking message.... by Vijay YD Posted May 27, 2008 2:13 AM
  1. Back to top

    "must-see"

    Mar 8, 2007 6:54 PM by John Davies

    JP is truly one of the great thought leaders, many of his ideas were years, even a decade ahead of their time, there are things he suggested years ago that are only now starting to be thought of as new ways of doing things. In many cases JP was the reason people wanted to work for DrKB, he was the man behind OpenAdaptor released in 2001. He was driving open source in the bank before most people knew what it was. He stopped paying Microsoft and bought hundreds of Macs for his developers. The developers left other banks to work under JP. Because he had such high quality staff he was able to reduce head count and effectively cost. You really need to watch this if you're into open source or work for a bank. -John-

  2. Back to top

    qutie enjoyable

    Mar 12, 2007 5:55 PM by Stuart Charlton

    My favorite moments (around the 40 minute mark)... - Three pieces of advice for architects: Don't actually write an enterprise architecture, it's too controlling and stifling ("I'm proudly accused of not having one"), don't write hard policies & guidelines ("you must [instead] have principles that are flexible"), engage with the teams ("The architect is the de facto project manager. It is not an ivory tower job."). - Cameron asks, "What are the biggest factors that contribute to project failure?" Without hesitation, JP says, "an unwillingness to say 'no' to the customer."

  3. Can this article be reproduced in a podcast / text form so that it can be acessed in full-text form?

Exclusive Content

Rustan Leino and Mike Barnett on Spec#

Rustan Leino and Mike Barnett of Microsoft Research discuss the technology in Spec# and its futures.

10 Ways to Screw Up with Scrum and XP

Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.

Tips from a Top Sports Team Coach

This article outlines 9 principles Marc Lammers discovered while building the world’s best field hockey team, mapping them to software development practices.

SOA Governance: An Enterprise View

Michael Poulin explains the necessity for SOA governance to ensure an Enterprise SOA's success, relying on concepts from the OASIS SOA Reference Model and Reference Architecture.

Developing Portlets using JSF, Ajax, and Seam (Part 2 of 3)

This article covers setting up a RichFaces portlet using JBoss Portlet Container and JBoss Portlet Bridge, deploying a RichFaces portlet, and RichFaces capabilities.

Scalability Worst Practices

This article discusses scalability worst pratices including The Golden Hammer, Resource Abuse, Big Ball of Mud, Dependency Management, Timeouts, Hero Pattern, Not Automating, and Monitoring.

Do the Hustle

Obie Fernandez shares his experience selling consulting services for both Thoughtworks and Hashrocket and give tips how Ruby developers can work with clients.

Natural Laws of Software Development - Deriving Agile Practices

Jeffries and Hendrickson derive Agile practices from the natural laws of software development. They don't just say "Be Agile!", but they explain why Agile practices make perfect sense.