Project Management Study Notes

 marketinguyz.com

Chapter 1: Overview of Project Management

A project is a temporary endeavor that has a defined start and end date, aimed at achieving a specific goal within a set budget and resources. Projects can range from building a house to launching a new product or implementing a new system.

Attributes of a Project:

1. Temporary: Projects have a defined start and end date.
2. Unique: Projects are one-of-a-kind, unlike regular business operations.
3. Specific: Projects have a clearly defined objective or goal.
4. Resources: Projects require resources, including time, money, and people.
5. Planning: Projects require a comprehensive plan to achieve the desired outcome.

Project management is important because it provides a structured approach to achieving project goals within the constraints of time, budget, and resources. It involves planning, organizing, and controlling resources t4o achieve specific objectives. Project management helps ensure that projects are completed on time, within budget, and to the satisfaction of stakeholders.

Project Management Process:

The project lifecycle describes the stages that a project goes through from initiation to closure. The stages of the project lifecycle include: 

1. Initiation: the project is defined, and goals and objectives are established
2. Planning: a detailed project plan is developed, including timelines, budgets, and resource requirements 
3. Execution:  involves the actual implementation of the project plan
4. Monitoring: involves tracking project progress and making adjustments as necessary and Control
5. Closure: the project is completed and evaluated

Project stakeholders are individuals or groups who have an interest in the outcome of the project. They can include project sponsors, customers, team members, suppliers, and regulatory agencies. It is important to identify stakeholders and manage their expectations throughout the project lifecycle.

Project management structures: functional, matrix, and projectized. In a functional structure, team members report to their functional manager, and project management is performed by a dedicated project manager. In a matrix structure, team members report to both a functional manager and a project manager. In a projectized structure, the project manager has full authority over the project team.

The appropriate project management structure depends on several factors, including the project's complexity, the level of authority required by the project manager, and the availability of resources.

The main causes of project failure include poor planning, inadequate communication, lack of stakeholder involvement, inadequate resources, scope creep, and inadequate project management. Effective project management can help address these issues and increase the likelihood of project success.

Project definition is the process of clearly defining the scope, objectives, and deliverables of the project, and identifying the resources required to complete the project successfully. The key steps in project definition include:

1. Defining Scope: The first step in project definition is to define the scope of the project, which includes identifying the project goals, objectives, deliverables, and stakeholders. 
   
   
2. Establishing Priorities: Once the project scope has been defined, the next step is to establish priorities. This involves identifying the critical path of the project, which is the sequence of tasks that must be completed on time to meet project objectives. 
   
   
3. Creating the Work Breakdown Structure (WBS): The WBS is a hierarchical decomposition of the project scope into smaller, more manageable components. It is used to identify the work required to complete the project and to organize the work into manageable sections. 
   
   
4. Integrating the WBS with the Organization: Once the WBS has been created, it needs to be integrated with the organization's structure and culture. This involves identifying the resources required to complete the project and assigning roles and responsibilities to team members. It also involves identifying any communication or reporting requirements.
   
   
5. Coding the WBS for Information System: The WBS can be coded using a variety of systems, including numerical, alpha-numeric, or mnemonic codes. Coding the WBS helps to facilitate project tracking and reporting, and can be used to identify project components for budgeting, scheduling, and resource allocation.
   
   
6. Project Roll Up: Project roll-up involves aggregating the information contained in the WBS to create higher-level summaries and reports. This helps to provide a high-level overview of the project and to identify any areas of concern or potential risks.
   
   
7. Process Breakdown Structure: The process breakdown structure (PBS) is a hierarchical decomposition of the project into processes, procedures, and tasks. It provides a detailed view of the work required to complete the project and helps to identify any interdependencies or bottlenecks.
   
   
8. Responsibility Matrices: Responsibility matrices are used to assign roles and responsibilities to team members and to ensure that everyone knows what is expected of them. There are several types of responsibility matrices, including the RACI (Responsible, Accountable, Consulted, and Informed) matrix, which is used to clarify the roles and responsibilities of team members.

                                            Chapter 2: Project Planning

