Building an effective business case for PPM software

Building an effective business case for PPM software

Executive Summary Provide a brief overview of what will be covered in the following sections.

Business Objectives Describe how the PMO objectives support the business goals. Outline what you’ll be able to do that you can’t do now and what requirements the PPM software should have to support your team or department’s ability to solve their problems and/or accomplish their goals

PMO Challenges & why PPM software is necessary Provide an assessment of the current state around project success, failure rates, project management maturity and project processes.

Tangible and Intangible Benefits Highlight the expected benefits, including quantifiable benefits, such as time and money saved, as well as the qualitative benefits, such as increased collaboration and stakeholder satisfaction

Tangible and Intangible Benefits Objective Decrease number of team meetings by [xx]% over [time frame] Increase budget adherence by [xx]% over [time frame] Increase on-time project delivery by [xx]% over [time frame] Decrease number of audit findings by [xx]% over [time frame] Benefit Measure Current Target X X X X

Cost Savings With the implementation of PPM software organisations can expect to attribute resource and technology to the use of a single PPM tool. List the savings related to technology consolidation and/or replacement, resource overhead, ongoing maintenance costs, etc.

Implementation Cost Include a table of the costs associated with the software purchase and implementation. This includes people, process and technology. These costs will vary for Software-as-a-Service and on-premise solutions. Include both physical costs, such as the hardware costs in the case of an on-premise solution, number and price of the software licenses, as well as costs that are harder to pin down, such as the time required to implement and learn a new system. Remember to include both once-off and recurring costs.

Once-Off Costs Description Type Configuration and set-up Dependent of costs complexity of requirements Data migration As needed Frequency Once-Off Estimate X Once-Off X Training Cost Number of users Once-Off X Internal costs to run the implementation project Communication and change management Internal resource rate cost External consultants / Internal resource cost Once-Off X

Recurring Costs Description Software licence cost Software maintenance and support costs Type Number of users Frequency Annual/ As needed Monthly Annual/ Monthly/ Inclusive of licence cost Estimate X X

Return on Investment / Payback period A typical Return on Investment (Ro. I) analysis looks at the costs versus the benefits, and how long it will take to realise the benefits.

Solution Evaluation If you’re not sure what to look for, it’s easy to get overwhelmed when you compare project portfolio management software. List the functionality required and whether the shortlisted vendors support the functionality in a table format.

Solution Evaluation Portfolio Management and Prioritisation Yes No Allows for simple or complex categorisation models Includes automated, manual, simple or complex prioritisation models; Allows for the collection of all demand required projects Graphical portfolio and prioritisation dashboards with drill down capability

Execution Timeline Depending on the complexity of the requirements, expect a PPM software implementation to take anything from 3 to 24 months for a successful implementation. Work with the vendors ahead of time on the implementation approach and timeline. This will provide your audience with an idea of what to expect during the implementation.

Implementation Approach Detail the implementation options and provide a recommendation on the approach that will generate the most business value in the shortest time frame.