通过

SharePoint 2010 - Delivering on the Promise

  • 项目

My name is Jim Masson, and I’m the Group Program Manager for the Enterprise Content Management team within SharePoint. My team is part of the engineering team, and is responsible for designing the features around content management, including managing documents, web content, rich media assets, records, and a new service for managing shared content types and taxonomy.

With the coming launch of SharePoint 2010, this seemed like a good time to ramp up the ECM team blog, and start a conversation about the SharePoint 2010 release. In the lead up to the offical launch of the product and beyond, various members of the team will be posting details about the major feature areas and features within ECM in SharePoint 2010, including design overviews, walkthroughs, best practices, and eventually interesting case studies. I hope you will subscribe and participate with us in the conversation

ECM For the Masses

When speaking with customers about the content management features in SharePoint 2010, we often refer to the release as being about ECM for the Masses.  I wanted to take this first post to outline a little bit about our approach to designing and building SharePoint 2010, and how that has helped us deliver on that vision.

When the team started building 2010, we came up with 3 pillars that drove our investment decisions, and really helped to define the release. These pillars represent design principles that we would apply to each of the feature we built to help us focus in on delivering ECM for the masses. We call them the 3 E’s of ECM, and they are:

  • Enterprise Ready – This is all about ensuring that SharePoint more easily scales to the amount of content the largest Enterprises deal with and delivers consistently high performance and reliability at any scale. In addition we provide the feature depth, customizability and extensibility that Enterprises need to support the full breadth of business scenarios around content.
  • Easy to Use – Our focus here is on 2 audiences. First, the features must be Easy for the Information Worker, with best-in-class usability, providing supreme user acceptance and speeding deployment and adoption. Second, the product must also be Easy for IT, providing great functionality OOB that is fast to deploy and easy to manage at the Enterprise, Divisional, Team and Workgroup levels.
  • Everyone Participates – This is all about ensuring that Everyone in the organization has access to and benefits from the functionality offered by the ECM features – not just a few specialists who have been specially trained, or for whom the organization can justify a high per seat price. This also means that the capabilities can be adjusted to suit the needs of everyone in the organization; from minimal interaction to highly structured and complex workflows – everyone sees exactly as much as they need.

It is my hope that, as we go through the features over the next several months that you will see the impact of those pillars on the product, and how they have helped us to deliver ECM for the masses.

Comments

  • Anonymous
    February 20, 2010
    Hi Jim, thanks for your informative posting. The 'document set' feature seems very welcome in a government- or enterprise setting where repetitive products or outcomes ask for case-files. In MOSS2007 metadata-based virtual files were posible, but they were also lacking sevral neccesary features (retention, batch-move  or -copy operations, group-send to archive, etc.) Is the new 'document set' feature the solution to this problem? Cheers, Eric