VP of Applications CAP

The purpose of the VP of Applications Content Acceleration Pack (CAP) is to provide a set of items (Dashboard pages, Scorecards, Contexts, KPIs, and more) that automatically gathers information from across your enterprise to build Key Performance Indicators (KPIs) related to VP of Applications-related issues. The CAP provides broad and deep insight that should enable you to reduce the cost of application development, justify the investments, provide explanations for project's delays, provide explanations for application failures in production, analyze why applications are not meeting business requirements, find the vendors with the best performance, balance available resources with business demands, be provided with the ability to quickly respond to the needs of the business, and to deliver secure applications

If the applications are not aligned with the business, there is no innovation, users go to competitors, and business revenues decline.

The use case for this Content Acceleration Pack is to provide a 360 Degree Application View.

The data sources for the VP of Apps CAP are Application Lifecycle Management (ALM), Project and Portfolio Management (PPM), and Service Manager (SM).

The relevant content packs are ALM, PPM, and SM. For details, see Integration with ALM, Integration with PPM, andIntegration with SM.

ClosedVPAps_Demo

User interface elements are described below (when relevant, unlabeled elements are shown in angle brackets):

UI Element

Description

Pages

Demo VPApps Main Page

Scorecards

VP Applications

Business Contexts

VPApps_Demo

For details, see Semantic Layer - Contexts and Universes.

KPIs and Metrics

Note The Demo CAP includes KPIs with names followed by (Demo). The CAP includes the same KPIs with names that do not include (Demo). The KPIs are the same but have different names so that both the Demo CAP and the CAP can be activated at the same time.

  • Average Age of Active Demands KPI. The average age of active demands that are currently waiting for approval during the measurement period.

  • Average Age of Active Proposals KPI. The average age of active proposals that are currently waiting for approval during the measurement period.

  • Average Cycle Duration KPI. The average cycle duration. This KPI. enables you to measure whether the organization has adopted Agile best practices. Short cycles can lead eventually to more agility from the time-to-market perspective.

  • Average Project Delivery Time KPI. The average project delivery time of new products/services defined as the time it takes from the conception of a project until it is delivered to customer (EndDate and StartDate used in this KPI. formula).

  • Average Project Initiation Time KPI. The average time it takes to initiate a project (until all resources are assigned and the planning is completed) during the measurement period.

  • Average Time to Evaluate Proposals KPI. The average duration of proposals from the time they are opened to the time they are closed during the measurement period.

  • Average Time to Evaluate Scope Change KPI. The average duration of scope changes from the time they are opened to the time they are closed during the measurement period.

  • Average Time to Resolve Production Defect KPI. The average time needed to fix a defect in production during the measurement period. A production defect is a post-release defect (detected after the release end date).

  • Average Time to Review Requirement KPI. The average time spent to review and approve a requirement during the measurement period.

  • Change Success Rate KPI. The number of successful changes relative to the total number of changes performed during the measurement period.

  • Defect Resolution Time KPI. The average time it takes to close a defect during the measurement period.

  • Demands Backlog KPI. The number of open demands.

  • Detected Vs Closed Defects Ratio KPI. The ratio between detected defects and closed defects during the measurement period.

  • Deviation of Planned Work Hours KPI. The sum of the actual effort and the remaining estimated effort, relative to the planned effort for project tasks started during the measurement period.

  • Number of Escaped Defects KPI. The number of defects that were not discovered during pre-production quality testing, and were found after the release (their discovery date is after the release).

  • Percentage of Actual vs Planned Projects Cost KPI. The actual project costs relative to the planned project costs during the measurement period.

  • Percentage of Actual vs Planned Executed Tests KPI. The number of tests that were executed relative to the total number of test instances that were opened during the measurement period.

  • Percentage of Approved Project Scope Changes KPI. The number of scope changes that were approved relative to the total number of scope changes that were closed during the measurement period.

  • Percentage of Authorized Test Cases KPI. The number of test cases with a planning status that is ready relative to the total number of test cases that were created during the measurement period.

  • Percentage of Automated Test Cases KPI. The number of test cases that were automated relative to the total number of test cases that were created during the measurement period.

  • Percentage of Availability Compared to SLTs KPI. The total outage time relative to the total service-based SLT uptime during the measurement period.

  • Percentage of Change in Project Cost KPI. The change in the cost of projects during the last period relative to the change in the cost of projects during the previous period.

  • Percentage of Critical Defects KPI. The number of critical defects ('Urgent' and 'Very High' Statuses) that occurred relative to the total number of defects that were opened during the measurement period.

  • Percentage of Documented Requirements KPI. The number of requirements with attachments or descriptions larger than 50 words relative to the total number of requirements during the measurement period.

  • Percentage of Healthy Projects KPI. The number of healthy projects relative to the total number of projects that are ongoing in the current month.

  • Percentage of Incidents Classified as Security Related KPI. The number of incidents classified as security-related relative to the total number of incidents that occurred during the measurement period.

  • Percentage of Project Tasks on Time KPI. The number of project tasks completed on time relative to the total number of project tasks completed during the measurement period.

  • Percentage of Projects on Time KPI. The number of projects completed on time relative to the total number of projects that were completed during the measurement period.

  • Percentage of Rejected Defects KPI. The number of defects that were rejected relative to the total number of defects that were opened during the measurement period.

  • Percentage of Reopened Defects KPI. The number of reopened defects (supposedly fixed defects or defects that were once fixed but reappeared) relative to the total number of defects that were logged during the measurement period

  • Percentage of Requirements Traced to Tests KPI. The number of requirements that have a corresponding test relative to the total number of requirements. Note: The assumption is that a cycle duration is shorter than the KPI. periodicity (if a KPI. periodicity is monthly, the cycle duration should be a month or less).

  • Percentage of Reviewed Requirements KPI. The number of business or functional requirements that have been reviewed relative to the total number of business or functional requirements that were planned to be reviewed during the measurement period.

  • Percentage of Successful Test Runs KPI. The number of successful test runs relative to the total number of test runs that occurred during the measurement period.

  • Percentage of Tested Requirements KPI. The number of requirements that are actually covered and completed by tests that run, relative to the total number of requirements during the measurement period. Note: By default, the KPI. is based on cycles; if the organization does not use cycles the default can be changed to Projects.

  • Percentage of Test Instances Resulting in Defects KPI. The total number of test instances linked to defects relative to the total number of test instances that were run during the measurement period. Note that the KPI. only counts the test instances that are directly linked to defects.

  • Project Scope Change Backlog KPI. The number of open scope changes.

  • Proposal Backlog KPI. The number of open proposals.

Data (External Tables)

VPApps_Demo

ClosedDemo VPApps Main Page