Project Management
Project Manager is CEO of the project. He is responsible for everything in a project similar to manner a CEO is for everything in his company. He is all in all responsible for the success and failure of a project. He has to manage the project in whatever manners possible.
Project Manager’s responsibility start as soon as he is assigned the project after the contract is signed.
Scenario
Let me take a scenario. A project estimated to be of 100 man days needs to be developed is assigned to Aditya, the PM. The project is a development project which would have to be follow entire SDLC phase. This project has been estimated to be of 80 FP with productivity taken for java for 10 hrs per FP.
First, Aditya does his own estimation to be convinced that he has taken the project with correct estimated effort.
Re Estimation
In case of major discrepancies in the effort, he needs to bring that out to his reporting manager, Shreya, which may mean some additional functionality or constraint not known at the time of estimation phase. In case, of some issue Shreya and Aditya may take up the issue with regards to change the contract or come to some agreement with the client. In case, of client not agreeing to the situation, Shreya and Aditya needs to take the call off choosing any of the many available options. One solution could be to project agree with his reporting manager to work with his own estimates.
If Aditya found the estimate to be correct and he is convinced of the estimate. Aditya now gets down to project management.
Planning
SPMP
Aditya starts with building the Software Project Management Plan (SPMP). In SPMP, Aditya documents the entire plan how he will be managing the project.
TOC of SPMP
Project Summary
Scope, Purpose and Objectives
Assumptions and Constraints
Project Deliverables
Schedule and Budget Summary
Project Organization
Roles and Responsibilities
Managerial Process Plans
Work Plan
Control Plan
Requirements Control Plan
Schedule Control Plan
Budget Control Plan
Quality Control Plan
Reporting Plan
Metrics Collection Plan
Risk Management Plan
Technical Process
Process Model
Methods, Tools, and Techniques
Infrastructure Plan
Product Acceptance Plan
Support Process Plans
Configuration Management Plan
Validation & Verification Plan
Documentation Plan
Quality Assurance Plan
Review and Audits
Problem Resolution Plan
Process Improvement Plan
Project Plan
Aditya now also starts on the project plan. He could be using any tools for this. Much used tool is Microsoft Project Plan (MPP). For 100 days project, he divides the project first into the phases.
This is tentative plan at high level for phases, it may change based on the company internal metrics phase breakup, project constraints like requirement phase, no architecture phase etc.
Based on this high level plan now Aditya is working out his low level plan in MPP,
Divide the phases into components to be built. Also display column “Work” which will have estimated hours from above table. Now when Aditya, enter estimate for that component in the work column and resource name in resource column, MPP calculates the duration based on the number of effort allowed and number resources working for that component.
Aditya also needs to enter precedence column for sequence. Review of component UC1 will start when UC1 completes. So once precedence is entered for all the start and end date is calculated automatically by MPP.
Project Manager is CEO of the project. He is responsible for everything in a project similar to manner a CEO is for everything in his company. He is all in all responsible for the success and failure of a project. He has to manage the project in whatever manners possible.
Project Manager’s responsibility start as soon as he is assigned the project after the contract is signed.
Scenario
Let me take a scenario. A project estimated to be of 100 man days needs to be developed is assigned to Aditya, the PM. The project is a development project which would have to be follow entire SDLC phase. This project has been estimated to be of 80 FP with productivity taken for java for 10 hrs per FP.
First, Aditya does his own estimation to be convinced that he has taken the project with correct estimated effort.
Re Estimation
In case of major discrepancies in the effort, he needs to bring that out to his reporting manager, Shreya, which may mean some additional functionality or constraint not known at the time of estimation phase. In case, of some issue Shreya and Aditya may take up the issue with regards to change the contract or come to some agreement with the client. In case, of client not agreeing to the situation, Shreya and Aditya needs to take the call off choosing any of the many available options. One solution could be to project agree with his reporting manager to work with his own estimates.
If Aditya found the estimate to be correct and he is convinced of the estimate. Aditya now gets down to project management.
Planning
SPMP
Aditya starts with building the Software Project Management Plan (SPMP). In SPMP, Aditya documents the entire plan how he will be managing the project.
- He starts with listing the scope of the project, things out of scope of the project, the contact people of the project, risks of the project (there could be a separate Risk Management Plan for thing) with risk mitigation strategies for each risk.
- Aditya also documents what he will meet the various other processes of the project, configuration management; reporting and weekly report and expectation form the client with dates. Aditya documents the SLA for answering of the queries, and escalation mechanism on both sides.
- Aditya communicate SPMP to his reporting manager, his counterpart, and other stakeholder like Quality Manager etc. All the people can agree or recommend the change in any of the procedure. Client PM can agree or disagree on the expectation from his side, SLAs and escalation procedure. This communication is healthy and sets the expectation from all sides.
TOC of SPMP
Project Summary
Scope, Purpose and Objectives
Assumptions and Constraints
Project Deliverables
Schedule and Budget Summary
Project Organization
Roles and Responsibilities
Managerial Process Plans
Work Plan
Control Plan
Requirements Control Plan
Schedule Control Plan
Budget Control Plan
Quality Control Plan
Reporting Plan
Metrics Collection Plan
Risk Management Plan
Technical Process
Process Model
Methods, Tools, and Techniques
Infrastructure Plan
Product Acceptance Plan
Support Process Plans
Configuration Management Plan
Validation & Verification Plan
Documentation Plan
Quality Assurance Plan
Review and Audits
Problem Resolution Plan
Process Improvement Plan
Project Plan
Aditya now also starts on the project plan. He could be using any tools for this. Much used tool is Microsoft Project Plan (MPP). For 100 days project, he divides the project first into the phases.
This is tentative plan at high level for phases, it may change based on the company internal metrics phase breakup, project constraints like requirement phase, no architecture phase etc.
Based on this high level plan now Aditya is working out his low level plan in MPP,
Divide the phases into components to be built. Also display column “Work” which will have estimated hours from above table. Now when Aditya, enter estimate for that component in the work column and resource name in resource column, MPP calculates the duration based on the number of effort allowed and number resources working for that component.
Aditya also needs to enter precedence column for sequence. Review of component UC1 will start when UC1 completes. So once precedence is entered for all the start and end date is calculated automatically by MPP.
No comments:
Post a Comment