If you haven’t checked out some of the launch sessions, take a peek. Mary Jo Foley disclosed some of the “behind the scene changes” that occurred to make the Microsoft's 'Cloud OS' a reality (Windows Server 2012). This is the type of information that you don’t get a chance to simply read in some release notes or product docs somewhere. I highlighted a few which I thought were pretty important below.
· Establishing and executing on a single “Microsoft's 'Cloud OS' vision and strategy. Can’t imagine how many individuals were involved in this massive effort but in the first session titled Built from the Cloud Up by Satya Nadella http://www.windows-server-launch.com/ . He states this is the biggest release ever with 4 years in the making.
· 1 year hiatus from writing code and spending it “revisiting the market”. “Microsoft created a number of sub-teams: The Voice of Technology team (investigating what was going on in the industry); a Voice of the Business team (investigating where the markets were headed); Voice of the Experience team (discerning pain points in data centers around the world); and Voice of the Customer team (systematically recording customer needs and requirements). The Server team also assembled its code check-in tools, quality tools and process tools during these first few months”.
· Organizational changes with merging the Windows Azure and Windows Server Teams and creating a unified Server and Cloud division. I personally don’t think this could have been achievable if this type of change didn’t happen. Why? When you’re divided you tend to strictly focus only on the things you’ve focused on in the past. Windows Server’s roots were of course based on an on-premises platform so I can just imagine the fun these teams especially management had when they were initially assimilated.
Kudos to Microsoft for pulling this off as it was no easy feat by any means. If you haven’t checked out the launch sessions, you really should! I’m really looking forward to seeing the adoption and how we can continue to complement Microsoft’s platform whether customers leverage it in a public, private or hybrid deployment scenario.