Project Management

What is a Project?

A project is a temporary endeavor or effort with a unique goal and a defined budget. Unlike routine operations, projects have a clear beginning and end. They aim to produce a unique result, i.e., to achieve something specific such as a product, service, improvement in process, implementation of a new system or any other outcomes. Projects are distinct from day-to-day operations, which are ongoing & repetitive and has constraints like time & money.

• Temporary Endeavor: A project has a clear start and end. It’s not ongoing work like daily tasks. For example, implementing an ERP system in an organization is a project because it has a specific beginning and end while it involves use of resources like time & money and has a particular goal.
• Unique Goal: Every project aims to achieve something specific and unique, like creating a new product or service. For instance, developing a new treasury software application is a project because it has a unique goal.
• Budget: Projects usually have a budget, which means they have limits on money, time, and economic resources. For example, an improvement in product costing system; requires an amount of money and time to get everything done.

Let’s understand Project Management!

Project management involves applying knowledge, skills, tools, and techniques to meet project objectives. It’s more than just organizational skills; it’s about solving problems and achieving specific goals with optimized use of resources. The projects are usually designed to address a particular problem. Hence, project management fundamentals involve defining the problem, selecting a strategy, planning the work, and ensuring the project meets its goals while meeting its cost budget.

Planning and execution are also an essential part of a project management. It involves detailed planning, identifying work, estimating time and costs, and managing resources. Clear objectives, requirements, and deliverables are essential for defining success criteria.

Characteristics of a Project Manager

A successful project manager needs a blend of technical skills, business expertise, problem-solving abilities, and interpersonal skills. The project manager must understand project planning, scheduling, and performance measurement. Commercial acumen is crucial to ensure the project delivers value. Strong leadership and the ability to inspire and guide a team are also essential, as project manager works with team members from diverse groups. Lastly, the projects often don’t go as planned, so problem-solving skills are essential to meet objectives within schedule and budget.

What is the Waterfall Project Management Lifecycle?

The Waterfall lifecycle is a traditional project management approach divided into five phases:

·       Initiating,

·       Planning,

·       Executing,

·       Monitoring & controlling, and

·       Closing.

Each phase must be completed before moving to the next. The waterfall lifecycle follows a sequential approach.

This method of project management works well for all projects with clearly defined goals and solutions. For example, the CFO of a company is acting as a project sponsor to implement a new financial reporting system. In such a case it may come with clearly defined objective, specific need and requirements for the new financial reporting system.

This method works well for projects with clear scope & deliverables. It is most effective for straightforward projects with little uncertainty and where the scope and deliverables are well understood. However, for projects with uncertainty and lack of clarity the below method known as Agile project management lifecycle may be opted.

The Agile Project Management Lifecycle

Agile project management is suited for projects where the solution is not clear from the start. It involves iterative cycles called Sprints, where small, functional parts of the project are developed and reviewed. Agile emphasizes flexibility, customer collaboration, and the ability to adapt to changes quickly.

Agile project management is an approach designed to handle projects where business needs frequently change or where there is a need to deliver value quickly.

The agile project management lifecycle has the following key characteristics:

• Iterations: Agile projects use Sprints to deliver partial sets of features at regular intervals, allowing for continuous improvement based on customer feedback. In Agile project management, a Sprint is a set period during which specific work has to be completed and made ready for review.
• Clients: Clients or customers are more involved throughout the project, providing feedback that helps to refine the solution obtained from each iteration.
• Flexibility: Initial goals are defined during the envisioning phase, but they can change as the project progresses following the iterative cycles and client feedback.
• Taskforce: Agile teams are typically small and composed of highly skilled members who are capable to work with minimal supervision.

The Agile lifecycle is composed of five stages: Envision, Speculate, Explore, Adapt, and Close.

• Envision: This initial stage involves defining the project goal, objectives, and boundaries. It sets the foundation for the project by establishing a clear vision and identifying the team and guidelines for collaboration.
• Speculate: In this stage, the team plans the iteration by identifying and prioritizing features to be developed. This planning is done for each iteration, allowing for flexibility and adjustments based on feedback and changing needs.
• Explore: The team builds and implements the features identified in the Speculate stage. This involves frequent collaboration and peer reviews to ensure the features meet the required standards and are production-ready.
• Adapt: After each iteration, the team reviews the results, gathers feedback, and makes necessary adjustments. This stage includes a retrospective to evaluate what worked well and what could be improved.
• Close: The final stage involves wrapping up the project, ensuring all features are complete, and documenting lessons learned.

An example of a project in a finance department where Agile Project management lifecycle applies would be a Real-Time Financial implementation Dashboard project. At the starting stage the senior finance executives as, key stakeholders may not be able to clearly define the outcome. And the objective of such a project could cover a high-level definition of the vision and high-level requirements for the real-time financial dashboard. This would require multiple iterations and continuous improvements to reach the desired outcome.

