Author’s view of Software Project Management Phases and their Processes
The author’s model contains five main phases:
1.
2.
3.
4.
5.
Project Initiation
Planning and Estimation
Execution and Control
Monitoring and Reporting
Closure and Evaluation
Phase 1 – Project Initiation
Purpose:


To define the project and establish its business value, scope, and sponsors.
Sets the foundation for all future planning and execution.
Key Activities:



Define project objectives, scope, and stakeholders.
Request for Proposal (RFP) and Project Charter are key outputs.
Focus on feasibility analysis, sponsor identification, and business case development.
Phase 2 – Planning and Estimation
Purpose:


To establish a comprehensive roadmap for executing the project.
Determine resources, schedule, budget, and risks.
� Key Activities:


Develop the Software Project Management Plan (SPMP).
Define the Work Breakdown Structure (WBS).


Estimate effort using techniques like:
o Function Point Analysis (FPA)
o Use Case Points (UCP)
o COCOMO II
Schedule tasks using PERT/CPM charts.
Phase 3 – Execution and Control
Purpose:

To implement the plan, build the deliverables, and ensure quality and control.
� Key Activities:



Assign tasks to teams and begin development.
Apply Quality Assurance (QA) practices.
Manage communications, risks, and changes.


Execute tasks as per SPMP.
Track progress using:
o Gantt charts
o Scrum boards
o Daily stand-ups
Apply quality assurance, risk mitigation, and change control.

Phase 4 – Monitoring and Reporting
Purpose:

To ensure the project remains on track in terms of scope, cost, and schedule.
� Key Activities:




Measure performance using Earned Value Management (EVM).
Track Key Performance Indicators (KPIs).
Conduct regular status meetings and reviews.
Identify deviations and apply corrective actions.


ompare planned vs. actual metrics.
Communicate with stakeholders through:
o Status reports
o Scrum retrospectives
Phase 5 – Closure and Evaluation
Purpose:

To formally complete the project, release resources, and capture lessons learned.
� Key Activities:




Conduct user acceptance testing (UAT).
Archive project documents and source code.
Conduct post-mortem analysis or retrospectives.
Transfer deliverables to operations or maintenance teams.


Prepare Project Closure Report and update organizational process assets.
Reflects Agile’s Sprint Review and Retrospective practices.