Project Management

PMO Collaboration: Sharing with SharePoint

From the PMO Setup T3 - Tips, Tools, and Techniques Blog
by
Bringing you PMO Setup Tips, Tools, and Techniques for PMOs of all shapes and sizes.

About this Blog

RSS

Recent Posts

PowerPoint Presentation Tips

Planning tips from a mouse..!

Fool me once shame on you, fool me twice shame on me..!

Project Manager Knowledge Areas

Who is to blame when a project fails?

Categories

PMO 2.0, PMO Architecture, PMO Leadership, PMO Setup, PMO Tips, PMO Value

Date

linkedin twitter facebook Request to reuse this  

Categories: PMO Tips


Sharing (noun) / having or using something that other people also have and use at the same time.
 
PMO Comics, by Mark Perry
 
Does your organization have SharePoint or a tool like it? Often times, the excitement of moving away from all those network file shares to a collaboration platform soon diminishes as without just a bit of planning and policy your collaboration platform can quickly grow into a jungle of various and sundry teamsites and document folders that even Indiana Jones would have difficulty navigating through. Soon enough, users may even resort back to the use of those network file shares or even sending their files to each other via email. Below are a few SharePoint tips to avoid that.
 
  1. Understanding how SharePoint fits into your PMO. SharePoint is a Microsoft offering that provides the server infrastructure to support needs that information workers have such as collaboration, document storage, and the ability to inform others and to be informed by others. While understanding the technology and features of SharePoint is important, understanding how SharePoint fits within your existing PMO and how it can be used by all those involved in support of executing the best practices of the PMO is even more important.
  2. Identify and replace disparate repositories. Many organizations have disparate repositories for storing information that quickly erode into a collection of information dumping grounds. Seek to identify and replace with your SharePoint the following kinds of disparate repositories:
    • Documents, spreadsheets, and images stored on PC hard drives
    • Documents, spreadsheets, and images stored on network shares
    • Reference materials stored in three-ringed binders
    • Calendar appoints and todos stored on cork boards
    • Archived files stored on Zip drives and CDs
    • Links for web resources found in a user's My Favorites folder
    • Flip charts and sticky noted from brainstorming sessions and meetings
    • Worker knowledge stored in the heads of subject matter experts
  3. Accessing structured assets with SharePoint. Structured assets are found in the databases of the formal systems of the company. Though it is easy to query and aggregate data from these systems, accessing these systems is often difficult to do and it can be challenging to teach busy executives how to login, navigate menus, and run reports to get the information they need. SharePoint makes it possible and easier to control and customize access to these structured assets as well as to consolidate data that comes from multiple back-end sources.
  4. Managing unstructured assets with SharePoint. Unlike structured assets, less structured assets such as Word documents, Excel Spreadsheets, PowerPoint presentations, Visio workflows, etc, are not usually stored in databases. Contrary to what IT staff may think, these assets are stored in more locations than just file servers such as PC hard drives, email folders, removable media, as well as printed and stored in filing cabinets. By providing a manageable environment for less structured information, SharePoint enables and makes it possible to standardize, share, archive, backup and restore, secure, audit, analyze, and legitimize the unstructured assets of the organization.
  5. Use SharePoint as the hub. Companies make significant investments in people and technologies. With IT staff already overburdened, it is not surprising to find little support and enthusiasm for implementing yet another complex, high maintenance vendor application. The result is that many users, despite all the advances in systems and technology, find themselves increasingly alienated and isolated from their companies information environments. Most end users will tell you that there is a missing link. Using SharePoint as a hub solves this problem and provides users with access to their information assets.
  6. Continually sell your SharePoint. When you and your team discover new features, capabilities, and uses of SharePoint, don't be surprised if everyone else doesn't see the same value that you do. Take the time to show and explain the business value of SharePoint. Seeing is believing and often your users have to see SharePoint in action to understand its value over business as usual approaches.
  7. SharePoint isn't right for every organization. Be open to the fact that SharePoint isn't right for every organization. If you have difficulty getting people to cooperate with you or to see the value in SharePoint as a collaborative platform over other alternatives, then you and your organization may be best served by waiting until the winds of change come through. Since it is very difficult to prove the value or push a new way of thinking, be prepared to plant new ideas and be ready to act upon them when the time is right for the organization to fully embrace the change.
  8. Using lists with Excel and Access. Quite often, individual departments use spreadsheets and databases for analyzing and keeping track of data. And just as often, the information technology department is completely unaware of these things. As a result, IT may have a problem when a department's spreadsheet stops working or when a department outgrows its database. SharePoint provides extensive features for integrating with Excel and Access such as creating one-to-one relationships between spreadsheets and databases to SharePoint lists providing a natural repository for working with tables, rows, and columns.
  9. Managing business processes using workflows. Managing a PMO is all about managing processes and many of these processes are mostly manual. SharePoint provides extensive support for managing organizational processes by using workflows. SharePoint can generate tasks and other kinds of list items to drive movement through the workflow. Rather than keeping all the information about processes filed away where few people will take the time to find and read them, SharePoint has a workflow feature that triggers and tracks the processes associated with your documents.
  10. Using Portal Sites. SharePoint 2007 provides a new kind of site template called a portal site template. The portal site template lets you define a hierarchy of sites such as a PMO site and project sites that can all be created at once. So, rather than creating project sites one at a time with site templates, portal site templates create a set of multiple sites that are intended for use together.

