I like SharePoint, it is not a love-level relationship but it has matured definitely to the like stage. Through this and future good-intention blogs, I want to put down what I think are some pretty cool ways to use SharePoint and just as important, some good ways to use the tool.
If you are reading this and have never used or heard of SharePoint, go onto some of my other postings on this website. Unfortunately SharePoint is kinda hard to explain and so therefore I will assume that you know about the following things:
- Its general architecture (e.g. there are farms, sites, sub-sites, lists and items)
- Its typical structures (lists, libraries, workflows, webparts, pages, search, etc.)
- Who uses and how access is managed (e.g. super-administrators; site-administrators; users with contributor, read and other access)
If any of the above is makes you go huh?, sorry I can’t help you but I can point you in the right direction:
- Wikipedia has a good over-view description.
- Read the Microsoft Sales Stuff.
- Take a course, there are lots out there including those from Microsoft.
- By a book, Chapters or Amazon sells lots, and
- Most importantly – start using it!
How Not to Use SharePoint
… but before you start using SharePoint, here is something to recognize about how not to use SharePoint. Don’t use SharePoint as a glorified Network File System. It can do so much more, so why do so many people do so little with it? Hopefully the next few blogs will give you just some examples.
How to Use SharePoint
In my ongoing effort to remember what the heck I have done, I have the good intention of writing a series of blogs about some cool uses of SharePoint (and associated technologies). Check back to read about cool stuff or to see a post of shame of good intentions gone bad.
- SharePoint Wikis as a Desk Reference Tool
- Creating ‘HOW-TO’ Pages.
- (Infra)structure Pages.
- Desk Reference Standards.
- Data Dictionary (of SharePoint and other stuff)
- Looking up a Look Up of a Look Up
- Managing Sites, Structures and People (a poor man’s content management strategy)
- Using SharePoint as a Budgeting Tool
Business Case Example
I have used SharePoint for a variety of uses including:
- An internal facing team-site with a handful of users having access
- A highly restricted decision making site with very sensitive information
- A status reporting system for dozens of project teams who in turn need to consolidate their work into a few sentences for an executive office
- A ministry briefing binder in which hundreds of documents were managed that had varying degrees of sensitivity and right of access
- Widely available budget site in which budget clients uploaded their working papers for consolidation
- A project site composed of numerous teams working on a complex system transition
For the purposes of this and other blogs, I will use a fictional example of a budget site in which internal clients need to submit content and documents. This example will centre around a government organization and specifically one that primarily manages projects but also manages contractors, contracts and staff.