Estimating project times and costs is a critical part of project management. Accurately estimating project times and costs helps to ensure that the project is completed on time, within budget, and to the satisfaction of stakeholders. The key factors influencing the quality of estimates include:

1. Project Complexity: The complexity of the project is a major factor that influences the accuracy of estimates. Complex projects are more difficult to estimate accurately than simple projects.
2. Project Size: The size of the project also affects the quality of estimates. Larger projects are typically more difficult to estimate accurately than smaller projects, as they involve more tasks, more people, and more resources.
3. Experience: The experience of the project team is another important factor that influences the quality of estimates. Experienced project teams are more likely to be able to accurately estimate project times and costs than inexperienced teams.
4. Assumptions: Estimates are often based on assumptions, and the quality of the estimates is directly related to the accuracy of the assumptions. If the assumptions are inaccurate, the estimates will also be inaccurate.
5. Data Availability: The availability of data is another important factor that affects the quality of estimates. The more data that is available, the more accurate the estimates are likely to be.

Estimation Guidelines for Time, Costs, and Resources:

1. Defining the scope of the project
2. Breaking down the project into smaller, more manageable tasks
3. Identifying the resources required to complete each task
4. Identifying any constraints or limitations that may impact the project
5. Documenting all assumptions and risks
6. Using historical data to inform estimates
7. Reviewing and refining estimates regularly throughout the project

Macro versus Micro Estimating: There are two main methods for estimating project times and costs: macro estimating and micro estimating. Macro estimating involves estimating the overall cost and duration of the project, while micro estimating involves estimating the cost and duration of individual tasks.

Methods for Estimating Project Times and Costs:

1. Expert Judgment: This involves seeking the opinions of experts in the field to estimate project times and costs.
2. Analogous Estimating: This involves using historical data from similar projects to estimate project times and costs.
3. Bottom-Up Estimating: This involves estimating the cost and duration of individual tasks and then aggregating the estimates to create an overall project estimate.
4. Three-Point Estimating: This involves using optimistic, pessimistic, and most likely estimates to calculate a weighted average estimate.

Developing Budgets: Once project times and costs have been estimated, budgets can be developed. Budgets should include all costs associated with the project, including direct costs (such as labor and materials) and indirect costs (such as overhead).

Developing a project network involves a series of steps that help to create a visual representation of the project plan. It involves breaking down the project into manageable work packages, defining the sequence of activities, determining the duration of each activity, and establishing the dependencies between activities. The following steps are involved in developing a project network:

1. Work Package Creation: A work package is a unit of work that can be easily managed and tracked. It is a deliverable-oriented grouping of project activities that are defined at the lowest level of the work breakdown structure (WBS). Work packages should be small enough to be easily estimated, planned, and tracked.
2. Defining Activity Sequence: Once the work packages are defined, the next step is to determine the sequence in which the activities will be performed. This involves identifying the logical dependencies between activities, i.e., which activities must be completed before others can begin.
3. Estimating Activity Duration: The next step is to estimate the duration of each activity. This involves determining how long each activity will take to complete, based on the available resources, skills, and tools.
4. Establishing Dependencies: After estimating activity duration, the next step is to establish the dependencies between activities. Dependencies are the relationships that exist between activities, and they can be classified as either mandatory or discretionary. Mandatory dependencies are those that must be followed, while discretionary dependencies are those that are preferred but not essential.
5. Constructing the Network: The final step is to construct the project network. This involves creating a visual representation of the project plan, showing the sequence of activities, their dependencies, and the duration of each activity. The most commonly used tool for constructing the project network is the Activity-on-Node (AON) diagram.

The Activity-on-Node (AON) diagram is a graphical representation of the project network. It is based on the nodes and arcs concept, where nodes represent activities and arcs represent the dependencies between activities. The AON diagram has two types of nodes: the activity node and the dummy node.

