This excerpt taken from the GPS 10-K filed Mar 28, 2006.
Project Filters
There are seven project filters that enable IT to assess project impacts to the overall portfolio as well as the risk associated with the project.
Rating
Description
Definition
Change Impact Insert Rating:
0
Narrow/Shallow
A small number of people are impacted (<50) and the change to their processes and/or roles is minimal.
1
Moderate
A moderate number of people are impacted (50-500) and the business is able to absorb the change introduced. (Also use for narrow/deep or shallow/broad)
2
Broad/Deep
A large number of people are impacted (>500) and the change to their jobs is significant requiring business skill transition.
Development Risk Insert
Rating: Based on minutes from ARB meeting.
0
Vanilla Package or ASP
No application development is required to use the solution. Vendor is credible and financially viable. Integration with existing systems is straightforward.
1
Package w /Customization
The package requires customization to meet business needs, and some complex integration with existing systems is required OR the package is unproven.
2
Custom Developed Solution
A significant amount of custom development is required in order to meet business requirements OR the vendor is not credible and financially viable.
Business Case Insert Rating:
0
Strong Economic Justification
The business case has a high IRR (>40%) with budgetable benefits OR the project is a regulatory mandate needed to stay in Legal Compliance.
1
Quantifiable Benefits
The business case has an IRR (>15%) OR is necessary to enable critical process controls OR enables scalability critical to support business.
2
Conceptually the Right Thing to Do
The business case identifies a compelling need to change, but does not have budgetable benefits at this time. OR system will be unsupported and that represents significant risk to critical
processes.
Resource Capacity Insert Rating:
0
Readily Available
The business AND IT resources required to accomplish the project are readily available and have the skills necessary to complete the project.
1
Exist, but Scarce
The project requires a specialized skill from the business or IT that exists, but is not readily available or will be challenging to acquire.
2
Do Not Exist
The project requires an expertise that does not exist, is challenging to acquire and the skill may need to be developed rather than acquired
Legacy Application Insert Rating:
If the project proposes leveraging an existing legacy application select from these three
choices:
0
Moving off Legacy is Not Critical
There is little risk associated with staying on the legacy system and this project proposes leveraging that legacy application.
1
Moderate Risk incurred with Legacy Solution
There is a moderate business or technical risk associated with staying on the legacy system.
2
Current Legacy Solution is High Risk
There is a high business or technical risk associated with staying on the legacy system and this project proposes leveraging the legacy application
If the project proposes a new solution select from these three choices:
0
New Solution is Critical
The current legacy solution is high risk and this project proposes moving functionality off of the legacy system.
1
Moderate Risk incurred with New Solution
There is a moderate business or technical risk associated with moving off of the legacy system.
2
New Solution is Nice to Have
There is low risk associated with staying on the legacy system and this project proposes a new solution.
N/A
No Legacy Impact
There is no impact to legacy applications and this risk is not applicable.
Project Dependencies Insert Rating:
0
Standalone Solution
Projects that do not impact and are not impacted by other projects are considered standalone with no dependencies.
1
Interface Solution
Projects that provide input to another project or provide output to another solution are considered interface solutions with some dependencies.
2
Dependent/Integrated Solution
Projects that must be integrated with other ongoing initiatives such that requirements and/or design information must be shared are dependent.
Project Focus Insert Rating:
0
Facilitates
Projects that facilitate the strategic projects (a.k.a Big 3) by providing new or better capability.
1
No Impact
Projects that use resources independent of the strategic projects and have no functional or technical impact on the strategic projects.
2
Adds Complexity
Projects that take resources or focus away from the strategic projects and/or add complexity to their work.
Bet you've never seen portfolio analytics like these.