SharePoint Application/Content Lifecyle Management anonymous survey

July 29, 2009

So I’ve repeatedly been questioned by various clients, user group members, SPDevWiki consumers and Twitter followers about this area and figured I’d gauge the landscape by doing a survey much like I did with the SharePoint Implementation one.

If you are a Microsoft Partner/Integrator please fill in this case study in the context of one of your clients. Some of the questions relate to size of the organisation for example.

The survey will take about 10 mins of your time.

image

The results will be published on the SharePointDevWIki just like last time with all of the questions graphs published. I will then do a more detailed analysis of this shortly afterwards.

I would appreciate any RT’ing on Twitter, blog posts on this to spread the word as this is important for the SharePoint community and will gauge your clients and own maturity in this space.

“Content management, or CM, is a set of processes and technologies that support the evolutionary life cycle of digital information. This digital information is often referred to as content or, to be precise, digital content. Digital content may take the form of text, such as documents, multimedia files, such as audio or video files, or any other file type which follows a content lifecycle which requires management.” WikiPedia

The SharePoint Platform is the next step forward in Content Management because it allows Organisations to reuse common framework patterns developed by Microsoft rather than developing their own. Never before have the boundaries of the ownership of elements been so hard to define and manage within an Organisation.

Applications have often been built on a bespoke basis, using ASP.NET and SQL technology stack, where the separation between the content and the system are easily defined by architectural layers and the roles that create them. SharePoint has blurred this separation by allowing the architecture of systems and management of content by Information Workers within the same interface without the need for Solution Architects and Developers. This can often be compared to the same issues raised by Microsoft Excel and Microsoft Access solutions designed by Information Workers in the past.

“Application lifecycle management (ALM) is the marriage of business management to software engineering made possible by tools that facilitate and integrate requirements management, architecture, coding, testing, tracking, and release management.” WikiPedia

Traditional Applications typically followed a more structured software engineering process called Application Lifecycle Management. With the power being given to the Information Worker by default with SharePoint, control of the Systems has left the hands of the IT team and moved into a more uncontrollable state of typically untrained individuals.

The main challenge of using the SharePoint Platform is often how an Organisation governs both Content Management and Application Lifecycle Management. The Microsoft MSDN web site has many disperse articles on this this topic and this survey will hope to identify common issues across implementations.

diigo itdeliciousdiggfacebookreddit

Comments

blog comments powered by Disqus