The activity node represents an actual activity, and it is drawn as a rectangle. The dummy node represents a logical relationship between activities and is drawn as a circle. A dummy node is used to show a dependency between two activities that do not have a direct relationship.

The network computation process involves determining the earliest and latest start times and the earliest and latest finish times for each activity in the project network. This is done using two techniques: the forward pass and the backward pass.

1. The Forward Pass: The forward pass is used to determine the earliest start and finish times for each activity in the project network. The earliest start time is the earliest possible time an activity can start, given the dependencies and the duration of the preceding activities. The earliest finish time is the earliest possible time an activity can finish, given its duration and the earliest start time.
2. The Backward Pass: The backward pass is used to determine the latest start and finish times for each activity in the project network. The latest start time is the latest possible time an activity can start without delaying the project completion date. The latest finish time is the latest possible time an activity can finish without delaying the project completion date.

Extended Network techniques refer to a set of methods and approaches used in social network analysis (SNA) to study networks that go beyond the immediate connections between individuals or entities. These techniques are used to analyze the complex interactions and relationships that exist within larger networks, such as organizations, communities, and ecosystems. Extended network techniques in SNA include:

1. Centrality measures: Centrality measures are used to identify the most important nodes or entities within a network. These measures include degree centrality, betweenness centrality, and eigenvector centrality.
2. Cohesive subgroups: Cohesive subgroups are groups of nodes that are highly connected within a larger network. These subgroups can be identified using algorithms such as the k-core decomposition and the clique percolation method.
3. Structural holes: Structural holes are gaps in a network that create opportunities for information or resources to flow between different parts of the network. These gaps can be identified using measures such as the constraint measure and the effective size measure.
4. Multiplex networks: Multiplex networks are networks where individuals or entities have multiple types of relationships or connections with each other. These networks can be analyzed using methods such as multilayer network analysis and blockmodeling.
5. Network dynamics: Network dynamics refers to how networks change over time. Techniques such as longitudinal network analysis and event sequence analysis can be used to study how networks evolve and change.                    

CPM Numerical (Not in Current Syllabus )

PERT Numerical (Not in Current Syllabus)

 

 

Chapter 3: Project Scheduling & Risk Management

Types of Project Constraints

1. Time constraint - The project must be completed by a specific deadline.
2. Resource constraint - The project must be completed with a specific set of resources.
3. Cost constraint - The project must be completed within a specific budget.

Classification of Scheduling Problem:

1. Deterministic scheduling - The time required for each activity is known and fixed.
2. Stochastic scheduling - The time required for each activity is not known and can vary.
3. Resource-constrained scheduling - The project schedule must take into account the limited availability of resources.

Resource Allocation Methods:

1. Resource Leveling - Adjusting the start and end times of project tasks to ensure that resource usage is balanced and does not exceed resource capacity.
2. Resource Smoothing - Adjusting the durations of project tasks to ensure that resource usage is balanced and does not exceed resource capacity.
3. Critical Chain Method - The project schedule is based on the availability of critical resources.

Splitting involves dividing an activity into smaller parts that can be completed at different times.

Multitasking involves working on multiple tasks at the same time. This can help reduce the project duration, but can also lead to reduced productivity and increased risk.

Benefits of scheduling resources:

1. Helps ensure that resources are used efficiently.
2. Helps identify potential resource conflicts and bottlenecks.
3. Helps ensure that project deadlines are met.
4. Helps ensure that project budgets are not exceeded.

Assigning project work involves determining which tasks need to be completed, who will complete them, and when they will be completed.

Multi-project resource schedules involve creating a schedule that takes into account the resource needs of multiple projects. This can help ensure that resources are used efficiently across all projects.

Rationale for reducing project duration:

1. Meeting tight deadlines - In some cases, a project may need to be completed within a short timeframe due to external factors such as contractual agreements or market demands.
2. Cost savings - Reducing the project duration can help save costs associated with labor, materials, and other resources.
3. Competitive advantage - Completing a project faster than competitors can help gain a competitive advantage in the market.
4. Managing risks - A shorter project duration can reduce the risk of unforeseen events that may occur during the project timeline.

