Project Management Fundamentals
What is a Project?
A project is defined as a temporary endeavor or effort to create a unique product, services or results.
- The outcome of the project is not temporary. It has definite start data and end date.
- A project is progressively elaborated. As more information is available the plans are elaborated.
What is Project Management?
The project management can be defined as applying knowledge, skills, tools to project activities to achieve project objectives.
Project activities includes works that will produce the deliverable, Estimating cost and estimating resources are the example of project activities.
Meeting scope, cost and time are the main objectives of a projects. However meeting customer satisfactions and customer expectations are the implicit project objectives.
Project Constraints:
Project Management includes dealing with constraints that keep surfacing throughout the life cycle of a project. The most common set of constraints are cost, scope, time, quality, risks and resources.
Relationship among project, program and portfolio:
Portfolio: Portfolio is a collection of program put together to drive the strategic objectives. It may not be all related program.
Program : Program is a collection of related projects put together for better management. Example a program may have common resources which can be use effectively.
Project: A project is defined as a temporary endeavor or effort to create a unique product, services or results. A project may have sub-projects.
Operational Management: Operation management is a ongoing activities which has repetitive deliverable whereas the project management is a temporary endeavor which has unique deliverable.
Role of a Project Manager: Responsible for planning, executing, controlling and closing a project. A temporary role limited to project duration.
Enterprise Environmental Factors (EEF) - How company run the business?
Enterprise Environmental factors are conditions, situations or events in the company or in the market that directly or indirectly influences the project success.
Example of EEF:
- Market Place conditions
- Company culture and structure
- Risk tolerances
- Project Management Information System (MIS) - how the company run the projects
- Work Authorization System
- Government regulations
Project Life Cycle: Project life cycle is defined as collection of phases. Projects are divided into phases for better control and management. It focuses on managing the work that is required to produce the deliverable and accomplish the objective of the product.
A life cycle determines what work need to be done in each phase, who is involve in each phase how to control and approve each phase.
Phase End Review: The phase is marked by the completion of the deliverable. The completion is marked by phase end review ( kill points, phase exits, phase gates) where "go ahead" or "no go ahead" or postponement decision is taken.
Notes:
- Cost and staffing are low at the early phases, rise in the middle phases and fall in the last phases.
- Risk of failing is high at the starting phase and risk of failing is low at the last phase.
- Cost of making changes increases from the early phases to the later phases.
- Ability of stakeholders to influence the project reduces from the early phases to later phase.
Product Life Cycle: Process of managing entire life cycle of a product from its conception, through design and manufacture to service and disposal.
Project Stakeholders: Project stakeholder are individuals or organization who are actively involved in the project and whose interest may be positively or negatively influenced by the project.
Example of stakeholders:
- Project Manager
- Customer/User
- Performing organization
- Project Team Members
- Project Management Team
- Sponsor
- Influencers
- PMO
Integration Management: Integration Management is about coordinating or bringing together all the different processes and activities in a project.
Importance of project charter:
The project charter is a result of charting or formal initiating a project. It document that formally authorized a project or phase.
Project Authorization: Not having formal authorization for starting a projects can result in failure due to lack of support and misalignment. The process of authorizing a project is aim at preventing these common reason of project failure.
Lack of authorization process will cause effect:
Importance of project charter:
The project charter is a result of charting or formal initiating a project. It document that formally authorized a project or phase.
Project Authorization: Not having formal authorization for starting a projects can result in failure due to lack of support and misalignment. The process of authorizing a project is aim at preventing these common reason of project failure.
Lack of authorization process will cause effect:
- Decline in profit
- Project with no end date
- Lot of rework
- Duplication of work
- Loss of opportunity
- Frustration
Documenting initial requirements: The develop project charter process also focuses on documenting initial requirements. The stakeholder expectations and needs are converted into high level requirements as a part of developing project charter.
Linking customer and the project: The develop project charter process also focuses on linking customer and the project. If the project is internal the linking is between the performing organization and the project.
Linking customer and the project: The develop project charter process also focuses on linking customer and the project. If the project is internal the linking is between the performing organization and the project.
Content of Project charter:
1. Project Purposes: Why the project is undertaken? Justification of project undertaken. Reason why we have taken the project -may be for ROI.
2. Measurable Project objectives - Mentioned all the objectives'
3. High Level Requirements - Get requirement from initial documents
4. High Level project Description:
5. High level product characteristics:
6. Summary milestone schedule
7. Summary Budget
1. Project Purposes: Why the project is undertaken? Justification of project undertaken. Reason why we have taken the project -may be for ROI.
2. Measurable Project objectives - Mentioned all the objectives'
3. High Level Requirements - Get requirement from initial documents
4. High Level project Description:
5. High level product characteristics:
6. Summary milestone schedule
7. Summary Budget
Input to the project charter:
Statement of Work (SOW)-SOW is a narrative description of product or services to be delivered.
The project statement of work contains following information.
For external project the SOW is provided by the customer sometime in the form of RFP, RFI and RFB.
For the internal project the SOW is provided by the sponsor.
Business Need - Give the justification and reasons of the project. Why it is initiated? What the project result will translate to business objectives.
Contracts-Commercials details. May not have detailed requirements.
EEF: Market Place conditions ( Demand and Supply, Currency Exchange fluctuation etc), government regulations
Organization process: -
Company culture and structure
Project Management Information System (PMIS)
Work Authorization System
Risk tolerance- risk taker vs. risk averse
Develop project Management plan - It contains process ( how the project will be defined, executed, monitored, controlled and closed), management plan (subsidiary plans) and baselines( Scope, cost and schedule).
(Processes + subsidiary plans) + Baselines + other details==> Project Management Plan
Direct and Manage Project Execution: Performing or getting work done as per the project management plan. Performing the work and creating deliverable are the 2 elements in this.
Approved changed request are authorized changes to the project. Only approved change request to be implemented and shall update the project plan. Approve change request include approved corrective actions, approved preventive actions and approved defect repair.
The change request remains as recommendations until they are approved. When they are approved by the CCB then it is called approved change request.
Monitor and control project work: Monitoring refers to collecting, measuring, analyzing and distributing work performance information throughout the project life cycle. Controls refer to the action taken based on the work performance information. This sometimes results in change requests. Note that only approved change request shall be implemented. The rejected change request shall be documented.
Close project or Phase:
Close project includes formally closing project or Phase by finalizing all the activities across all the process groups.The final product, services or results needs to undergo formal acceptance and handover. The formal acceptance and handover is provided in the form of a formal statement confirming completion of the deliverable.
Scope Management:
The scope management is concern with defining the work to be done in the project. From then it is controlling the scope.
Process of scope management:
Statement of Work (SOW)-SOW is a narrative description of product or services to be delivered.
The project statement of work contains following information.
- Product Scope Description- Characteristics of the product. Deliverable at high level
For external project the SOW is provided by the customer sometime in the form of RFP, RFI and RFB.
For the internal project the SOW is provided by the sponsor.
Business Need - Give the justification and reasons of the project. Why it is initiated? What the project result will translate to business objectives.
Contracts-Commercials details. May not have detailed requirements.
EEF: Market Place conditions ( Demand and Supply, Currency Exchange fluctuation etc), government regulations
Organization process: -
Company culture and structure
Project Management Information System (PMIS)
Work Authorization System
Risk tolerance- risk taker vs. risk averse
Develop project Management plan - It contains process ( how the project will be defined, executed, monitored, controlled and closed), management plan (subsidiary plans) and baselines( Scope, cost and schedule).
(Processes + subsidiary plans) + Baselines + other details==> Project Management Plan
Direct and Manage Project Execution: Performing or getting work done as per the project management plan. Performing the work and creating deliverable are the 2 elements in this.
Approved changed request are authorized changes to the project. Only approved change request to be implemented and shall update the project plan. Approve change request include approved corrective actions, approved preventive actions and approved defect repair.
The change request remains as recommendations until they are approved. When they are approved by the CCB then it is called approved change request.
Monitor and control project work: Monitoring refers to collecting, measuring, analyzing and distributing work performance information throughout the project life cycle. Controls refer to the action taken based on the work performance information. This sometimes results in change requests. Note that only approved change request shall be implemented. The rejected change request shall be documented.
Close project or Phase:
Close project includes formally closing project or Phase by finalizing all the activities across all the process groups.The final product, services or results needs to undergo formal acceptance and handover. The formal acceptance and handover is provided in the form of a formal statement confirming completion of the deliverable.
Scope Management:
The scope management is concern with defining the work to be done in the project. From then it is controlling the scope.
Process of scope management:
- Defining the scope
- Creating WBS
- Obtaining formal acceptance of the deliverable
- Controlling the Scope
Collect the requirements: Project charter and stakeholder registers are the main input to collect the requirements.
Below is some of the tools and techniques use to collect requirements.
Interview- Interview are conducted to elicit the requirements with the key stakeholders. Sometime interview is done one to one basic. However it is a time consuming process.
Focus Groups: Discuss are been done with domain expert or SME. Some discussion are also conducted with other department to get their requirements and attitude towards the project.
Facilitated Workshop: Different workshop conducted with the key people and with the cross functional team.
Prototypes: When the user requirement is not clear or when design is not clear or there are history of the communication problem , then we should go for simulation of the product to get the requirements.
Observations: End user can give input as to how it is performing or how it is working.
Questionnaire and Survey: Sometime offline question are shared and offline survey is done.
Group creativity technique:
Brainstorming- It is used to generate a large number of ideas, risk, solution or gather lot of information for decision making , priority setting or planning. It should be free flow idea and no judgement is passed.
Nominal Group Technique: It is used to rank the most useful ideas, risks and solutions for further brainstorming.
Delphi Technique is used to reach a consensus of expert opinion anonymously. No bias and no grouping is allowed.

