Not long ago, if the corporate brass wanted to change major functionality in a big piece of software, the IT delivery time might be six to 12 months, maybe longer. Once upon a time, that was acceptable. Not today.

Thanks to agile, many software changes can be delivered in, say, six to 12 weeks. That’s a huge improvement, but not huge enough. Business imperatives might require that IT deploy new application functionality in six to 12 days.

Sounds impossible, right? Maybe. Maybe not. I had dinner a few days ago with S. “Soma” Somasegar, the corporate vice president of Microsoft’s Developer Division. He laughed—and nodded—when I mentioned the need for a 30x shift in software delivery from months to days.

After all, as Soma pointed out, Microsoft is deploying new versions of its cloud-based Team Foundation Service every three weeks. The company has also realize that revving Visual Studio itself every two or three years isn’t serving the needs of developers. That’s why his team has begun rolling out regular updates that include not only bug fixes, but also new features. The latest is Update 2 to Visual Studio 2012, released in late April, which added new features for agile planning, quality assurance, line-of-business app development, and improvements to the developer experience.

I like what I’m hearing from Soma and Microsoft about their developer tools, and about their direction. For example, the company appears sincere in its engagement with the open-source community through Microsoft Open Technologies. (I’ll confess to being a skeptic, though, based on Microsoft’s historical hostility toward open source.)

Soma said that it’s vital not only for Microsoft to contribute to open source, but also to let open-source communities engage with Microsoft. It’s about time!

Soma also cited the company’s newfound dedication to DevOps, adding that future versions of both on-premise and cloud-based tools will help tear down the walls between development and deployment. That’s where the 30x velocity improvement might come from.

Another positive shift is that Microsoft appears to truly accept that other platforms are important to developers and customers, and that the answer to every problem cannot be to use Microsoft technologies exclusively.

Case in point: Soma said that fully 60% of Microsoft developers are building applications that touch at least three different platforms. He acknowledged that Microsoft still believes that it has the best platforms and tools, but, “We now know that developers make other choices for valid reasons. We want to meet developers where they are,” that is, engaging with other platforms.

Soma’s words may seem like a modest and obvious statement, but it’s a huge step forward for Microsoft.

Alan Zeichick is editorial director of SD Times. Read his blog at