Options for accelerating project completion:

1. Increasing resources - Adding more resources to the project can help complete tasks faster. However, this can lead to increased costs and potential coordination challenges.
2. Overlapping tasks - Overlapping tasks can help reduce the overall project duration. However, this can increase the risk of errors and require additional coordination efforts.
3. Reducing scope - Reducing the scope of the project can help complete it faster. However, this may result in a less comprehensive solution and potential dissatisfaction from stakeholders.

A Project Cost – Duration Graph is a graphical representation of the trade-offs between project duration and cost. The graph is constructed by plotting the total project cost against the project duration.

The graph typically has a curve that shows the minimum cost for each duration. The curve is called the "minimum cost curve". The point at which the curve intersects with the vertical axis represents the minimum cost for the project. The point at which the curve intersects with the horizontal axis represents the minimum duration for the project.

Practical considerations:

1. Realistic estimates - Accurate estimates of task durations and resource requirements are critical to creating a realistic project schedule.
2. Communication and coordination - Effective communication and coordination among team members and stakeholders is essential to ensure that project tasks are completed on time.
3. Risk management - Identifying potential risks and developing contingency plans can help mitigate the impact of unforeseen events on the project timeline.
4. Resource availability - Availability of resources such as skilled labor, materials, and equipment can impact the project duration. Careful consideration of resource availability is important when developing a project schedule.

Risk management is an essential process in project management that involves identifying, assessing, and mitigating risks to the project. Here are the six main steps in the risk management process:

1. Risk Identification: The first step in the risk management process is to identify potential risks that could impact the project. This involves brainstorming sessions with the project team, stakeholders, and subject matter experts to identify potential risks.
2. Risk Assessment: The next step is to assess the likelihood and impact of each identified risk. This involves assigning a score to each risk based on the probability and impact of the risk occurring.
3. Risk Response Development: Once the risks have been identified and assessed, the next step is to develop a plan for responding to each risk. This involves developing strategies to mitigate or avoid the risk, transferring the risk to another party, or accepting the risk.
4. Contingency Planning: Contingency planning involves developing a backup plan for responding to risks that cannot be avoided or mitigated. This involves identifying the resources, activities, and timeline needed to implement the contingency plan if the risk occurs.
5. Risk Response Control: Once the risk response plans have been developed, the next step is to monitor the project to ensure that the risk response plans are being implemented. This involves tracking the progress of the risk response plans and making adjustments as needed.
6. Change Control Management: The final step in the risk management process is to ensure that any changes to the project are managed in a way that minimizes risks. This involves evaluating the potential impact of changes on the project risks and developing appropriate risk response plans.

                                    Chapter 4: Project Organization

The project manager is responsible for planning, executing, and closing a project successfully. The following are some of the key responsibilities of a project manager:

1. Defining the project scope and objectives
2. Developing a project plan that outlines the project timeline, budget, and resources required
3. Assigning tasks and responsibilities to team members
4. Monitoring project progress and making adjustments as necessary
5. Managing project risks and issues
6. Communicating project status to stakeholders
7. Ensuring the project is delivered on time, within budget, and meets the required quality standards
8. Managing the project team and providing leadership and support
9. Ensuring effective collaboration and communication between team members and stakeholders
10. Conducting project post-mortems to identify areas for improvement.

Planning, Organizing, Controlling by project manager:

1. Planning: A project manager needs to have the ability to develop a detailed project plan that outlines the project timeline, budget, and resources required to complete the project successfully.
2. Organizing: A project manager needs to have the ability to organize the project team and assign tasks and responsibilities to team members based on their skills and expertise.
3. Controlling: A project manager needs to have the ability to monitor project progress and make adjustments as necessary to ensure the project is delivered on time, within budget, and meets the required quality standards.

Skills of the Project Manager:

