You have 6 months to design, build and deliver an Intranet based on SharePoint 2013 for a dynamic marketing company. You can only employ three people. Which three would you choose from the list below, and why ? You may give several answers, for different assumptions 🙂
- SharePoint Architect
- SharePoint Consultant
- Project Manager
- Business Analyst
- SharePoint Developer (Heavy on code)
- SharePoint Developer (Heavy on OOTB or third party tools)
- SharePoint Administrator
- Web Developer heavy on Javascript, CSS, graphics design
- SQL Administrator
Win-an-eBook Wednesdays is a small three day contest that we hold every week. The Prize? An O’reilly eBook for your choice! Furthermore, if you win, you also get the chance to ask the community whatever question you want and be the judge for next week’s contest!
This week’s judge is Peter Ridgway-Davies winner of last week’s contest!
You have until Sunday, May 12th (10pm GMT) to answer this question!
This depends on several factors, is it SharePoint On-premise or Online? What is the scope of the Intranet, information? Social Networking? Employee Self Service business processes? If you are developing an intranet portal from scratch you would need most of resources listed. If you are using SharePoint Online, you do not need the SP Admin. Probaby don’t need SQL Admin either. The most important resources are those that manage and create content, which are not listed here. Also, management who must provide the vision of what they want to convey.
Now if you took a different approach, that of using a template to start with the picture changes substancially. We have over 50 clients who have used our Intranet Portal template to deploy their Intranet. Typical time to deploy and setup – a few weeks (mostly for content generation). SP Intranet (part of SP Business Suite) can be used Turn-key or as a Template. It comes out of the box with the ability of the client to configure it to their needs, pick a branding skin, and easily add their own content. It eliminates the need for many of the resources listed. No Web developer, no SP Administrator, no SP Developers. What you still need is a business analyst, and a SharePoint power user as an application admin. Most important, you need the content providers.
This approach allows the organziation to concentrate on content not development. See client examples attached.
Darrell Trimble