How to determine project size? - Sizing | Estimation & Planning - Project Management

In project management, knowing project size is important for the estimation and planning for each task of a project. Hence, it is obvious that the determining project sizing and level help to understand clearly, and easier for planners as well sponsors to allocate the budgets and organize the tasks accordingly.

Determining Project Levels:

Project level will be based on Funding Expense and/or Total Man-hours (capture in Project Charter the number of hours for civilians and contractors) and/or Visibility.

Project Sizing Example:

If the project is very complex, you may choose to move the project up to the next level for documentation purposes. Complexity is defined under the definitions section.

Minor Projects:

1. Project Charter Executive Summary (PCES)
2. Project Task List
3. Communication Plan - Communication Plan MATRIX
4. Project Closure Plan

Small Projects:

1. Project Charter Executive Summary (PCES)
2. Project Task List
3. Project Management Plan (Abbrev)
    - Work Breakdown Structure (WBS)
    - Project Schedule
    - Quality Management Plan
    - Issue Management Plan
    - Change Management Plan
    - Risk Management Plan (Abbrev)
    - Procurement Plan (Actual)
    - Record of Changes
4. Communication Plan - Communication Plan MATRIX
5. Functional Requirements
6. User Acceptance Test (UAT) Plan (Abbrev) *
7. Project Closure Document

Medium Projects:

Large Projects:

1. Project Charter Executive Summary (PCES)
2. Project Task List
3. Project Management Plan
4. Risk Management Plan (Abbrev)
    - Risk Identification Form
    - Risk Analysis Summary
    - Risk Response Summary
    - Risk Monitor and Control
    - Risk Mitigation Cost
    - Contingency (Risk) Budget Plan
    - Record of Changes
5. Project Schedule
6. Procurement Plan (Choose one):
- Initial Stage
- Actual
7. Work Breakdown Structure
8. Project Status Report
9. Communication Plan
    - Communication Plan MATRIX
10. Functional Requirements
11. User Acceptance Test (UAT) Plan (Choose one): *
    - UAT Plan
    - UAT Plan (Abbrev)
12. Preliminary and Critical Design Reviews *
13. Project Closure Document

Multi-agency and Enterprise

1. Project Charter Executive Summary (PCES)
2. Project Task List
3. Project Management Plan
4. Risk Management Plan (Abbrev)
    - Risk Identification Form
    - Risk Analysis Summary
    - Risk Response Summary
    - Risk Monitor and Control
    - Risk Mitigation Cost
    - Contingency (Risk) Budget Plan
    - Record of Changes
5. Project Schedule
6. Procurement Plan (Choose one):
- Initial Stage
- Actual
7. Work Breakdown Structure
8. Project Status Report
9. Communication Plan
    - Communication Plan MATRIX
10. Change Management Plan
11. Functional Requirements
12. User Acceptance Test (UAT) Plan (Choose one): *
    - UAT Plan
    - UAT Plan (Abbrev)
13. Preliminary and Critical Design Reviews *
14. Project Closure Document

* These documents may be more relevant for the software development life cycle which is a subset of the overall project management life cycle, as identified in the methodology.

DEFINITIONS

Complexities:

Low – simple schedule, low cost, minimal interruption.
Medium – few dependencies, staff from other areas, impacts more than one area. High – complex schedule, high cost, untested technology, extensive impact.
Funding/Expenses – includes in-house contractor cost, additional contractor requirements cost (detail in Charter), purchase requirements (software, hardware, out year license/maintenance cost, supplies, etc.), travel.
Total Man-hours – includes civilian and contractor hours.
Visibility - Anything on the Project Watch List requires Project Status Briefing slides (scope, dates, milestones, funding requirements, and risk identification), Project Charter, Project Management Plan, and any other document requested by organization.