1. Leadership Abilities: A project manager needs to have strong leadership skills in order to motivate and inspire the project team to achieve their goals.
2. Coaching and Mentoring Abilities: A project manager needs to have the ability to coach and mentor team members to help them develop their skills and achieve their full potential.
3. Communication Skills: A project manager needs to have excellent communication skills in order to effectively communicate project status, goals, and requirements to team members and stakeholders.
4. Interpersonal Skills: A project manager needs to have strong interpersonal skills in order to build effective working relationships with team members and stakeholders.
5. Ability to Handle Stress: Project managers need to be able to handle stress and remain calm under pressure in order to successfully manage projects.
6. Problem Solving Skills: Project managers need to have strong problem solving skills in order to identify and resolve issues that arise during the project.
7. Time Management Skills: A project manager needs to have strong time management skills in order to effectively manage project timelines and ensure the project is delivered on time.
8. Delegation: A project manager needs to have the ability to delegate tasks and responsibilities to team members based on their skills and expertise.
9. Management of Change: A project manager needs to be able to effectively manage changes that occur during the project, including scope changes, resource changes, and schedule changes.

The five stage team development model also known as Tuckman's model, describes the stages that teams go through as they develop and become more effective:

1. Forming: In this stage, team members are introduced to each other, and they begin to understand the goals and objectives of the project.
2. Storming: In this stage, team members begin to assert themselves and conflicts may arise. This stage is important for establishing trust and resolving conflicts.
3. Norming: In this stage, team members begin to work together effectively and establish group norms.
4. Performing: In this stage, the team is highly productive and focused on achieving the project goals.
5. Adjourning: In this stage, the project is completed, and the team disbands.

Situational Factors Affecting Team Development:

1. Task complexity and difficulty
2. Time constraints
3. Available resources
4. Team size and composition
5. Organizational culture
6. Leadership style

Team effectiveness is the degree to which a team is able to achieve its goals and objectives. Factors that contribute to team effectiveness include:

1. Clear goals and objectives
2. Open communication
3. Trust among team members
4. Shared decision-making
5. Effective conflict resolution
6. Supportive leadership

Conflict is an inevitable part of project management. Sources of conflict in projects can include:

1. Differences in opinions and ideas
2. Limited resources
3. Role ambiguity
4. Personality clashes
5. Differences in work styles

Effective conflict resolution involves:

1. Identifying the source of the conflict
2. Listening to all parties involved
3. Finding a solution that addresses everyone's concerns
4. Implementing the solution
5. Following up to ensure the solution is effective

Managing virtual project teams presents unique challenges, including:

1. Communication barriers
2. Time zone differences
3. Lack of face-to-face interaction
4. Cultural differences
5. Trust and accountability issues

To manage virtual project teams effectively, project managers should:

1. Use technology to facilitate communication
2. Set clear expectations for communication and collaboration
3. Foster a team culture that values inclusivity and respect
4. Establish trust through regular communication and feedback

Common pitfalls that project teams may encounter include:

1. Lack of clearly defined roles and responsibilities
2. Poor communication
3. Limited resources
4. Unrealistic expectations
5. Resistance to change

To avoid these pitfalls, project managers should:

1. Define roles and responsibilities clearly
2. Encourage open and frequent communication
3. Ensure adequate resources are available
4. Set realistic goals and expectations
5. Foster a culture that values adaptability and continuous improvement.

                                        

                                            Chapter 5: Project Evaluation

The structure of a project typically includes:

1. Project charter: Defines the project scope, objectives, and stakeholders.
2. Work breakdown structure (WBS): Breaks down the project into smaller, manageable tasks.
3. Project plan: Outlines the timeline, resources, and budget for the project.
4. Project team: Comprised of individuals responsible for carrying out the project plan.
5. Project management office (PMO): Provides oversight and support for the project team.
6. Communication plan: Outlines the methods and frequency of communication between project stakeholders.

Practical example

A monitoring information system (MIS) is a system that collects and analyzes data about a project's progress. The MIS provides project managers with the information they need to make informed decisions and adjust the project plan as needed.

