That O365 Guru from Cape Town (#NadirKamdar)

This article is a continuation of Part 2 - Please read that article first. Phase 3: Development   In the development phase, the solution is built according to the specifications defined by the architect (As defined in Part 2 ).   The development phase requires 2 key players, the SharePoint Administrator and the SharePoint Developer.  Yes - this is two different roles with two different skill sets.  You may want to add SharePoint data-capturer to the list so basic tasks like deploying a taxonomy and site population can be completed by a cheaper resource, allowing the higher skilled resources to spend time on more complex requirements. The SharePoint Administrator The SharePoint Administrator focus is on the setting up, configuration and management of services running on SharePoint.  Anything available "out of the box" from SharePoint can be deployed by the SharePoint Administrator, which should be at least 80% of the entire solution.  (If anything less than 80% of the

This article is a continuation of Part 1 - Please read that article first.   Phase 2: Planning After the Envision Phase is completed, the Planning Phase starts, that requires a different set of skills. If the Envision Phase is all about "What the Organisation wants", then the Planning Phase is about  "How are we going to give them what they want". Successful projects (SharePoint or otherwise) places a lot of time into planning, on average, 20% of your entire project should be placed in the planning phase, if you get that right, the future phases is just about applying the plan. The experts needed for this phase are as follows: Project Manager Business Analyst SharePoint Architect Infrastructure/network administrator Database administrator SharePoint Designer Steering Committee From the last phase, the Business Analyst would have defined the scope and document what the organisation wants.   In this phase, the SharePoint Architect