Organizational Structure and Projects Delivery

Organizational structure significantly impacts project execution. It influences how projects are performed, the authority of project managers, and the ease of project success.

• In a functional hierarchy, projects may struggle due to limited authority and resources.
• Matrix organizations balance functional and project management, providing more support for projects.
• Projectized organizations focus primarily on projects, granting project managers significant authority and dedicated resources.

Organizational Culture and its impact on Projects

Organizational culture shapes project outcomes through shared values, beliefs, and behaviors. A positive culture fosters motivation and collaboration, while a negative one can hinder project success. The organization’s mission, leadership style, and work environment all influence how projects are managed and executed.

The following slide explains the multiple leadership styles the can be adopted by project managers:

Project Management Software

Various software tools assist in project management, including scheduling software like Microsoft Project, Oracle Primavera, Smart Sheet and Jira, collaboration tools like Asana and SharePoint, and document management systems. These tools help in planning, tracking progress, managing resources, and facilitating communication among team members.

Initiating a Project

Initiating a project involves securing commitment from the client or customer or sponsor to move forward. This phase typically starts with the assignment of a project manager who guides the project through its initial stages. The project manager’s role includes defining the project, identifying the problem it aims to solve, and gathering essential information about objectives, requirements, and deliverables.

Project Stakeholders

Identifying stakeholders is crucial for project success. Stakeholders include anyone with a vested interest in the project, such as the client, customer, project sponsor, departments involved, and team members. Understanding their expectations, influence, and contributions helps build strong relationships and ensures their satisfaction with the project outcomes.

Analyzing stakeholders involves understanding their roles, influence, and interests in the project. This analysis helps prioritize stakeholders based on their interest and power, allowing the project manager to focus on key relationships. Effective stakeholder analysis ensures that influential stakeholders are engaged and supportive throughout the project.

Mendelow’s Matrix is a tool that can be used in project management to identify and prioritize stakeholders based on their power and interest in the project. For example, in an SAP implementation for a finance project, the CFO would have high power and high interest, making him/her a key player to engage closely. On the other hand, a regular employee might have low power and low interest, so they would be informed & monitored but not heavily involved. The below matrix may help project managers while dealing with stakeholders by giving focus to the most influential stakeholders in order to ensure project success.

The Project Goals and Project Objectives

The project goal is the end result that the project aims to achieve. It is essential to clearly define this goal to guide all project activities. Developing a concise problem statement helps in identifying the project goal. This statement should clearly articulate the problem or opportunity the project addresses, ensuring that all stakeholders have a shared understanding of the project’s purpose.

Project objectives provide detailed targets that support the overall project goal. These objectives can be business-related, financial, quality-focused, or technical. Using SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound) helps in defining clear and actionable objectives. Well-defined objectives guide the project scope, approach, and success criteria.

Project Deliverables, Success Criteria and Risk

Before we proceed to discuss about project deliverables and its success criteria let’s have a check on what are the key requirements need to be gathered for a Project. Gathering requirements involves identifying the specific needs and expectations of stakeholders. Accurate requirements are crucial for project success, as they define what the project must deliver. Techniques for gathering requirements include interviews, engaging with multiple teams, following some observations, and surveys. Clear and detailed requirements help ensure that the project meets stakeholder expectations and avoids unnecessary scope changes.

Project deliverables are the tangible or intangible results produced by the project. Success criteria are the standards used to measure the quality and completeness of these deliverables. Defining deliverables and success criteria helps in setting clear expectations and provides a basis for evaluating project performance. Deliverables should be specific and aligned with the project objectives, while success criteria should be quantifiable and agreed upon by stakeholders.

Lastly, we must proceed towards checking on key assumptions related to the project and its risks. Assumptions are factors considered true for planning purposes, while risks are potential events that could impact the project. Identifying assumptions and risks early helps in developing mitigation strategies. Assumptions should be documented and revisited as the project progresses. Risk management involves identifying, analyzing, and planning responses to risks to minimize their impact on the project.

Project Charter

Once the project manager is done with the initial part of the activities related to Project Management, it’s time to conclude the most important document in a Project, i.e. the Project Charter.

The project charter is a formal document that authorizes the project and outlines the project manager’s authority. It includes the project name, purpose, high-level description, objectives, scope, stakeholders, and a summary of the project plan. The charter is signed by the project sponsor and key stakeholders, signaling their commitment to the project. It serves as a foundational document that guides the project from initiation through completion.

The project charter is a crucial document in the project initiation phase. This document is essential for ensuring everyone involved understands the project’s purpose, scope, and the authority of the project manager.