The project control process involves monitoring and controlling project performance to ensure that the project is completed on time, within budget, and to the desired quality. The project control process includes:

1. Setting project baselines: Establishing a baseline for the project's scope, schedule, and budget.
2. Monitoring performance: Collecting and analyzing data to track the project's progress.
3. Controlling changes: Managing changes to the project scope, schedule, or budget.
4. Taking corrective action: Making adjustments to the project plan as needed to ensure project success.

Monitoring time performance involves tracking the project's progress against the project schedule. This involves measuring actual progress against planned progress, identifying deviations, and taking corrective action if necessary.

An integrated information system is necessary to ensure that project data is accurate, up-to-date, and easily accessible. An integrated system can help project managers make informed decisions and quickly respond to changes in the project environment.

A dashboard, status report, and index are useful tools for monitoring project progress. A dashboard provides a visual representation of project data, while a status report summarizes key project information. An index can be used to compare the project's actual performance to the planned performance.

Forecasting the final project cost involves estimating the total cost of the project based on its current status. This involves analyzing cost data and projecting the final cost of the project based on the project's performance to date.

1. Collecting and analyzing cost data: The project manager should gather data on actual costs incurred to date, including labor, materials, and other expenses related to the project.
2. Estimating remaining costs: Based on the project schedule and remaining tasks, the project manager should estimate the remaining costs for the project. This estimate should consider factors such as resource availability, productivity, and any changes to the project scope.
3. Determining the total cost estimate: Using the actual costs incurred to date and the estimated remaining costs, the project manager can calculate the total cost estimate for the project.
4. Comparing actual costs to the estimate: The project manager should compare the total cost estimate to the actual costs incurred to date to determine if the project is on track to meet its budget.
5. Adjusting the forecast: If the actual costs are higher than the estimated costs, the project manager should adjust the forecast to reflect the current status of the project. This may involve reducing scope or finding ways to reduce costs.
6. Communicating the forecast: The project manager should communicate the forecast to stakeholders and provide regular updates on the project's financial status. This will help stakeholders make informed decisions about the project and ensure that the project remains on track to meet its budget.

Other control issues that project managers may need to address include quality control, risk management, and stakeholder management.

A project audit is a review of the project's performance to determine if it met its objectives and to identify areas for improvement. The audit may be conducted during the project or after it is completed.

Project Audit Process

1. Plan the audit
2. Conduct the Audit
3. Summaries the audit
4. present the result
5. determine the action plan 
6. Schedule follow up
7. repeat

Project closure involves completing all project activities and delivering the final product or service to the customer. This involves:

1. Obtaining acceptance of the project deliverables from the customer.
2. Completing all project documentation.
3. Disbanding the project team.
4. Conducting a lessons learned session.

Team, team member, and project manager evaluations are conducted to assess performance and identify areas for improvement. Evaluations may include feedback on communication, collaboration, problem-solving, and other areas relevant to project success.

Team evaluations:

1. Focus on the overall effectiveness and productivity of the team as a whole.
2. Consider factors such as communication, collaboration, goal achievement, and adherence to deadlines.
3. Can be conducted through surveys, interviews, or other feedback mechanisms.
4. Provide an opportunity to identify areas where the team could benefit from additional resources, training, or support.

Team member evaluations:

1. Assess the performance of individual team members in relation to their job responsibilities and goals.
2. Consider factors such as quality of work, productivity, attendance, and interpersonal skills.
3. Should be conducted regularly to provide ongoing feedback and support for individual development.
4. Provide an opportunity to identify areas where individual team members could benefit from additional training or coaching.

Project manager evaluations:

1. Assess the performance of the project manager in relation to the overall success of the project.
2. Consider factors such as project planning and organization, leadership, communication, and problem-solving skills.
3. Can be conducted by team members, stakeholders, or upper management.
4. Provide an opportunity to identify areas where the project manager could benefit from additional training or support, and to ensure that the project stays on track and meets its objectives.