Wednesday, March 7, 2012

Project Server 2010 - To implement or not implement? That is the question.

It comes down to what Project Management maturity your organisation has or wants to achieve. Project Server is an 'Enterprise Project Management' system so it is designed to provide a suite of business benefits to an organisation. For example:
  • Data Visibility across the entire portfolio of projects across the organisation
  • A uniform and consistent approach which conforms and compliments your organisational Project methodologies and processes
  • Demand Management
  • Resource Management (Capacity and utilisation reporting)
  • Project Team collaboration capabilities. (Project site, list registers, security model, document management capabilities, version control, alerts, search, etc...)
  • Portfolio Management (Ability to assess projects against organisational strategic drivers, perform what-if scenarios and project selection processing)
  • Schedule Management (Work break down structures, cost, duration, work, timelines, etc...
  • Business Intelligence and Reporting Capabilities (SQL reporting, OLAP cubes, several reporting tool options for designing reports)
  • Time management and task status reporting from project team to project managers
  • Ability to create custom project workflows to guide project managers through the project lifecycle
  • Robust and flexible security model
SharePoint Server 2010 Enterprise edition is a pre-requisite for Project Server 2010 so in addition to all this you also get the full set of SharePoint enterprise features to take advantage of. A bit of Bing/Google Kung-Fu will explain all this in detail. Bottom line is this is a serious enterprise project management solution for any organisation out there wanting to increase and streamline their Organisational Project Management Maturity. Whilst this level of project maturity is the ultimate destination for an organisation, it does however take a huge amount of effort and commitment for it to succeed. It is not a turn-key solution. It is a business enabler. In my opinion, completely worth the investment! With the enhancements made to Project Server 2010 it is now positioned to be a ‘Big Boys Toy’ and also the reason for it being one the leading EPM solutions available on the market today.


Agree or disagree? Feel free to make comments below and share your views on this post.

2 comments:

  1. You ask the question: To implement or not implement? but only give reason to implement.

    What are the negatives?

    ReplyDelete
  2. Fair Comment. I hadn't really interpreted it that way as it was more of a playful title but I see your point. Clearly I'm a BIG advocate for implementing an Enterprise Project Management Solution as there are so many good reasons for implementing this sort of software and process. As for negatives hmmmm let me think…
    • It’s hard to work to get it right and implement successfully but same goes for any EPM system.
    • Don’t be fooled that the software is a turn-key solution for dealing with what is often an issue with business process, change management or internal politics. The tool is merely designed to complement and structure that process
    • Once you implement the software, don’t be fooled that the project has now been completed and you can pack up and leave it running without any maintenance. This is the most delicate part of the project where careful planning must be taken in the change management and on-going support and maintenance in which will be required as the tool continues to evolve and mature.
    • Don’t bite off more features than you can chew with the initial roll-out. Implement only the sets of features which your organisation is ready to use or can cope with. This is a continually evolving process which the organisation needs to grow into. Set out the business benefits and priorities to form an EPM road map.
    • Users who have never been asked to do certain things who will now have to as a result of implementing this solution will make all excuses under the sun to get out of using the tool. Watch out for these sorts of users who are rallying their peers to bring the system down with their pitch forks and torches. Again, the change management of the project is essential in preventing/reducing this scenario.
    • If you are a small organisation then this product is most likely going to be overkill. Project Server 2010 now requires a SharePoint 2010 Enterprise platform, gathered with a SQL Server so licensing will be a problem for small business. Licensing for larger organisations will find this to be reasonable compared to some of the other competitors aorund. There are a few products out on the market for low maturity Project Management solutions. I’d even say look into MS Project on its own which can still handle Program management. Even using SharePoint Foundation with MS Project and allowing the ability to synch the project schedule tasks to a SharePoint list could significantly lower licensing costs for small business.

    How about yourself? Any thoughts, experience or comments to share? Good, bad, undecided?

    ReplyDelete