|  Login  |   
    You are here Learn  »  Experts/Blogs
Meet our Experts  
Search Blogs  
Blog Archive  
Why you should never buy project management software  
Location: BlogsNick Matteucci - Virtual Teamwork with Real Results    
Posted by: Nick Matteucci 11/9/2007 11:45 PM

Homewithdad10f987171628.jpg

Let me begin with a disclaimer.  I live, eat, and breathe project management software.  Work wise, it is the reason for my existence (far as I can tell).  I quit my job 10 years ago as an Ernst & Young PMO consultant to start a project management software company with no income, little in savings, and our first child had just been born.  Since that time we have built an award winning company with dramatic growth, expert accolades, and customers around the globe.

So for me to tell you that you should never buy project management software must come as some surprise to you.

Let me explain.

People call us all the time saying "I want to buy some project management software".  My answer is always the same "no you don't".


Here is my top 10 list:  What you really want to buy when you say you want project management software

Paul - give me a drum roll - please!



10. An end to the administrative nightmare that has become project management

9. Resource capacity planning

8. A defensible argument as to why your team can't take on any more project work this month

7. A way to standardize a better process

6. An end to the chaos surrounding projects

5. An end to the 10 status reports to 10 different managers - every week!

4. A way to prioritize projects and communicate priorities to everyone

3. A way to measure the quality, quantity, and satisfaction of completed work

2. The ability to get more work done with the same number of people

and the number one thing you really want to buy when buying project management software is...

1. Getting your boss off your back!

These are the things you are REALLY looking for.  Not another piece of software for your organization to digest.

Why do I bring this up?  Because so few companies follow the axiom "You lead with the need". 

Or consider this quote from one of my favorite pontificators, Yogi Berra:  "If you don't know where you're going, you might not get there".

The risk of not having clearly defined needs?  We see all the time that people buy the wrong project management system and in the process waste hundreds of thousands of dollars, months of lost effort, and sour their organizations to the many benefits of project management.  They fall in love with pretty pictures that require too much end user input or satisfy no real management.  They may be suitable for framing, but won't allow your company to make more money, save money, or eliminate business risk.

I recommend (before you look for software) that you make a list of objectives and prioritize them.  It is also nice to know the things you know you need today and the things you think you might need in the future.  It might look something like this:

Current Requirements (By Priority) Future Requirements (By Priority)
Benefits Features Benefits Features
  1. Simple to use

  2. Supportable by current staff with less time

  3. Web-Based

  4. Project Tracking

  5. Work (Deliverables/Tasks)

  6. Milestone tracking

  7. Issue Management

  8. Timesheets

  9. Status Reporting

  10. Email Integration

  11. Project Templates

  12. Workflow/Lifecycle

  13. Gantt Chart

  14. Forecasting/Capacity Planning

  15. RYG Metric Reports

  16. Project Accounting

  1. Action Items

  2. Service Requests

  3. Risks

  4. Document Management

  5. Feedback/Wiki

  6. Location Hierarchy

  7. Active Directory Sync

  8. Post project scoring

  9. Change Management

  1. Microsoft Project Integration

  2. Program Management

  3. Customer Integration

  4. Pre-project client requests

  5. Balanced Scorecards

  6. Portfolio Mgt by Organization

  7. Portfolio Mgt by Client

  8. Issue Resolution Reporting

  9. Milestone Completion Reporting

  10. Changes By Priority Reporting

  11. Avg Number of Risks Reporting

  12. Project Satisfaction Reporting

  13. Risks By Exposure Reporting

     

  1. Customer Satisfaction Metrics

  2. Project Dependencies

  3. Small/Support Project Tracking

  4. Red-Yellow-Green Reporting

  5. Schedule Variance Reporting

  6. Risk Resolution Reporting

  7. Avg Number of Issues Reporting

  8. Cost Overage Reporting

  9. Issues By Priority Reporting

  10. Avg Number of Changes Reporting

This will give an excellent probably of picking the right solution the first time and not getting "snowed" by flashy charts and graphs that either mean nothing or require so much administration it would bury the organization.

Now that you have a handle on your requirements you are ready to look at possible solutions.  In the next Blog I will teach you the top 5 things to never say to a vendor while shopping for project management software!

Virtually yours,
Nick Matteucci, MBA

Author: Nick Matteucci is a co-founder of
VCSonline.com a web 2.0 project management software company headquartered in St. Louis Missouri. Mr. Matteucci is also an active board member and the Chief Technology Officer for the PMI ISSIG. When not obsessing over virtual project management best practices Mr. Matteucci enjoys spending time with his wife and three small children. He also enjoys travel, running, and all things automotive.


Bookmark this post:   del.icio.us:Management Software digg:Why you should never buy project management software newsvine:Why you should never buy project management software reddit:Why you should never buy project management software Y!:Why you should never buy project management software magnolia:Why you should never buy project management software
 

Copyright ©2007 Nick Matteucci
Permalink |  Trackback

Comments (2)   Add Comment
5 Things to Never Say to a Project Management Software Salesperson    By TrackBack on 11/26/2007 1:00 PM
So your organization has decided it needs: Project management software Resource management software / Capacity planning Enterprise Project and Portfolio management If you read my l ...
# PMS: Project Management Sanity

Re: Why you should never buy project management software    By 885610 on 11/25/2007 3:56 PM
Well said Nick. I've had people approach me wanting to learn how to use MS Project. When I ask why they generally answer along the lines of "So I can manage a project". If I dig deeper(I think you'd call this 'qualifying the prospect'), they have little or no idea of project management methodologies and believe that MS Project will solve all their problems. If only!

If I (gently) point out that possession of MS Word does not necessarily make them a great writer, or Excel a financial whizz they begin to get the picture. We can then get down to finding out what the real problem is and work out a solution (which may include using MS Project, but only once they understand what for).

PS Is that a new baby, or an old picture?


Your name:
Title:
Comment:
Add Comment   Cancel