Example Project Request Scorecard

Body

This article will help project request reviewers/evaluators to create and configure project request scorecards in TDAdmin by providing useful tips and examples of questions. The user must have access to Portfolio Planning in TDAdmin.

Overview

The Portfolio Planning scorecard can be used to evaluate project requests. This article describes example scorecard configuration and questions. Review the How Project Requests are Scored article for technical details on how the scorecard works.

Where to Find This

Scorecards appear in both the TDAdmin and TDNext interfaces, in the Portfolio Planning and Projects apps. They can also appear in TDClient if they are included in the project request form.

  • TDAdmin > Portfolio Planning is where administrators create and configure scorecards.
  • TDNext > Portfolio Planning is where users assigned to evaluate project requests score those requests using scorecards. Note: Scorecards can also be used in projects if this option is enabled.

Navigate to create/edit project request scorecards and scorecard criteria as follows:

  • TDAdmin > Portfolio Planning > Scorecards or Scorecard Criteria

Using Scores Wisely

We recommend scorecards be used as an input or factor in decision-making, but project request scores should not be the sole determining factor. For example, if project request A receives a score of 87 and project request B receives a score of 84, this does not necessarily mean that project request A should be approved over project request B.

The score should not be the only deciding factor for several reasons:

  1. The scorecard criteria may be missing questions or be weighted incorrectly.
  2. There may be qualitative factors to consider.
  3. Making decisions based on the score creates a large incentive for people to optimize for a high score, rather than for good project outcomes.

Scores can and should be used to band or group project requests. For example, project requests receiving a score in the lower quartile usually should not be considered.

Types of Scorecard Questions

When considering questions to include on a scorecard, take the following into account:

Value/Cost/Risk

One way of thinking about scorecard questions is in collectively weighing value, cost, and risk. In TeamDynamix, cost data can be collected via the Expenses section, value data can be collected in the scorecard, and risk data can be collected in the organizational risks section. It is also possible to ask questions related to value, cost, and risk – all in the scorecard section.

Project (Implementation) vs. Service (Ongoing)

Another way of thinking about scorecard questions is in considering the implementation itself along with the ongoing service that's being created or changed by the project. For example, some scorecard questions might ask about implementation costs; other scorecard questions might ask about total cost of ownership (TCO) such as the full-time equivalent (FTE) required to maintain the service once the project is complete.

Example Scorecard

Value-Related Questions

  • How aligned is this project request to the organization's strategic plans?
    • 0 strategic plan goals
    • 1 strategic plan goals
    • 2+ strategic plan goals
  • To what extent is this project expected to generate ongoing cost savings to units outside of IT?
    • >$100,000/yr savings
    • $10,000/yr-$100,000/yr savings
    • less than $10,000/yr savings
    • Introduces new costs: less than $10,000/yr new costs
    • Introduces new costs: $10,000/yr – $100,000/yr new costs
    • Introduces new costs: >$100,000/yr new costs
  • What is the level of active sponsorship for this project request?
    • Board-level sponsorship
    • President-level sponsorship
    • Cabinet-level sponsorship
    • Assistant Vice President (AVP)-level sponsorship
    • No executive sponsorship

Cost-Related Questions

  • To what extent is this project expected to generate cost savings to IT?
    • >$100,000/yr savings
    • $10,000/yr-$100,000/yr savings
    • Less than $10,000/yr savings
    • Introduces new costs: less than $10,000/yr new costs
    • Introduces new costs: $10,000/yr – $100,000/yr new costs
    • Introduces new costs: >$100,000/yr new costs
  • To what extent does this project request require key constrained IT resources?
    • Requires no constrained resources
    • Requires minimal involvement from constrained resources
    • Requires some involvement from constrained resources
    • Requires major involvement from constrained resources
  • Are new positions needed to maintain this service post-implementation?
    • Yes, 2+ FTE
    • Yes, 1-2 FTE
    • Yes, up to 1 FTE
    • No
  • To what extent does IT have the capabilities needed to implement this service?
    • IT has performed similar projects in the past
    • IT has experience with related projects
    • IT has little related experience 
    • IT has no related experience

Risk-Related Questions

  • Are there examples of similar project requests being implemented successfully at peer organizations?
    • Yes, several examples
    • Yes, one example
    • Other peers are implementing currently
    • No peers have implemented something similar
  • To what extent does this project request introduce new operational risks?
    • This project request would introduce virtually no new operational risks
    • This project request would introduce minor new operational risks, such as the risk of departments not operating
    • This project request would introduce major new operational risks, such as the risk of data breach
  • To what extent does this project request ameliorate or remove existing operational risks?
    • This removes significant current legal or compliance risks
    • This lessens significant current legal or compliance risks
    • This prevents possible future legal or compliance risks
    • No impact

Details

Details

Article ID: 40208
Created
Thu 10/5/17 1:16 PM
Modified
Thu 11/7/24 9:23 PM

Related Articles