Chapter 3: Types of Project Management

A method rooted in structured sequences leading to a final outcome. This approach offers simplicity and predictability, albeit at the expense of flexibility.

Waterfall project management thrives in endeavors characterized by a singular, substantial deliverable such as constructing a building. However, its effectiveness diminishes when confronted with projects necessitating adaptability, susceptible to alterations, or demanding the synchronization of interdependent tasks, like software development.

The notable advantages of Waterfall lie in meticulous planning, organizational efficiency, and an elevated level of control over individual project tasks and the overarching schedule. Nevertheless, this methodology poses challenges when confronted with unforeseen circumstances or changes in project scope, potentially resulting in extended timelines, increased resource allocation, and escalated costs.

Within Waterfall-managed projects, teams often rely on Gantt charts—a visual tool that presents project tasks in a sequential manner—to maintain clarity and alignment. For further insights on Gantt charts, please refer to Chapter 9.

Introducing Agile project management, a category of project management methodologies that champions adaptability and continuous improvement over rigid, sequential processes. Within the realm of Agile, numerous popular methodologies have emerged, each with its unique characteristics and merits. Let's delve deeper into these methodologies below.

Agile project management, a dynamic and collaborative approach, revolves around completing smaller, incremental tasks and then consistently reviewing, refining, and iterating based on feedback from end users and ever-evolving demands.

In 2001, a group of visionary software developers sought to revolutionize project management by fostering a more flexible and collaborative method. Their revolutionary ideas were crystallized in the Manifesto for Agile Development, which sets forth four core values:

1. Emphasizing individuals and interactions over processes and tools
2. Prioritizing working software over comprehensive documentation
3. Promoting customer collaboration over contract negotiation
4. Favoring the ability to respond to change over adhering to a rigid plan

At the heart of Agile project management lies a profound commitment to nurturing a collaborative relationship between the project team and the end user. While the customer defines the project objectives, the deliverables remain malleable as the team incrementally executes each task. In Agile, every development feature takes the form of a user story, reflecting how the end user will interact with it.

Initially conceived for software development, Agile project management has now transcended boundaries and become a widely adopted approach across diverse industries and project types. To gain comprehensive insights into the Agile process and its implementation, we invite you to explore our comprehensive guide to Agile PM.

Agile project management pluses and minuses

Agile proves to be an ideal fit for projects that demand a high degree of flexibility and are prone to evolving throughout the project lifecycle. Noteworthy advantages of adopting Agile include:

1. Reduced upfront planning
2. Enhanced open communication
3. Continuous feedback loops
4. Flexible objectives

When effectively employed, Agile often leads to expedited project delivery, fostering a competitive edge.

Nevertheless, embracing this flexible approach comes with tradeoffs:

1. Ambiguous delivery dates, potentially leading to scope creep
2. Demanding significant dedication and adaptability from the project team

Agile isn't always the right fit

It is crucial to bear in mind that Agile may not be suitable for everyone. The methodology might not align with your team if any of the following circumstances apply:

1. Your project lacks a sense of urgency.
2. Your client's expectations are incompatible with Agile principles—for instance, if they require final approval at every stage or incremental delivery does not align with the project specifications.
3. Your organization or your client's organization necessitates meticulous documentation at every phase.
4. Your current processes are not conducive to a more flexible approach.
5. Your team or organization has no prior experience with Agile, and the implementation process would be excessively burdensome in terms of cost or time.

In the subsequent sections, we will explore alternative methodologies falling within the Agile family.

Agile Methodologies: Scrum and Kanban

When it comes to Agile methodologies, two prominent approaches are Scrum and Kanban. Each method brings its own unique benefits and considerations to the table.

Scrum: Agile with a Focus on Incremental Progress

Scrum, renowned as the most popular Agile methodology, revolves around small teams working on time-bound sprints to tackle different aspects of a larger project or release. This approach promotes responsiveness in customer relationships, cost-effective development, enhanced job satisfaction, and immediate returns. As the project unfolds, Scrum acknowledges the complexities of multiple moving parts, diverse teams, and varying goals.

To maintain structure throughout each sprint, Scrum teams engage in four regular meetings, or ceremonies:

1. Sprint planning: In this meeting, the team presents the product, discusses concerns and feedback, prioritizes tasks, and estimates the timeline.
2. Daily stand-up: A daily debriefing session where the team establishes a plan for the day, addresses concerns, and collaboratively resolves issues.
3. Sprint review: Held at the end of each sprint, this meeting offers stakeholders transparency by showcasing the working product and highlighting the team's achievements during the sprint.
4. Sprint retrospective: Occurring after each sprint, this meeting focuses on evaluating team performance and devising strategies to enhance future efforts.

Within the Scrum framework, specific team members hold designated roles:

1. Product owner: A crucial figure with a comprehensive understanding of the product's business value. They act as the bridge between stakeholders and the development team, prioritizing user stories and communicating requirements effectively.
2. Development team: The technical backbone responsible for analyzing, designing, coding, testing, and communicating on the product. They work based on the user stories provided by the product owner.
3. Scrum Master: A facilitator who collaborates closely with the product owner and development team to streamline workflow, eliminate distractions, and ensure the Scrum team's progress.

While Scrum finds its roots in software development, its adaptability extends to marketing, design, and other creative projects. Explore our comprehensive guide to implementing Scrum with the right tools for further insights.

Kanban: Embracing Continuous Improvement

Kanban, an Agile framework, prioritizes continuous improvement through incremental enhancements of products or services. Teams utilizing Kanban organize work items based on their capacity and employ a visual kanban board to track task status effectively.

Originating in Japan during the 1940s, Kanban emerged from the innovative practices observed in supermarkets. Inspired by this, Toyota engineer Taiichi Ohno implemented a supply-and-demand system on the factory floor, leading to significant improvements in inventory management.

The concept of a "kanban," meaning a visual sign or card, was introduced by Toyota's teams to communicate their readiness to take on new tasks or materials. Workers would "pull" additional work when they had the capacity, resulting in reduced work in progress (WIP). This approach is now commonly referred to as the just-in-time (JIT) method.

Utilizing a Kanban board lies at the heart of the methodology. Whether physical or digital, the board typically consists of three columns or lanes: to-do, doing, and done. Team members move task cards across these columns to visualize and manage task progress. This provides a quick overview of work items and ensures teams have sufficient capacity to take on new tasks.

In recent years, many teams have transitioned to online, digital kanban boards. These platforms facilitate collaboration among distributed teams and offer real-time visibility into project progress. Discover more about setting up a Kanban board by referring to our comprehensive guide.

Kanban pluses and minuses

Kanban proves highly beneficial for teams handling numerous incoming requests, operating on short work cycles, and seeking flexibility with resources and scheduling. However, it may pose challenges for teams working on interconnected, dependent tasks or those subject to tight deadlines.

In summary, Scrum and Kanban present distinct methodologies within the Agile realm. While Scrum emphasizes incremental progress through sprints and structured ceremonies, Kanban focuses on continuous improvement and resource management using visual boards. Both approaches offer valuable insights and advantages, depending on the specific needs and characteristics of your project or team.

Discover the art of project estimation with the powerful Critical Path Method (CPM). This technique unveils the intricate order in which you must conquer project tasks, allowing you to visualize their interdependencies and achieve success.

Embrace the following fundamental steps of CPM:

1. Unveiling the Task Landscape: Uncover all the tasks that comprise your project, leaving no stone unturned.
2. Untangling the Web of Dependencies: Explore the intricate web of dependencies among the tasks, unraveling their interconnectedness.
3. Crafting the Network Tapestry: Carefully weave the tasks together, creating a masterful network diagram that illuminates their relationships.
4. Calculating the Tapestry's Timelines: Diligently estimate the duration of each task, meticulously calculating the threads of time required.
5. Uniting the Threads of Time: Thread by thread, sum up the durations to reveal the grand tapestry's total duration, capturing the essence of your project.
6. The Crucial Path Unveiled: Unveil the critical path, a sacred trail composed of tasks of utmost importance, essential for the project's completion.
7. The Dance of Progress: Witness the evolution of the critical path as your project progresses, comparing estimated timelines with the actual tempo.

