When getting an organization to make an investment into using SharePoint (irrespective of premise i.e. on-off, or SharePoint version), a SharePoint Feasibility Study should be carried out for them. A Feasibility Study identifies the following:
- What are the current information and management challenges? What needs to be put right?
- What are the alternatives (including ways to achieve those objectives), including costs and benefits of each?
- What is the recommended solution, which not only gives reasons for choosing the option but also discusses its feasibility? (how difficult will it be to carry out?, and will the recommended solution meet all the requirements).
(more…)
Using SharePoint, organizations should be leveraging every asset which makes them more productive out of the platform, and as effectively as they can. This means investing time and resources to make sure users are fully utilizing the functions made available to them; especially the capabilities that can help them more productive and meets their objectives.
(more…)
User Adoption of SharePoint is based on meeting the goals and requirements of the business sponsor. To do that, there is an importance in ensuring that the correct features are applied to the relevant solutions to meet their goals. Platform Governance is key; since there would need to be knowledge of the relevant features and an understanding therefore in how they would be implemented, supported, maintained in an evolving SharePoint landscape. This is particularly important in deciding on the migration path of SharePoint 2010 to 2013, since quite a few features have been enhanced.
(more…)
One of the most difficult migration paths for SharePoint is from version 2007 to 2010. Not so much due to the technical requirements concerning things like content database shift, Web Application shift, Site Collection review, Third Party review. But more on the actual sequence of events, which if not worked out completely could leave people attempting to go this in a pickle! To help, I’ve provided a map which I have used with several customers which allows me to produce key documentation and at the same time keep them involved in the process.
To assist the map, there are two project plans attached in 2007 / 2010 / 2013 formats, which allows you to set time-frames against each of the sections.
Note that these are generic. You must use your own judgement concerning things like Third party products (and what you wish to do with them), what must happen to content on the document lifecycle trail (i.e. old sites, archived content), and what must happen to any control processes surrounding things like security (who should have access to the new world).
This is particularly related to testing, and again, you should adopt a generic approach first then tailour it to your own requirements. Read through my Verification and Validation article to give you ideas of what should be in your testing plans (which will encompass technical and non-technical concerns).
The outline below is in collapsed state. Click the + icons to expand each section, and – icons to compress. if the view of the map outline is too small, you can view the full screen by
going here
A major important milestone in the step to get information workers creditations in the use of Office products. Just last year I completed the SharePoint Study guide for Microsoft Office, and now in not the too distant future (in fact in late August to be precise), Office 365 will get an exam study guide. In fact, the author happens to be my co-author for the brilliant study guide for Office 2010 (including SharePoint of course!).
This is I think a major move on the part of Microsoft who are keen to ensure that educational establishments, armed with the free offer of Office 365 will now also be able to offer courses, examinations and creditations for information workers to place on their CVs, and shout to the world they are proficient in the use of Office 365! (more…)