• Authorization: It formally authorizes the project, giving the project manager the authority to use organizational resources for project activities.
• Definition: It includes a high-level description of the project, outlining the problem it aims to solve and the project’s objectives, requirements, and deliverables.
• Roles: The charter defines the roles and responsibilities of the project manager and other key stakeholders.
• Scope: It sets the scope and boundaries of the project, helping to manage expectations and guide the planning process. It is suggested to consider a project scope statement. The project scope statement defines the boundaries of the project, detailing what is included and excluded. It is a critical document that helps prevent scope creep by providing a clear reference for what the project will deliver. The scope statement includes the project goal, objectives, deliverables, success criteria, assumptions, risks, and constraints. It serves as a baseline for all project activities and decisions.

Sign-off: Typically, the project sponsor or customer signs off on the project charter, indicating their commitment and approval to proceed with the project.

Project Plan and Work Breakdown Structure

Project planning involves detailing the work required to complete a project. This includes breaking down tasks, estimating time and costs, scheduling, and planning for communication, quality, change, and risk management. A comprehensive project plan serves as a roadmap, guiding the project from start to finish.

A Work Breakdown Structure (WBS) is a hierarchical diagram that organizes project work into manageable sections. It breaks down the project into smaller components, making it easier to estimate time and costs, assign tasks, and track progress.

Building a WBS starts with identifying the top-level deliverables and then breaking them down into smaller, more manageable tasks. This process involves collaboration with the project team to ensure all necessary work is included and organized logically.

Work packages are the lowest level tasks in a WBS. They include detailed descriptions of the work to be done, success criteria, and how to measure completion. Creating work packages involves specifying the deliverables, resources needed, and time estimates for each task.

Time and Cost of a Project

Estimating time and cost of a project involves determining how long each task will take and how much it will cost. To make the best estimate of time and cost, you should consider the historical data from similar projects, expert judgment, and parametric models etc. Accurate estimates are crucial for developing a realistic project schedule and budget. Choosing the best estimate involves balancing accuracy with practicality.

The project budget should be prepared which is an estimate of the total cost to complete the project. It includes labour, materials, equipment, and other expenses. The budget should be detailed and realistic, providing a financial framework for managing project costs.

Resource Management Plan and Project Schedule

A resource management plan outlines the roles and responsibilities of the project team, the skills required, and how resources will be allocated. It includes a responsibility matrix, an organization chart, and a staffing plan, ensuring that the right people are available at the right times.

Building a project schedule involves sequencing tasks, assigning resources, and determining task durations. Dependencies between tasks must be identified to create a logical flow of work. The schedule should be realistic, taking into account resource availability and potential constraints.

Risk Management

Identifying risks involves recognizing potential events that could impact the project positively or negatively. This includes assessing the likelihood and impact of each risk and developing strategies to mitigate or capitalize on them.

A risk management plan outlines how identified risks will be managed. It includes risk responses, contingency plans, and a process for monitoring and controlling risks throughout the project. The plan ensures that risks are proactively managed to minimize their impact.

The quality standards for the project should be defined in order to minimize any possible risk in that aspect of the project. There should be quality assurance process to ensure that the project meets its objectives and quality control measures to verify that deliverables meet the required standards.

Change Management Plan

A change management plan outlines how changes to the project scope, schedule, or budget will be managed. It includes a process for submitting, evaluating, and approving change requests, ensuring that changes are controlled and documented.

Key aspects while executing the Project

Once planning is complete, the project moves into the execution phase. This begins with a kickoff meeting where the project sponsor and customer outline the mission and objectives, energizing the team. The project manager reviews the project plan, detailing how tasks will be managed, how communication will occur, and how changes will be handled. Setting up a project notebook, typically electronic, ensures that all project information is accessible to the team. Managing project work involves continuously aligning resources and tasks to keep the project on track.

Effective communication is crucial for project success. As a project manager, you must ensure your messages are clear and understood. Key techniques include:

• Relevance: Explain why the information is important to the audience.
• Clarity: Get to the point quickly to maintain interest.
• Tailoring: Customize your message to the audience’s needs and understanding.
• Positivity: Address problems with a proactive plan for resolution. Listening is as important as speaking. Pay attention to non-verbal cues and ensure your communication is two-way.

There should be more effective regular connect meetings among all the project team members. Meetings should be productive and focused. Start by defining the purpose and desired outcomes by using agenda, pre-read materials, minutes of meeting, and follow-ups etc.

Sequencing tasks is a crucial step in building a project schedule which involves arranging tasks in the order they need to be performed. This process transforms the Work Breakdown Structure (WBS) into a logical sequence of activities. Dependencies between tasks are identified, such as which tasks must be completed before others can start.

Following matrix may help in classifying project tasks into urgency & important and to be prioritized accordingly:

The resources should be assigned which involves determining who will perform each task and when they will be available. The resources for a Project may include team members, equipment, and materials etc. It’s important to assign resources only to the lowest-level tasks in the WBS, known as work packages. Resource availability and skill sets must be considered to avoid overloading team members and to ensure tasks are completed efficiently.