By embracing CPM, teams can slice through project timelines with precision. The method empowers you to prioritize and schedule crucial tasks while concurrently orchestrating parallel endeavors. Moreover, CPM bestows the gift of foresight, enabling accurate estimates of task duration for future projects. Dive into the realm of project planning, armed with the ability to effortlessly reference projected versus realized project schedules. Let CPM guide your path toward efficient project execution and unrivaled estimation prowess.

Change management encompasses a wide array of methodologies that aid individuals, teams, and organizations in implementing new processes or achieving transformative change. Let's delve into two distinct approaches: event chain methodology and extreme project management.

For a comprehensive understanding of change management, we invite you to peruse our indispensable guide or access free change management templates.

Event Chain Methodology

Within the event chain methodology, the primary focus lies in identifying tasks (referred to as events) and their interconnectedness (known as event chains). By doing so, the objective is to effectively allocate resources, evaluate and mitigate project risks.

The underlying goal of event chain methodology is to gauge the necessary time and resources required to accomplish a project. Although it shares some similarities with the critical path method, where activities are subdivided into smaller tasks while outlining their dependencies and durations, event chain methodology diverges by aiming to create a realistic timeline and budget. Its purpose is not solely to enhance task management and sequencing, but rather to construct a robust framework that accounts for unforeseen risks.

Change management initiatives frequently employ event chain methodology to obviate the need for extensive project overhauls, which can prove exceedingly time-consuming and resource-intensive.

Extreme Project Management

Extreme project management (commonly known as XP or XPM) serves as an effective means to navigate significant changes within compressed timeframes. Ideally suited for fast-paced, intricate projects, XPM embraces a trial-and-error approach to successfully execute ambitious endeavors.

Consider XPM as the antithesis of Waterfall methodology. Instead of adhering to a linear, pre-determined project development process, XPM grants the freedom to adapt project plans, budgets, and final deliverables in response to evolving requirements. In XPM, the responsibility lies with the project team to self-correct and adapt as needed.

Extreme project management excels in environments fraught with uncertainty, although it proves less advantageous for projects characterized by well-defined timelines, budgets, and scopes.

When it comes to optimizing work processes, a fresh perspective emerges through process-based methodologies. Rather than adhering to rigid frameworks for individual projects, these methodologies view work as a collection of interconnected processes. They often form an integral part of broader business process management (BPM) strategies, allowing for a holistic approach to improvement.

Let's delve into two influential methodologies: Lean and Six Sigma.

Lean: Maximizing Value, Minimizing Waste

With its roots in 1950s manufacturing, Lean has evolved into a versatile approach applicable across various industries. Its primary goal is to maximize value while minimizing waste, ensuring a more efficient and streamlined workflow. To achieve this, Lean follows five fundamental principles and activities:

1. Define value: Recognize the perceived value of each product or service from the customer's perspective.
2. Map the value stream: Chart the entire process (value stream) and identify areas of waste, such as redundant steps, resource inefficiencies, or time delays.
3. Create flow: Devise a plan that eliminates the identified waste, promoting smooth and uninterrupted progress.
4. Employ a pull system: Progress through the plan based on the customer's needs, preventing overwhelming workloads or bottlenecks.
5. Pursue perfection: Continuously improve the process, striving to eliminate as much waste as possible.

Six Sigma: Elevating Quality through Statistical Precision

Focusing on quality improvement, Six Sigma adopts a statistical approach to identify and eliminate defects within project deliverables. By optimizing processes and targeting the root causes of defects, Six Sigma seeks to enhance reliability and accuracy. Its core steps involve:

1. Finding defects: Carefully inspect the project and identify areas with flaws or deviations.
2. Identifying causes: Analyze and determine the underlying factors contributing to the defects.
3. Eliminating causes: Implement strategies to address and remove the identified causes, leading to quality enhancements.
4. Optimizing processes: Continuously refine processes to increase their dependability and minimize future defects.

Two prominent Six Sigma methodologies are widely used:

1. DMAIC: Define, Measure, Analyze, Improve, Control. This methodology aims to improve existing processes.
2. DMADV: Define, Measure, Analyze, Design, Verify. It is particularly effective for creating new processes or products.

