SharePoint in the Real World - Information Management - Analysis

Especially when dealing with content management need to know about INFORMATION.

Don't believe me, but believe the MCP's of the world and believe all those (big) technical driven implementations that failed.

You really need to know your information and how it is organized:

• What information will your intranet, DMS, BI solution, etc contain?
• Who will be using it and how?
• How do they access it (...and find)
• When do they need it

Microsoft set up some starter worksheets that WILL help:

• Windows Sharepoint services 3.0 
• SharePoint Server 2010
• SharePoint 2013

I suggest you use this information and implement in the mother of all enterprise applications: Excel (or even better in a database). Why?

[Sarcasme]

• Maybe you want to modify your information structure at some point… where within our 1.000 sites did we use this site column? ;-)
• What happens when we modify our taxonomy?

[/Sarcasme]

So again:

Analyse the information that you will put into your SharePoint environment. Write it down and publish it to the people involved.

Information Management - The Series

SharePoint in the Real World - Information Management

I've been playing around with this new blog and this thing is so complex that I decided to create several blog post for this one. 

• Information management - Findability & Data
• Information management - Analysis
• Information management - Deployment
• Information management - Maintenance

The above is certainly not carved in stone. I'm not totally convinced that Deployement and Maintance will become different blogs. Maybe I'll group them. maybe I will add more..and maybe the above will prove just about wright!

Findability & Data

Findability & data is all about how users find the data they need, what data it is that they need, how they are going to use it and why. This information is crucial for the steps to come.

Analysis

Analysis is all about analysing the information & business requirements. In this blog I'll write how I go about determining the requirements and validating them to the conceptual, logical and physical architecture. (I think I will also need to explain about the conceptual, logical and physical architecture)

Deployment

Okay, analysis is done! We are ready to create and deploy this stuf! Cool, but how are we going to do that?

Maintenance

As a wise man once said: WHOOHOO we deployed it and everything is fine we can go home and die - or do something else :-). Nooo some user wants to change my beloved configuration! Now what? Maybe we'd better think this through before hand. That's what this blog is going to be about. Planning for change and how change effects your environment, time-2-market and what not.

I really hope you guys and girls appreciate the effort and give me some feedback!

Regards,
GH