Managing team resources involves clearly defining roles and responsibilities. Set specific, achievable goals and provide the necessary support to remove obstacles. Respect and trust your team members, offering quick feedback and maintaining open communication.

Teams go through stages of development: forming, storming, norming, and performing. Initially, team members are getting to know each other and understanding their roles. Conflicts may arise during the storming stage as they work out their relationships. As they move to the norming stage, they start working more cohesively. In the performing stage, the team operates efficiently with minimal supervision.

Managing virtual teams presents unique challenges due to distance and lack of face-to-face interaction. Hence, video conferencing is ideal. Effective communication is key. Use clear, supportive, and respectful communication to build relationships.

Milestones are key points in the project schedule that signify the completion of major phases or deliverables. They help track progress and provide a clear indication of how much work has been completed. Milestones are useful for rescheduling and for highlighting important events, such as approvals or deliveries. They do not have durations but are critical for monitoring the project’s progress.

Monitoring and Controlling Processes and Performance

Gathering data is essential for tracking project progress. Key data points include actual start dates, hours worked, and costs incurred. Tracking these metrics helps in understanding how much work has been completed, how much remains, and whether the project is on schedule and within budget.

Managing project change involves implementing the change management plan developed during the planning phase. The changes should be controlled and documented, preventing scope creep and maintaining project integrity.

Managing project scope is crucial to prevent scope creep, which occurs when additional tasks are added without corresponding adjustments to the schedule or budget. Clear definition of scope during planning helps mitigate this risk. Any changes to the scope should go through the formal change management process, ensuring that all stakeholders agree to the modifications and their implications.

Risk management involves continuously monitoring identified risks and implementing planned responses. Each risk has an assigned owner responsible for tracking its status and executing mitigation strategies. Regular updates to the risk log and proactive management help in addressing risks before they impact the project significantly.

Evaluating progress involves comparing the current project status to the baseline plan. Tools like Gantt charts and variance analysis help in identifying tasks that are behind schedule or over budget. Early identification of issues allows for timely corrective actions, ensuring that the project remains on track.

When a project deviates from its plan, corrective actions are necessary. Techniques such as fast tracking, crashing, and assigning overtime can help in pulling the project back on schedule. Cost overruns can be addressed by finding less expensive resources or reducing scope. The chosen approach depends on the specific issues and requires appropriate approvals from stakeholders.

Closing the Project

Closing a project involves several key activities to ensure that all aspects are completed and documented. The most critical part is obtaining formal acceptance from the customer, confirming that the project has met its objectives. This is typically done through a sign-off meeting where stakeholders review and approve the final deliverables. Additionally, documenting lessons learned, producing final reports, and closing contracts are essential steps. Archiving project information and transitioning team members to their next assignments mark the final closure of the project.

Customer acceptance is achieved by running acceptance tests to demonstrate that the project deliverables meet the agreed-upon criteria. These tests are designed based on the success criteria defined during the planning phase. Once the tests are successfully completed, a sign-off meeting is held where the customer and key stakeholders formally approve the project completion by signing an acceptance document.

Documenting lessons learned is crucial for improving future projects. This involves identifying what worked well and what did not, and how processes can be improved. Regularly scheduling lessons learned sessions throughout the project helps capture valuable insights. These sessions should focus on both successes and areas for improvement, encouraging team members to share their experiences openly.

A close-out report should be prepared which summarizes the project’s performance, including what was accomplished, whether it met its objectives, and any significant variances from the plan. The report should detail the final schedule, costs, scope, and quality outcomes. It also includes a summary of lessons learned and recommendations for future projects. This report serves as a comprehensive record of the project and provides valuable information for stakeholders and future project teams.

PMBOK

The Project Management Body of Knowledge (PMBOK) is a comprehensive set of standard terminology, guidelines, and best practices for project management. It is compiled and published by the Project Management Institute (PMI).

The seventh edition of the Project Management Body of Knowledge (PMBOK) emphasizes creating organizational value through a value delivery system. This system aligns projects with the organization’s strategic goals, ensuring that each project contributes to the overall mission. It involves continuous feedback and adjustments to maximize the value delivered by projects.

PMBOK 7 introduces twelve principles that guide effective project management. These principles emphasize stewardship, team collaboration, stakeholder engagement, value delivery, holistic thinking, leadership, tailoring, quality, complexity management, risk management, adaptability, and change management. These principles provide a flexible framework for managing projects in various environments.

The new PMBOK focuses on eight performance domains that help achieve desired project outcomes. These domains include stakeholder engagement, team performance, development approach and lifecycle, planning, project work, delivery, measurement, and uncertainty management. Each domain encompasses activities that ensure projects deliver their intended benefits and value.