Although there isn't a centralized certification body for Six Sigma, numerous organizations offer training to facilitate its implementation.

Lean Six Sigma: Uniting Efficiency and Quality

Merging the Lean principle of waste reduction with the Six Sigma emphasis on defect elimination, Lean Six Sigma provides a compelling hybrid approach to process improvement. By synergizing these methodologies, organizations unlock a range of benefits, including:

• Enhanced cost savings by minimizing defects and errors
• Improved overall quality of outputs
• Time saved through reduced process issues
• Data-driven decision making
• Continuous process improvement ingrained within the organization's culture

While Lean Six Sigma originated in manufacturing, its advantages extend to various sectors such as healthcare, construction, design, and government.

In summary, these process improvement methodologies offer distinct approaches to enhance efficiency and elevate quality standards. Embrace the power of Lean and Six Sigma to drive impactful improvements across your processes, projects, and products.

Explore the following project management methodologies that are gaining momentum in the modern world of project management.

PRINCE2

PRINCE2, short for Projects in Controlled Environments, is a project management methodology that places great emphasis on precisely defining and delivering work according to specific requirements. In contrast to Agile PM, PRINCE2 prioritizes meticulous planning and thorough documentation of work items.

Originally developed for information technology (IT) projects to minimize cost and time overruns, PRINCE2 has now expanded its reach to various industries.

This approach proves effective for projects with clearly established objectives. However, if you require more flexibility or lack sufficient time for comprehensive planning and documentation, Agile methods may present a more suitable alternative.

PRiSM

Projects Integrating Sustainable Methods (PRiSM) represents a contemporary project management methodology that places utmost importance on sustainability. The primary goal of PRiSM projects is to reduce the environmental impact of a project and drive significant social change. The model is built on the following principles:

1. Commitment and accountability
2. Ethical decision making
3. Integration and transparency
4. Principled and values-based deployments
5. Social and ecological equity
6. Economic prosperity

Implementing PRiSM requires a long-term shift in mindset that places sustainability and equity at the forefront of all processes and projects, with the aim of maximizing value for all stakeholders involved.

By implementing an organization-wide project management method, teams can establish a unified framework to effectively navigate various project aspects such as resources, budget, communication, timeline, and more.

Undoubtedly, teams and projects possess distinct needs for planning, adaptability, and documentation. The abundance of available options often makes it challenging to determine the ideal approach.

Nonetheless, through a comprehensive evaluation of your customary project types and existing workflows, you can pinpoint the methodology that best suits your requirements and yields optimal outcomes.

Occasionally, organizations may even opt for multiple project management types to cater to the diverse demands of their projects and teams.

To find the perfect project management methodology, it's crucial to delve into the specifics of your project and carefully evaluate your existing systems and processes. By considering both your requirements and the resources already in place, you can make an informed decision on the most suitable approach.

Begin by posing the following inquiries to assess your project's needs:

A. Setup

• What is the primary focus of the project?
• Which industry does it belong to?
• How intricate is the project?
• Does it have the potential for scalability?

B. Planning

• To what extent can you adjust the timeline, budget, and deliverables?
• How much upfront planning is necessary?

C. Resources

• What is the allocated budget, and how adaptable is it?
• What resources are currently available, and what additional resources will be required?

D. Dates

• How flexible is the project timeline?
• Are there predefined start and end dates?
• Does the project involve significant milestones or a critical path?

E. People

• How many individuals or teams will collaborate on this project?
• What is the level of specialization required for the work?
• How involved are the customers and stakeholders?

Once you've examined the project-related questions, follow these steps to determine the most compatible methodology:

1. Outline the primary variables that will influence the project, such as the dates, resources, and people.
2. Consider how each methodology will impact these variables. For instance, assess how a more flexible approach might affect a strict deadline.
3. Evaluate the advantages and disadvantages of each methodology in relation to your project's needs. Consider both the best fit and the least disruptive option for your existing processes.
4. Engage in collaborative discussions with other team members to gather input and perspectives.
5. Introduce the selected methodology to the entire team, ensuring that everyone is educated about the new processes. Establish the necessary tools and documentation systems.
6. Implement the methodology in the project and closely monitor its progress for success.

‍