As always, if you have a SharePoint tip or two, share it here..!


Posted on: March 20, 2008 10:52 AM | Permalink

Comments (5)

Please login or join to subscribe to this item
bgkeen
Thanks. This is a nice overview of questions to start. I am trying to find the "right" collaborative technology that I can get behind and suggest to my clients and work teams. SharePoint is popular and probably the most "sellable" to my current client. But these are questions that can be used for all.

avatar
Randy Bennett sr proj mgr| fiserv Collegeville, Pa, United States
My company uses Sharepoint as a tool to collect all relevant project and product (we are a software house) infromation. SharePoint is no Lotus Notes, but once learned is relatively easy to navigate. However things got interesting as we implemented Microsoft's Project and Portfolio Server 2007. PPS 2007 comes with a limited license for SharePoint 2007. Suddenly the workflow features of SharePoint 2007, including electronic "signatures" seized the attention of senior management. My next project after PPS implementation is going to be the SharePoint 2007 installation and migration. Maybe workflow is the feature that will work for you and your clients too.

avatar
Joe Baker PM III| Cambia Health Solutions Vancouver, Wa, United States
I've used SharePoint as a project ''''hub'''' for managing communication, coordination, and information transparency for active projects. Combined with the other Microsoft suite of tools for communication and collaboration (Outlook, LiveMeeting) it lends itself quite nicely to a project hub/central clearing house type function. Like everything else you need to have put a lot of thought into structure and governance before turning it loose on your general PMO population. It can be just another out-of-control information dumping ground if you let it.

avatar
Peter Heydt Sausalito, Ca, United States
Love to know if there is a good template for keeping track and managing project documents on a SharePoint basis. Categories to include, Name, Purpose, intended audience, internal external, version, next version. Use for Sales, use for technical API, Sales material, Project plans, etc. More or less a change management control mechanism resulting in just-in-time access to up-to-date documents for multiple purposes.

avatar
Howard Lai PMP, CEng, CPEng, NER, IntPE(Aust), RPEQ, MIET, CSSBB, CISA, ISO9001 LA| QH Brisbane, Queensland, Australia
My company also aims to use SharePoint as a "Hub" to collaborate different project documents. More than that, ShrePoint's workflow engine is quite attractive for our company, which is a less costly solution than K2, and is a proven solution. I believe SharePoint will become more and more popular for PMO collaboration.

Please Login/Register to leave a comment.

ADVERTISEMENTS

"There is a theory which states that if ever anybody discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable. There is another theory which states that this has already happened."

- Douglas Adams

ADVERTISEMENT

Sponsors