IT Project Ranking & Estimation

Estimate complexity, duration, and priority, aligned with PMBOK scheduling practices.

Project Summary Step 1 of 8

Used to calculate planned and adjusted completion dates.

1. Core Scope & Size Step 2 of 8

Captures the basic footprint of the project: how big it is and how many systems are touched.

2. Technical Complexity Step 3 of 8

Measures how technically difficult the project will be to implement and support.

3. Security & Compliance Step 4 of 8

Captures regulatory or public-facing aspects that increase risk, governance, and lead time.

4. Stakeholder & Governance Step 5 of 8

Drives meeting load, decision cycles, and political complexity.

5. Requirements & Ambiguity Step 6 of 8

Measures how clear and stable the requirements are.

6. Resource & Capacity Constraints Step 7 of 8

Drives how quickly work can actually move through queues and staffing.

7. Time Estimation (PERT Inputs) Step 8 of 8

Provide your best estimate of the project duration in months.

months
If everything goes as well as possible.
months
What you realistically expect under normal conditions.
months
If major risks and delays occur.

8. Impact & Mandate

Captures business impact if delayed, critical domains, and mandate level to support priority scoring.

Saved Projects & Rankings

Projects are sorted by Priority Index (highest first). Data is stored in your browser and can be exported to Excel.

0 projects
# Project Name Sponsor Type Notes Complexity Level Expected Duration (months) Adjusted Duration (months) Impact Index Priority Index Actions

Summary Dashboard

Portfolio view of all projects, aligned with the current fiscal year settings and PERT-based duration estimates.

Completion Calendar

Calendar view of estimated project completion dates (based on adjusted duration). Each day lists the full project name(s) scheduled to complete on that date within the fiscal year.

Total Estimated PM Hours

Sum of estimated project management hours across all projects (calculated from complexity, governance, and risk).

0

Fiscal Year Window

Projects must complete within the configured fiscal year to comply with portfolio constraints.

Schedule Status Flags (Based on PMBOK Control Schedule Concepts)

Projects are flagged when they exceed their originally estimated duration or are approaching their adjusted (risk-informed) completion date.

Exceeding Estimated Duration Overrun

Approaching Adjusted Duration Warning

Portfolio Dashboard

Executive summary of the portfolio based on database records (complexity, impact, priority, and capacity).

Recent Activity

Counts of projects updated recently (based on updatedAt timestamps in the database).

Updated last 7 days

0

Updated last 30 days

0

Updated last 90 days

0

Users

Create User

User Directory

ID Email Name Role Active Actions

Audit Log

Filters

Results

When User Role Action Entity Entity ID Project IP Diff

All Projects (Database Records)

Records loaded from the SQLite database via /api/projects. This view mirrors the data behind the Saved Projects table.

Settings

Configure the fiscal year and core parameters for portfolio planning. These settings apply across all projects and dashboards.

Fiscal Year Configuration

Define the start and end of the current fiscal year. All project time estimates must fit within this window.

Constraint: All projects must have an estimated time of delivery that falls entirely within the defined fiscal year.

Complexity Weight Configuration

Set how much each dimension contributes to the overall complexity score. You can think of these as percentage weights; they don’t have to add up to 100 — the app will normalize them for you.

Default: 25
Default: 20
Default: 25
Default: 15
Default: 15
Tip: Higher numbers make that dimension more influential in the overall complexity score and ranking.

Project Manager Dashboard

Execution workspace. Projects are auto-populated from the Business Analyst intake database.