Jeff Teper, Corporate VP; Kirk Koenigsbauer, GM
- Question: A follow-up to a response during Steve Ballmer's keynote that was somewhat evasive. My follow-up here this morning was:
- What architectural change has been implemented within SP 2010 so that clients can expect quicker release cycles for application layer capabilities vs. lower-level infrastructure/platform modifications?
- What development life-cycle change internally was made to support a faster cycle-time (vs. 3-3.5 years between releases now)?
I'm left thinking that we will be talking about SharePoint 2013, SharePoint 2017 and so on - a release cycle of 3-4 years - even with Cloud/SaaS and BPOS. Should business and IT decision makers pause for a moment and take a long-view perspective on SharePoint over time.
While there is a level of irrational exuberance right now at the conference given all the changes in this release (there is a lot in SP2010 to like), business and IT decision-makers should think long and hard about committing too much of their business to this type of slow-moving platform infrastructure since Microsoft seems incapable or articulating how this release is a more adaptive platform for Microsoft itself to deliver capabilities more rapidly in response to customer needs.
For instance - even with this release there is still a lack of parity between on-premises and BPOS. As you listen to some Microsoft execs is sounds (not all the time but often) that SaaS follows on-premises vs. having BPOS as a first-class release target (that SaaS will "catch up to" on-premises) - I could be off here - but that's my perception. Microsoft still seems to be reacting to the Cloud from a SharePoint perspective versus treating it as a peer. And this gets back to the development life-cycle internally.
The other angle here is mobile - mobile seems to be consistently marginalized or treated as an after-thought. Responses are somewhat flippant and seem to avoid discussing much more popular platforms like iPhone and Android.
Perhaps there are certain solution domains that should NOT be on SharePoint if those solution areas require more business agility in the market. One space where this might be true is the social computing area as an example.
The eggs, bacon, and sausage however were excellent.