So finally I get to talk about the large “High Test or Super Octane” projects and tools! Most organizations will have only a few of these projects or maybe they will have a program that is a collection of many projects being managed under one team or PMO.
Even though there are not a lot of these types of projects or programs in an organization, they tend to be the strategic, highly visible and large staff projects. The need to manage them correctly is driven usually from both a cost and strategic perspective. These projects are often called the “career killer” projects — because if you don’t get them done on time and within budget, you may be looking for a new job.
Here are the characteristics of these types of projects:
- Large, strategic project
- 30+ full-time staff
- Long duration — 12 to 24 months
- Full time PM (Or perhaps more depending on the size and scope of the program)
- Needs rigor and Project Management tools to develop and track
- Charter and budget
- Project management plan
- Detailed schedule
- Risks and issues
- Quality plan
- Cost controls
- Status reports with metrics
So there are many tools and products on the market for this level of project management —many times they are called Enterprise Project Management (EPM) tools. Companies like Microsoft (Project Server), Computer Associates (Clarity) and Oracle (Primavera) have products exclusively aimed at assisting with these types of projects and programs. I will speak to the use of Microsoft Project Server 2010 for illustration purposes.
As the name implies Microsoft Project Server® is the first capable version of Microsoft Project® residing on a server along with a web based interface (SharePoint) that allows most team members access to the functions they need (Note: It does not have all of the functionality of the desktop version so a professional PM will still use MS Project Pro with Project Server). Project Server also works in conjunction with the desktop application, MS Project Professional, to provide a seamless experience for the PM. The major advantage of this arrangement is the ability to view and organize data across multiple projects for effective portfolio management. Microsoft Project Server is an enterprise and portfolio tool suite that:
- Works with Project and Office
- Has a web-based user interface
- Allows “cradle to grave” tracking for projects
- Shows status across multiple projects and global resource pool
- Supports typical project management work products such as:
- Project sites, libraries, collaboration and schedules
- Repository for all artifacts
- Timesheets and assignments
- Facilitates portfolio analysis and report generation
- Provides real-time data for decision making across multiple programs
Choosing an EPM tool, like Microsoft Project Server, requires an organization-level commitment. The utility of Project Server can be realized only when the resource, schedule and document information is updated by all project managers and used to allocate resources and make decisions. An organization’s commitment to Project Server requires a higher upfront cost than Microsoft Project or Excel, and training for PMs, portfolio managers and business analysts in accessing and using the reservoir of available information.
In my experience, the additional cost of Project Server is justified when:
- Projects are large and of strategic importance to the organization
- A single project employs 30+ full-time staff, some of whom may be in remote locations
- Projects last more than 12 months and may extend to two or three years
- The organization needs to compare status and outcomes across multiple projects in order to make the best resource allocation decisions
Here are a few examples of using Microsoft Project Server:
Individual projects can use Microsoft Project Server to generate status reports using established templates that access current information on key project metrics, such as planned versus actual costs, risk and issues status and resource utilization.
Project Management Offices and senior decision makers can see at a glance, the development stage of all suggested, proposed or ongoing projects.
And, portfolio managers can track the status and issues of all their projects on one page.
Overall I find that Microsoft Project Server meets my needs completely in managing a large project and consulting with companies on creating an effective PMO. Most importantly, I believe that the inherent collaborative nature of Project Server® (because it uses SharePoint® ) helps keep project team members on the same page and provides individuals with a knowledge that ranges from their current task list to how their project fits within the greater organization. To summarize:
Pros of Microsoft Project Server:
- Uses Web browser for most functions — since employees already know how to navigate and use a browser, this saves on training and orientation time.
- Central repository for all information — as previously discussed in Finding a Content Management System solution – Part 1
- Works well with other tools (Office, Project, etc.)
- Multi-User data — this ties the team together through facilitating communication and creating a common project picture
- Single Resource pool — helps solve resource management challenges because tasking and capabilities are in one location on the server
- Process and Workflow enforcement — tracking key metrics across multiple projects
Cons of Microsoft Project Server
- Cost (Initial setup and on-going administration required)
- All staff must utilize and update information in order to have complete picture
- Training is needed initially to maximize the investment in the tools
So do you have thoughts on the tools your organization is using for managing large or “High Octane” level projects?
Next week I will talk about a Hybrid tool approach to managing projects.
May 19, 2012 at 2:34 pm
I have heard of Microsoft Project, of course, but not Microsoft Project Server so thank you for providing an overview. Does it take a long time to get it setup and the a team using it successfully if the product is new to the organization?
June 23, 2012 at 2:52 pm
[…] So, you’ve heard of Microsoft Project Server, right? Do you know what it is? Do you know the guidelines for when it should be utilized? Bruce McGraw answers these questions in a recent post on his blog, Fear No Project. […]
May 15, 2014 at 10:18 pm
[…] Part 4 – Tools for Large Projects […]