Week 3: The project management life cycle and methodologies

Introduction: The Project Management Life Cycle and Methodologies

Welcome to the world of project management! This tutorial will introduce you to the fundamental concepts of project management through the lens of the project life cycle and popular methodologies.

Understanding the Project Life Cycle:

Imagine a project as a journey with distinct stages. The project life cycle defines these stages, providing a framework for planning, executing, and closing a project effectively. Common phases include:

• Initiation: Defining the project goals, scope, and feasibility.
• Planning: Creating a detailed roadmap, including tasks, resources, and budget.
• Execution: Carrying out the planned activities and managing resources.
• Monitoring and Control: Tracking progress, identifying risks, and making adjustments.
• Closure: Evaluating success, documenting lessons learned, and releasing resources.

Exploring Popular Project Management Methodologies:

Two main methodologies guide project execution:

1. Waterfall:

• Structured and sequential: Follows a predefined plan with tasks completed in a specific order.
• Ideal for predictable projects: When requirements are clear and changes are minimal.
• Examples: Construction projects, product development with fixed specifications.

2. Agile:

• Iterative and incremental: Breaks down work into smaller cycles (sprints) with continuous feedback and adaptation.
• Adaptable to changing requirements: Embraces flexibility and responds well to uncertainties.
• Examples: Software development, marketing campaigns, creative projects.

Choosing the Right Methodology:

The best methodology depends on the project’s nature, complexity, and environment. Consider factors like:

• Project complexity: More complex projects may benefit from the flexibility of Agile.
• Requirements clarity: Waterfall works well for well-defined needs, while Agile thrives on changing demands.
• Team structure: Agile often requires close collaboration and self-organizing teams.

Benefits of Understanding the Project Life Cycle and Methodologies:

• Improved planning and execution: Provides a structured approach for managing projects effectively.
• Enhanced communication and collaboration: Creates a common language for stakeholders and team members.
• Greater adaptability and risk management: Enables adjustments to changing circumstances and minimizes risks.
• Increased project success rates: Provides tools and frameworks for achieving project goals on time and within budget.

Next Steps:

This is just the beginning of your journey into project management. As you delve deeper, you’ll explore each phase in detail, master specific methodologies, and gain practical skills to tackle any project with confidence.

Resources:

• Project Management Institute (PMI): https://www.pmi.org/
• Agile Alliance: https://www.agilealliance.org/
• Coursera Project Management Specializations: https://www.coursera.org/professional-certificates/google-project-management

Remember, project management is a continuous learning process. Practice, explore, and adapt to navigate the exciting world of bringing projects to life!

Welcome back. Before we move on, let’s recap what’s
already been covered. You learned how to define
project management, what a project is, what it isn’t, and how to explain its value to businesses. You also discussed when and why it’s necessary to have
a project manager, the role in day-to-day
responsibilities of a project manager, and the core skills needed to be a successful project manager. Now is a good time to stop and recognize how
much you’ve learned. By now you’re familiar with the job of project management, and you’ve started
learning what it takes to be an effective
project manager. Now you’ll go a little further, and learn some of the
ins and outs of the job, and before you know it, you’ll be ready to guide any project successfully.
Are you ready? Well, coming up, I’ll
introduce you to the two most popular
approaches to project management,
Waterfall and Agile. We’ll also cover the project
management life cycle and phases, and you’ll learn
about the different styles, scenarios, and factors
that can impact a project and its tasks at any given phase. When we’re done, you’ll be
able to explain and follow the life cycle of a project, define and outline
a project’s phases, and each phase’s tasks, compare different project
management methodologies to determine which methodology is most effective for a
project, and finally, organize how a project is run, according to different program
management methodologies. Ready? Let’s get started.

Exploring the Phases of the Project Life Cycle: A Roadmap to Success

Welcome to the world of project management! In this tutorial, we’ll dive deep into the project life cycle, the backbone of successful project execution. We’ll explore each phase in detail, equipping you with the knowledge and tools to guide your projects to completion with confidence.

What is the Project Life Cycle?

Imagine a project as a journey with defined milestones. The project life cycle is the map for this journey, outlining distinct phases that provide structure and guidance. These phases serve as checkpoints, ensuring all crucial aspects are addressed before moving forward.

Common Phases of the Project Life Cycle:

While specific names and sequence may vary slightly, most project life cycles follow a similar framework:

1. Initiation:

• This is the birthplace of your project, where the spark ignites!
• You’ll define the project’s purpose, goals, and deliverables.
• Identify stakeholders, resources, and feasibility.
• Conduct a risk assessment and secure project approval.

2. Planning:

• Time to chart the course!
• Break down the project into manageable tasks and milestones.
• Develop a detailed schedule and budget.
• Define communication channels and team roles.
• Choose appropriate project management tools and methodologies.

3. Execution:

• Roll up your sleeves, it’s go time!
• Assign tasks and monitor progress closely.
• Manage resources effectively and adapt to changing needs.
• Facilitate communication and collaboration within the team.
• Proactively identify and address risks and issues.

4. Monitoring and Control:

• Keep your finger on the pulse!
• Track progress against the plan and identify deviations.
• Analyze performance and make adjustments as needed.
• Manage risks proactively and mitigate potential problems.
• Ensure quality control standards are met.

5. Closure:

• Celebrate achievements and mark the finish line!
• Conduct a project evaluation to identify successes and lessons learned.
• Document the project history and best practices.
• Release resources and finalize financial obligations.

Why are the Phases Important?

Following the project life cycle provides several benefits:

• Structure and organization: Ensures all critical aspects are considered and addressed.
• Improved communication and collaboration: Creates a shared understanding of goals and expectations.
• Enhanced risk management: Proactive identification and mitigation of potential challenges.
• Greater control and adaptability: Allows for adjustments based on progress and changing circumstances.
• Increased project success rates: Provides a framework for achieving goals on time and within budget.

Exploring the Phases in Depth:

In the following sections, we’ll delve deeper into each phase, providing practical tips and insights to master their implementation. We’ll also explore different tools and techniques to effectively navigate each stage of your project journey.

Ready to embark on this exciting exploration? Stay tuned for the next parts of this tutorial as we unlock the secrets of each phase and empower you to become a project management pro!

Remember, the project life cycle is a flexible framework, not a rigid rulebook. Adapt it to your specific project needs and embrace continuous learning to unlock its full potential!

This is just the beginning of your journey into the fascinating world of project management. Let’s explore the phases in detail and equip you with the skills to tackle any project with confidence!

Identify the correct order of the project life cycle.

Initiate the project, make a plan, execute and complete tasks, close the project

That’s correct! Most project life cycles have four major phases, with each building on the one before it.

No two projects are
exactly the same, which means there are many
different ways to manage them. Each project comes with
its own needs and factors that impact how you’ll take action and achieve your goals. There are many ways
to manage projects and not always one
right way to do so. Picture this, you’re project managing a political campaign
for a local candidate. To make it happen, you need to think about things like your available resources, the people you’ll
be working with, the election date,
and the location. You need to be aware of lots of details to successfully
complete your project. Because so many different
things can impact a project, it’s important to understand
its basic structure. We call this structure
the project life cycle. The life cycle is a
great way to guide your project in the
right direction so that you and your project stay on track and end
up in the right place. Most project life cycles
have four major phases, each with their own set of tasks and concerns. Check it out. The main phases of a project
are initiate the project, make a plan, execute and complete tasks, and
finally, close the project. Let’s talk about the first phase, initiate the project. This is the launchpad for the entire process
of your project. In this phase, you’ll define project goals
and deliverables, identify the budget and
resources you’ll need, the people involved
in your project, and any other details that can impact the successful
completion of your project. You’ll document all
this information in one place to showcase
the project’s value, and hopefully get approval
to move forward with it. Once the project is approved, it’s time to get rolling. Next, you’ll make a plan for how you will meet the
goals of your project. There are all kinds of
ways to plan your project, and we’ll get into
some different methods and techniques later on. Right now, the important thing to know is that for
every single project, creating a plan of how you’re
going to meet your goals is absolutely 100 percent essential. Think about it. You can’t hire a contractor
to build a house without planning what it’ll look like or how much
you have to spend. These same considerations apply to any project that you manage. To be effective, your plan needs to include a lot of things. For example, a budget, a breakdown of all the tasks that you need to be completed, ways to communicate team roles and responsibilities, a schedule, resources, and what to do in case your project encounters
problems or needs to change. That’s just to name
a few. Once you have your plan in place, it’s time to execute and
complete those tasks. It’s important to point out that your project team has the job of completing
the project tasks. As a project manager, your role’s a little different. While you might be in charge of completing certain
tasks in the project, your primary tasks as
the project manager are to monitor progress and
keep your team motivated. You also remove any
obstacles that might come up so that the tasks are
executed well and on time. Finally, when all the
tasks have been completed, all the resources have
been accounted for and the project has crossed
the finish line, it’s time to close the project. Why is it important to close? One big reason is so your team has a moment to celebrate all of their hard work. Closing the project is also a chance to evaluate
how the project went. You can make note of
what worked and what didn’t so you can plan
better for next time. Even if the project
was a massive success, it’s helpful to take
time to reflect. Closing the project is also a great way to
connect with anyone outside your team who may have had interest in
the project’s goal. You can let everyone
know what was completed and what
you accomplished. Some projects like
the campaign example will have a firm end date. Once the project is
finished, that’s it. There’s no more work to do. Other projects have
different finish lines. For example, a project where you’re implementing a
new ordering system at a restaurant is complete after the system is set up and the
employees know how it works. At that point, your
goals are completed. It’s time to hand
over the project to another group whose job it is to provide
support and make sure the system stays running
on a day-to-day basis. Another example of this is, I once project managed the
creation of a dashboard that would be used by
various stakeholders in my organization. This dashboard would show pertinent information
to each stakeholder, depending on the
team that they were a part of in our
broader organization. I project managed the beginning, from writing up the vision for the project to the end where
we delivered the dashboard. Once I passed off
the final product, I transitioned the
continued update of each team’s data and the corresponding dashboard
page to the respective teams. Think of it like turning over the keys of a newly built
house to its new owner. The project of
building the house is complete and now it’s up to the owner to take care of the house’s maintenance and the upkeep. There you have it. The project life-cycle. The exact name for each
phase might change depending on the type of project or organization you work for. The general idea stays the same. Following the project processes you will learn in this course will set you up for
project management success. Next, we’ll take a closer
look into what happens during each phase of the
traditional project life cycle.

Tutorial: Summary of Project Life Cycle Phases – Initiate and Plan

Introduction:

Every successful project has a roadmap. The project life cycle defines that roadmap, outlining the key stages from conception to completion. This tutorial focuses on the initial stages: initiation and planning. Mastering these phases lays the foundation for a smooth and successful project journey.

Initiating the Project:

• Gather Intel: Start by collecting all available information about your project. This includes the problem you’re trying to solve, desired outcomes (deliverables), and potential resources.
• Goal Setting: Define your project’s objectives clearly. What do you want to achieve? These goals will guide your decisions and keep your team focused.
• Research and Brainstorm: Don’t jump to solutions too quickly! Investigate different approaches and generate creative ideas to meet your goals.
• Resource Roundup: Identify all the resources you’ll need to complete the project. This includes people, equipment, software, financial backing, and even physical space.
• Proposal Power: Document your findings and plans in a compelling project proposal. This document secures buy-in from decision-makers and becomes your blueprint for moving forward.

Planning Your Project:

• Budgeting for Success: Develop a realistic budget that allocates resources efficiently. Consider all potential costs and anticipate possible budget adjustments.
• Time is Money: Create a detailed project schedule. Break down tasks into manageable steps, define deadlines, and identify dependencies between tasks. Remember, flexibility is key, so make room for potential changes.
• Teamwork Makes the Dream Work: Assemble your project team, assigning roles and responsibilities based on each member’s skills and expertise. Foster collaboration and communication within the team.
• Risk is Real: No project is immune to surprises. Identify potential risks, like budget constraints or technical challenges, and develop contingency plans to mitigate their impact.
• Sharing is Caring: Communicate your plan with everyone involved in the project. Ensure your team understands their tasks and stakeholders are kept informed of progress and potential roadblocks.

Remember:

• Project life cycle phases may vary in names and specifics, but the core tasks within each phase remain consistent.
• Thorough planning is essential for smooth execution and avoiding costly mistakes.
• Building a comprehensive project proposal and involving key stakeholders early on increases project success.
• Adaptability is key – plan for potential risks and changes with flexibility in mind.

Next Steps:

This tutorial covered the crucial first steps of project initiation and planning. In the next steps, we’ll delve into the execution and completion phases, exploring how to bring your plan to life and achieve your project goals.

Bonus Tip: Utilize project management tools and software to streamline your planning process, manage resources effectively, and track your progress throughout the project lifecycle.

By mastering the initiation and planning phases, you’ll set your project on the path to success. Remember, a well-defined plan is the first step to building a rock-solid foundation for your project!

Now that we’ve discussed
the project life cycle, we’re going to explore some of the different tasks that match up with each life cycle phase. But first, let’s
review the phases. The project life cycle phases
are initiate the project, make a plan, execute
and complete tasks, and close out the project. Great. Let’s get
back to the tasks that need to be accomplished
during each phase. For this video, we’re
going to focus on the first two project
life cycle phases, initiating the project
and making a plan. It’s important to call
out that the name or tasks for each
phase might change, or may be a little different
depending on the type of project or the
organization where you work. At Google, we use a mix of different project
management methods, which you’ll learn more
about later in the course. But regardless of the method, all projects share a
lot of the same tasks needed to get the job
done. So, let’s get into it. The first step of the project life cycle is
to initiate the project. During initiation,
you’ll organize all of the information you have available to you
about your project. This way, when you’re
ready to continue on, you’ll be prepared for the next phase when you
can create your plan. Defining project goals makes
the details of your project clear so that you and your team can successfully
complete the project. For example, if the
project goal is to manage a political campaign,
then some deliverables, which are specific
tasks or outcomes, might be to raise $5,000 or get 500 signatures in support of your
candidate’s cause. With this in mind, you’ll need to do some
research to come up with ideas that will help
you meet your goals. You’ll also need to find out what resources are available. Resources can include people,
equipment, software programs, vendors, physical space
or locations, and more. Anything you need to
actually complete the project is
considered a resource. Now as a project manager, you’ll record all of these details in your
project proposal and then get them approved by a decision maker or group of decision makers at your company so that you can move ahead
with your project plans. Now in some cases, you may be the decision maker so be sure to consider the
same set of factors when initiating your project before
moving to the next stage. No worries, you will learn all the details about how to
create a project proposal. We will be getting into
more detail of what this is and how to create one
later in the course. Voila, once your
project is approved, you’ll move into the second step of the project life cycle, which is to make a plan. In this phase, you’ll
create a budget and set the project schedule. You’ll establish
the project team and determine each person’s
roles and responsibilities. Let’s pause for a second. You may be thinking, “Why
can’t we just get started?”, but that’s the thing
with project management, deliberate planning is critical
to a project’s success. A crucial part of
project management is planning for risk and change. An experienced project manager knows that plans always change. This ability to adapt is all about thinking
and planning ahead. Scheduling delays,
budget changes, technology and software
requirements, legal issues, quality control, and access
to resources are just some of the more common
types of risks and changes that a project
manager needs to consider. So, it’s important to keep
in mind that planning is key to reducing those risks. But don’t worry, if the idea of risks seems a little
overwhelming right now, in later courses, we’ll teach you all about understanding risks. Just know that it’s
really important not to skip this step and to
always make a plan. Again, the success of your
project depends on it. Once you have a plan, you’ll communicate all of this
information to your team. That way, each member will know which tasks they’ll own and what to do if they have questions or if they
run into problems. You’ll also communicate
your plan with others who have an interest
in the project success, so that they are aware
of your plans and your progress as the project
continues to move forward. Nice job, we’ve made it halfway through the steps
of a project life cycle. Up next, we’ll check out
the remaining two phases, executing and completing tasks and closing the project.
Catch you in a bit.

What does a project manager do in the project initiation phase of the project life cycle? Select all that apply.

Define project goals

During the project initiation phase, project managers define project goals to clarify the details of a project. They also need to determine resources, people, and project details and get project approval from decision makers at the company.

Determine resources, people, and project details

During initiation, project managers organize all of the information they have available to them about a project. This includes defining project goals; determining resources, people, and project details; and getting project approval.

Get project approval

Project managers need to get project approval by sharing a project proposal with decision makers at the company. They also need to define project goals and determine resources, people, and project details. This all happens in the project initiation phase.

Project Management Tutorial: Executing, Completing, and Closing Your Project

From Plans to Action:

Welcome back! You’ve laid the groundwork with meticulous planning. Now, it’s time to transition from blueprints to action. This tutorial explores the crucial phases of execution, completion, and closing in the project management life cycle.

Phase 1: Execution – Orchestrating Action:

• Teamwork Makes the Dream Work: Delegate tasks effectively, ensuring team members understand their roles and responsibilities.
• Eyes on the Prize: Monitor progress closely, track deadlines, and proactively address any deviations from the plan.
• Clear Communication is Key: Maintain open communication channels. Regular meetings, progress reports, and timely updates keep everyone informed and aligned.
• Mastering Obstacles: Anticipate challenges and roadblocks. Quickly address resource constraints, budget adjustments, or technical glitches to avoid delays.

Phase 2: Completion – Crossing the Finish Line:

• Task Verification: Double-check that all tasks, both originally planned and newly added, are completed satisfactorily.
• Financial Housekeeping: Settle outstanding invoices, return resources used, and reconcile project expenses according to the budget.
• Documenting for Future Reference: Consolidate all project documentation, including plans, reports, and communication logs, for future reference and potential audits.
• Final Approval: Secure confirmation from stakeholders that the project has met its objectives and delivered the desired outcomes.

Phase 3: Closing – Reflection and Celebration:

• Learning from the Past: Conduct a retrospective to analyze successes and identify areas for improvement. Capture valuable lessons learned for future projects.
• Knowledge Sharing: Disseminate the project’s findings, documentation, and insights to stakeholders and relevant teams.
• Celebrating Achievements: Acknowledge and celebrate the team’s effort and dedication. Recognition boosts morale and fosters a positive project culture.
• Formal Release: Release team members and resources from the project, allowing them to move on to new endeavors.

Pro Tips:

• Embrace flexibility and adapt to unforeseen circumstances. Agile methodologies excel in such situations.
• Document everything! Clear records ensure smooth transitions and avoid confusion down the line.
• Celebrate milestones along the way to keep the team motivated and engaged.
• Remember, effective communication is your most valuable tool.

Next Steps:

• Master the popular Waterfall and Agile project methodologies to choose the best fit for your project.
• Explore project management tools and techniques to streamline execution, completion, and closing tasks.
• Continuously hone your project management skills and build your knowledge base.

Remember: Executing, completing, and closing are not simply finalizing tasks. They are opportunities to refine your project management approach, celebrate achievements, and prepare for future successes. Take control, communicate effectively, and enjoy the satisfaction of bringing your project to life!

This tutorial provides a roadmap for navigating the final stages of your project journey. By embracing these steps and adapting them to your specific needs, you can ensure a smooth execution, a satisfying completion, and a successful closure for your project.

Welcome back. We just learned about the core tasks that need to be completed in the
first two phases of the project life cycle, initiating the project
and making plans. Now, it’s time to put
your plans into action. Remember, it’s not your job
to actually do all the tasks. Your primary job as
the project manager is to manage the progress
of the project as a whole. This means you’ll oversee
your team’s efforts and make sure
everyone understands what’s expected of them, what tasks need to be done, and how and when to
complete those tasks. It’s also your job to help
remove any obstacles and to alert the right
people if it looks like there might be a
delay to the project. This means you’ll need to
communicate with your team, and anyone else involved in your project through meetings, written communications
like memos, emails or internal chat tools, and other working documents
like task reports. Quick pro tip, if in doubt, err on the side of
overcommunication. As your project progresses you’ll make adjustments
to the schedule, budget, and allocation
of resources, clearly communicating
updates all along the way. When all the tasks are complete and you’ve met the project goal, it’s time to close the project. This phase is usually
overlooked because it’s easy to assume that once the project
goal has been delivered, everyone can move on. But hold up, there’s still a
lot that needs to be done. First, check to make sure all
tasks have been completed, including any work that
was added along the way. Be sure any outstanding
invoices have been paid, resources are returned
and accounted for, and project documentation
has been submitted. Next, and this is very important, get confirmation that
the final outcome of your project is acceptable to the people you’re
delivering it to. It is crucial to your
project’s success that the person who
asked you to manage the project is satisfied
with the end result. Once your project has been
accepted as meeting its goals, take some time to reflect on what went well and maybe
what didn’t go so well. This reflection is usually
called a retrospective, and it’s a chance to
note best practices and learn how to manage your project more effectively next time, even if everything went great. The notes from your retrospective
are also valuable to the people or organization receiving the end
result of the project. That’s because they can use
that information to inform decisions about
their business the next time they
consider a project. Now it’s time to collect all the project
documentation that you created or collected
along the way, including all of your
plans and reflections, and share the final results of your project with
your stakeholders. Remember, stakeholders
are people who are interested in and affected by the project’s
completion and success. Depending on the type of project, stakeholders could
include a department or organization’s
management team, clients or customers of
your product or service, users of your new
tool or process, or even the community at large if you’re planning a
community town hall meeting. Pro tip, stakeholders play a huge role in the development, and success of your project. You’ll learn a lot more about
these key players later on. But for now, just know
that they’re like the VIPs of your project. Next, take some time to celebrate the effort your
team invested in the project. Celebrations help people feel good about the work they’ve done, and think of the work
as uplifting and rewarding because it truly is. Some ideas for small
celebrations are a company or team-wide email, thanking the team and
acknowledging individual efforts. Now for big projects, you may even consider
a company party to celebrate the team
and the project success. To wrap up, you and your team
can formally move on from the project so that you can pursue new projects
in the future. Well, as you can see, being a project manager
is a lot of work, but it’s very rewarding,
and it’s all, well, manageable when you follow through with the
project life cycle. You can see how the
organization, communication, and improvements you
add to various areas of a project can make the entire team more
effective and efficient, and you can have an impact on many areas of a project in a way that’s greater than
if you focused on any one task on the project. Similar to a coach
with a sports team, even though you aren’t actually playing a direct
role in the game, your guidance, your
communication, and your team-building can make the difference in a happy, high-performing, and
successful team. In later courses we’ll discuss each of these
project phases, and you’ll learn methods, techniques, and
tools to help you. For now, we just
want you to become familiar with the general
project management process, and we’ll share some
of the terms and concepts used in the field that you’ll need to know as you develop your project
management skills. Up next, we’ll
introduce you to two of the more popular
project methodologies, Waterfall and Agile.
See you soon.

Which of the following activities are part of the “execute and complete tasks” project phase? Select all that apply.

Communicate with the project team

Project managers should err on the side of overcommunication when sharing information with the team through meetings, emails, memos, and more. In this phase, project managers also manage project progress and make adjustments to the project as necessary.

Manage project progress

To manage project progress, project managers oversee the team’s efforts and make sure everyone understands what’s expected of them and how and when to complete key tasks. In this phase, project managers also make needed adjustments and communicate with the team and stakeholders.

Make adjustments to the project

Project managers make adjustments to the project as necessary. This can include updating the schedule, budget, and allocation of resources. In this phase, project managers also manage progress and communicate with the team and stakeholders.

Project Management Methodologies: Choosing the Right Tool for the Job

In the vibrant world of project management, there’s no one-size-fits-all approach. Different projects, like building a rocket compared to organizing a charity event, require a unique blend of tools and processes. This tutorial explores the diverse landscape of project management methodologies, equipping you with the knowledge to select the ideal fit for your next venture.

The Methodology Menagerie:

• Waterfall: The granddaddy of methods, Waterfall follows a structured, sequential flow. Imagine pouring water through a series of steps, each completed before moving to the next. It’s ideal for well-defined projects with minimal anticipated changes, like constructing a building.
• Agile: Embrace flexibility with Agile! Projects unfold in iterative cycles called sprints, each delivering a working piece of the puzzle. Feedback and adjustments happen within each cycle, making it perfect for adapting to new information and evolving requirements, like developing software.
• Scrum: A popular Agile framework, Scrum emphasizes short sprints (usually 2 weeks) and focuses on delivering valuable increments quickly. Think of it as building a ship in smaller, functional sections rather than waiting for the entire vessel to be complete.
• Kanban: Visualize workflow with Kanban! Tasks flow through boards representing different stages (e.g., To Do, In Progress, Done). It’s like a traffic light for your project, ensuring smooth progress and preventing bottlenecks.
• Lean: Optimize and eliminate waste! Lean principles focus on maximizing value delivery while minimizing time and resources. Think of it as streamlining your project without sacrificing quality, like a well-oiled machine.

Matching Tools to Needs:

Choosing the right methodology depends on several factors:

• Project Complexity: Simpler projects might do well with Waterfall, while complex ones might benefit from Agile’s adaptability.
• Goal Clarity: Well-defined goals might point towards Waterfall, while flexible goals might favor Agile or Kanban.
• Risk Tolerance: Rigid projects might find comfort in Waterfall, while projects open to experimentation might embrace Agile.

A Hybrid World:

Remember, methodologies are not mutually exclusive. Many projects, like Google’s, adopt a hybrid approach, borrowing elements from various frameworks to create a custom fit. The key is understanding the core principles and tailoring them to your specific project needs.

Tips for Methodology Masters:

• Know your project inside and out: Before choosing a methodology, thoroughly understand your project’s goals, resources, and potential challenges.
• Seek expert guidance: Consult experienced project managers or mentors to gain insights and recommendations.
• Be flexible and adaptable: Projects, like life, can be unpredictable. Be prepared to adjust your methodology as needed.
• Communicate effectively: Keep stakeholders informed about the chosen methodology and its implications.

Mastering the methodologies toolbox empowers you to tackle any project with confidence. Choose wisely, adapt creatively, and watch your projects soar!

Stay tuned for further exploration of specific methodologies and practical tips for their implementation!

Welcome back, as we’ve already discussed,
not all projects are alike. Different types of projects will
benefit from applying different project management approaches or methodologies. A project management methodology
is a set of guiding principles and processes for
owning a project through its life cycle. Project management methodologies help guide project managers throughout
a project with steps to take, tasks to complete, and principles for
managing the project overall. We will talk through two different types,
linear and iterative. Linear means the previous phase or task has to be completed
before the next can start. A linear approach would work well for
a project like building a house. You’d need the blueprint created before
you can begin laying the foundation. You’ve got to know exactly what the house
will look like, its dimensions, and what type and
how many resources you’ll need. Then you’ve got to finish the foundation
before you put up the walls and the walls before you put up the roof and
so on before you have the finished project,
which is a bungalow-style home. There’s also a clear goal, you know
exactly what the house will look like. It’s unlikely that in the middle
of building the house, your client is going to decide they’d
rather have a multi-level Victorian instead of a single-level bungalow. What’s more, even if they
wanted to change, it’s too late, you already laid the foundation and built
the walls for the bungalow, done and done. A bungalow is what they wanted, and
a bungalow is what they’ll get. Using this type of linear
project management approach, completing each step in order and sticking
to the agreed upon specific results and being able to deliver just
what the client ordered. For a project like producing a new
show for a television company, on the other hand, it might be more effective to use
a methodology that uses an iterative, more flexible approach where some of the phases in tasks will
overlap or happen at the same time that other tasks are being worked on. Your team comes up with an idea for
a show and films a pilot. You ran several tests of the pilot in
different locations and time slots. As your team gathers feedback about the
pilot, adjustments to the show are made. At the same time,
you’re able to make decisions and start working on other parts of
the project, like hiring permanent actors, starting film production,
and working on advertising even while the final version of
the show is being worked on. And even though the overall goal is clear,
produce a new show, the type of show could end up being
different from the original idea. Your team may have started out
creating a one-hour show, but during testing they realized a half-hour
show would actually be more popular. Or maybe a supporting character
got a lot of positive feedback, so you want to make them one
of the main characters. What’s more important is that you produce
a show that audiences are going to watch. Because of the iterative approach,
plans remain flexible and you’re able to make
adjustments as you go along. Each of these projects, benefits from
a different approach to how tasks will be carried out,
in order to best meet the project’s goals. Linear projects don’t require many
changes during development and have a clear sequential process. If you
stick to the plan, it’s likely you’ll finish your tasks within the time
schedule and all other criteria. Iterative projects allow for
more flexibility and anticipate changes. You’re able to
test out parts of the project to make sure they work before
the final result is delivered, and you can deliver parts of
the project as they are completed, rather than waiting for
the entire project to be done. Over the years, the field of project management has
developed many different methods that project managers can choose from that
will help them manage most effectively. Google takes a hybrid approach
to project management. We mix and match from different methods
depending on the type of project. Our project managers are encouraged
to adapt their own style to what makes the most sense to
their project and their team. So are you starting to see how different
approaches might benefit the projects you’ll be working on now? Pretty soon you’ll become a pro
at picking an approach or combining approaches to
fit with your project. Up next, we’ll learn about the most well
known and most used project management methods that you can add to your
project management tool box.

What is a project management methodology?

A set of guiding principles and processes for owning a project through its life cycle

A project management methodology is a set of guiding principles and processes for owning a project through its life cycle. The method can be linear (with one task completed before the next can begin) or iterative (with some tasks happening at the same time).

Project Management Methodologies: Waterfall vs. Agile – Choosing the Right Tool for the Job

Imagine two teams building a house. One meticulously pours concrete footings, lays bricks precisely, and meticulously installs the roof, only to realize halfway through they accidentally built a bungalow instead of the desired two-story mansion. The other adapts on the fly, adjusting room sizes based on feedback, even swapping the kitchen and living room after realizing the flow works better that way. Welcome to the world of project management methodologies, where Waterfall and Agile represent two distinct approaches.

Waterfall: The Structured Builder

Think of Waterfall as a blueprint built from concrete. Each phase – Initiating, Planning, Executing, and Closing – follows a rigid sequence, like water cascading down a waterfall. This structured approach thrives on:

• Crystal-clear goals: The final vision is defined upfront, minimizing mid-project course corrections.
• Clearly defined tasks: Dependencies between tasks are mapped out, ensuring smooth sequencing.
• Limited room for change: Once a phase starts, adjustments are costly and potentially disruptive.

Ideal for:

• Software development with well-defined specifications.
• Construction projects with detailed blueprints.
• Marketing campaigns with fixed timelines and deliverables.

Agile: The Adaptive Architect

Agile embraces change like a sculptor molding clay. Instead of a rigid blueprint, projects unfold in iterative cycles called sprints, each delivering a working piece of the puzzle. Feedback and adjustments are woven into the process, making Agile ideal for:

• Uncertain requirements or evolving goals: Adapt to changing client needs or market dynamics.
• High risk and uncertainty: Minimize wasted effort by testing and iterating early and often.
• Collaborative environments: Foster team flexibility and rapid feedback loops.

Ideal for:

• Developing software with evolving user needs.
• Launching marketing campaigns with continuous optimization.
• Managing projects with high levels of complexity and unknowns.

Choosing the Right Tool:

The best methodology is like the perfect tool for the job. Consider:

• Project complexity: Simple projects might flourish with Waterfall’s predictability, while complex ones might need Agile’s adaptability.
• Goal clarity: Well-defined goals might favor Waterfall, while flexible goals might thrive with Agile.
• Risk tolerance: Rigid projects might find comfort in Waterfall, while experimental projects might embrace Agile.

Hybrid Approaches:

Remember, methodologies are not mutually exclusive. Many projects, like Google’s, adopt a “hybrid” approach, borrowing elements from both Waterfall and Agile to create a custom fit. The key is understanding the core principles and tailoring them to your specific project needs.

Mastering the Methodologies:

• Know your project inside and out: Before choosing a methodology, thoroughly understand your project’s goals, resources, and potential challenges.
• Seek expert guidance: Consult experienced project managers or mentors to gain insights and recommendations.
• Be flexible and adaptable: Projects can be unpredictable. Be prepared to adjust your methodology as needed.
• Communicate effectively: Keep stakeholders informed about the chosen methodology and its implications.

By understanding Waterfall and Agile, you can choose the right tool for the job, build your project management toolbox, and watch your projects soar!

Next: Explore other popular methodologies like Scrum, Kanban, and Lean Six Sigma, and learn how to combine them for maximum success!

Remember, the perfect project management approach is like finding the right key for your project’s unique lock. Choose wisely, adapt creatively, and unlock your project’s full potential!

Two of the most popular project
management methodologies are Waterfall and Agile. Each of these methods has a
rich and complex history. In fact, you could take
an entire certificate on just one of these
methods alone. You’ll have a chance to learn
more about Waterfall and Agile methods in the upcoming courses
of this certificate. Be sure to check those out after completing this
one to learn more. For now, I’ll just give you a brief introduction and
provide you with some examples that illustrate how
different types of projects can be more successful or easier to manage when you consider
which method to use. First, let’s take a look
at the Waterfall approach. Waterfall as a methodology
was created in the 70s, and refers to the sequential
ordering of phases. You complete one at a
time down the line like a waterfall starting
at the top of a mountain and traveling
to the bottom. Remember the definition and example of linear
from that last video? Well, Waterfall has
a linear approach. At first, Waterfall was used in the physical
engineering disciplines like manufacturing
and construction, then software emerged as an important field of engineering and Waterfall was applied
to those projects as well. It still used a lot
in engineering fields including product feature
design and application, also known as app design. Over time, other industries
like event planning and retail have adapted
Waterfall phases to fit their projects. There are now many
styles of Waterfall, and each style has its own
specific set of steps. What they all have
in common, though, is that they follow an
ordered set of steps that are directly linked to clearly
defined expectations, resources, and goals that
are not likely to change. Let’s take a closer look. The phases of a Waterfall
project life cycle follow the same standard
project life cycle flow that you learned about earlier. Initiating, planning, executing, which includes managing and completing tasks, and closing. When would you want to use a Waterfall approach
to project management? Well, when the phases of the
project are clearly defined or when there are tasks to complete before
another can begin, or when changes to
the project are very expensive to implement
once it’s started. For example, if you
are catering an event for a client on a
very tight budget you might want to use
Waterfall methodology. This way, you could confirm
the number of guests first, then very clearly
define the menu, get approval and agreement
on the menu items and costs, order the unreturnable
ingredients, and successfully feed the guests. Because the budget is limited, you can’t afford to make
changes or waste food. The traditional method won’t
allow for the client to make changes to the menu once
the order has been placed. You can also reserve
tables, chairs, and dishes because
you know exactly how much and what kind of
food is being prepared. A well-thought-out
traditional approach to managing a project
can help you reach your desired outcome
with as little pain as possible during the
project implementation. By spending extra effort thinking through the
entire project upfront, you’ll set yourself
up for success. In an ideal world, following this
approach will help you identify the right
people and tasks, plan accordingly to avoid
any hiccups along the way, create room for documenting
your plans and progress, and enable you to hit that goal. However, plans don’t always
go according to plan. In fact, they rarely do. The Waterfall method has some risk management practices to help avoid and deal
with project changes. Luckily, there are
other methodologies that are entirely built for
change and flexibility. One of these is Agile, another popular project
management approach. The term agile means being able to move quickly and easily. It also refers to flexibility, which means being willing and
able to change and adapt. Projects that use an
Agile approach often have many tasks being worked
on at the same time, or in various stages of completion which makes it
an iterative approach. The concepts that shaped Agile methodology
began to emerge in the 90s as a response to the growing demand for
faster delivery of products, mainly software
applications at that time. But it wasn’t officially
named Agile until 2001. The phases of an Agile
project also follow the project life cycle stages we described earlier,
generally speaking. However, rather than
having to always go in order or wait for one phase to end before
starting the next, Agile project phases overlap and tasks are completed
in iterations, which in Scrum, are
called sprints. Scrum is a form of Agile
that you’ll learn more about in the course
focused entirely on Agile, and by sprint, we do not mean running a race
as fast as possible. In this case, sprints are short chunks of
time usually one to four weeks where a
team works together to focus on completing
specific tasks. What’s important to understand
is that Agile is more of a mindset than just a
series of steps or phases. It’s concerned with
building an effective, collaborative team that seeks regular feedback from
the client so that they can deliver the
best value as quickly as possible and adjust
as changes emerge. Projects that are best suited for an Agile approach are
those where the client has an idea of what they want but doesn’t have a concrete
picture in mind, or they have a set of qualities they’d like to
see in the end result, but aren’t as concerned with
exactly what it looks like. Another indicator
that a project may benefit from Agile is the level of high uncertainty and risk involved
with the project. We’ll talk more about
those things later. An example of a project
that would work well with an Agile approach might
be building a website. Your team would build the different parts
of the website in sprints and deliver each part to the client as they are built. This way, the website can be
launched with some parts, say the main homepage that are complete and ready
for public view, while other parts, maybe the company blog
or the ability to book online appointments, continue to get built out over time. This allows the team to get feedback early on about what
works and what doesn’t, make adjustments along the way, and reduce wasted efforts. This same website example, the Waterfall method will
plan for and require the whole website to be
complete before it can launch. Having a basic understanding of Waterfall and Agile will help you figure out an effective way to organize and plan
out your project. Knowing about these
two methodologies will come in handy during
future job interviews, because you’ll be
able to demonstrate a solid understanding of the project management landscape. Waterfall and Agile are two of the more common and well-known project
management methodologies, but they’re by no means
the only or the best ones. In the next videos, you’ll learn about
Lean Six Sigma, another way to approach projects. Here at Google, believe it or not, we select from many of these methodologies for
project management.

When would a project manager want to use the Waterfall approach? Select all that apply.

When the phases of the project are clearly defined

Waterfall has a linear approach. It follows an ordered set of steps that are linked to clearly defined expectations, resources, and goals that are not likely to change. This is a helpful approach when the phases of the project are clearly defined.

When project changes are expensive to implement once it’s started

Waterfall has a linear approach. It follows an ordered set of steps that are linked to clearly defined expectations, resources, and goals that are not likely to change. This is a helpful approach when project changes are expensive to implement once it’s started.

When there are tasks to complete before another can begin

Waterfall has a linear approach. It follows an ordered set of steps that are linked to clearly defined expectations, resources, and goals that are not likely to change. This is a helpful approach when there are tasks to complete before others can begin.

Lean Six Sigma & DMAIC: Supercharge your Project Management Toolbox

Hey project champions! Ready to dive deeper into the world of Lean Six Sigma and its powerful DMAIC process? This tutorial will equip you with the tools and knowledge to conquer complex projects, eliminate waste, and deliver maximum value.

Lean Six Sigma: The Efficiency Powerhouse

Think of Lean Six Sigma as a superpower duo. Lean, with its focus on eliminating waste and maximizing value, joins forces with Six Sigma’s data-driven approach to minimizing defects and variability. The result? Projects that are leaner, meaner, and deliver outstanding results.

DMAIC: The Five-Step Masterplan

DMAIC is the roadmap to Lean Six Sigma excellence. Each step guides you through the process of turning process pain points into polished perfection:

1. Define:

• Clarify the problem: Identify the area for improvement, set specific goals, and define success metrics.
• Gather stakeholder input: Understand their needs and expectations to ensure project alignment.
• Create a project charter: Document the defined purpose, scope, and resources.

2. Measure:

• Collect data: Gather quantifiable information about the current process, using tools like surveys, observations, and performance metrics.
• Identify critical measures: Focus on data points that directly impact your defined goals.
• Analyze process variation: Understand the sources and impacts of process inconsistencies.

3. Analyze:

• Dig deep into the data: Use statistical tools and techniques to identify root causes of problems and opportunities for improvement.
• Validate findings: Confirm the accuracy of your analysis through additional data collection or experimentation.
• Develop improvement options: Brainstorm and evaluate potential solutions based on your analysis.

4. Improve:

• Implement the chosen solution: Design and execute a plan to implement the chosen improvement, considering feasibility and potential risks.
• Monitor and measure: Track the impact of the implemented solution on your defined metrics.
• Refine and adjust: Make necessary adjustments to the solution based on real-time data and feedback.

5. Control:

• Standardize the improved process: Document and communicate the new process to ensure consistent execution.
• Monitor performance: Keep a watchful eye on process metrics to identify and address any deviations.
• Continuous improvement: Foster a culture of continuous learning and improvement, seeking new opportunities to optimize the process.

Unlocking the Benefits:

DMAIC offers a treasure trove of benefits for project managers:

• Structured approach: Provides a clear roadmap for project execution, minimizing chaos and confusion.
• Data-driven decision making: Ensures solutions are based on objective data, not just gut feeling.
• Waste reduction: Eliminates inefficiencies and maximizes resource utilization.
• Improved quality: Minimizes defects and errors, leading to higher customer satisfaction.
• Enhanced collaboration: Encourages teamwork and fosters a problem-solving mindset.

Real-World Application:

Imagine you’re managing a project to increase online store conversion rates. You use DMAIC:

• Define: The problem is low conversion rates, the goal is a 20% increase, and success is measured by sales and abandoned cart metrics.
• Measure: You analyze website traffic, user behavior, and cart abandonment data.
• Analyze: You discover issues with the checkout process and confusing product descriptions.
• Improve: You redesign the checkout process, simplify product descriptions, and A/B test different variations.
• Control: You monitor performance, make adjustments as needed, and institutionalize best practices.

The Google Way:

At Google, we embrace a hybrid approach, blending methodologies like Agile and Waterfall with Lean Six Sigma principles. We choose the tool that best fits the project, leveraging DMAIC to streamline processes and achieve optimal results.

Mastering the Craft:

Remember, becoming a Lean Six Sigma and DMAIC master takes time and dedication. Here are some key takeaways:

• Understand the core principles: Get a solid grasp of Lean Six Sigma philosophy and the DMAIC framework.
• Practice makes perfect: Apply DMAIC to real-world projects, starting small and building your experience.
• Seek continuous learning: Stay updated on new tools and techniques in Lean Six Sigma and project management.
• Embrace collaboration: Leverage the power of your team to brainstorm solutions and share knowledge.

With dedication and practice, you can transform your project management skills and deliver results that wow even the most demanding stakeholders. So, go forth, champions, and conquer the world of project management with the power of Lean Six Sigma and DMAIC!

Remember, the journey to project management mastery is a continuous one. Keep learning, keep exploring, and keep exceeding expectations!

In which DMAIC step do project managers begin to identify gaps and issues?

Analyze

In DMAIC, the analyze step is when project managers learn what to improve by identifying gaps and issues.

Hey again. Now, you’ve
got Waterfall and Agile methodologies in your
project manager toolbox, Lean Six Sigma is one
more you can add. It’s a combination of two
parent methodologies, Lean and Six Sigma. The uses for Lean Six Sigma are common in projects that
have goals to save money, improve quality, and move
through processes quickly. It also focuses on team collaboration which promotes a positive work environment. The idea is that when
your team feels valued, motivation and
productivity increases and the whole process
functions more smoothly. There are five phases in the
Lean Six Sigma approach. They are define,
measure, analyze, improve, and control,
commonly known as DMAIC. DMAIC is a strategy for
process improvement, meaning you’re
trying to figure out where the problems are in the current process and fix them so that everything
runs more smoothly. The goal of each
step is to ensure the best possible results
for your project. Just like with
Waterfall and Agile, there’re more specific
details for using DMAIC and the Lean
Six Sigma approach. But what’s great about
the DMAIC process is that it can be used to solve any business problem.
Let’s break it down. The first phase is to define the project goal and what
it will take to meet it. This first phase
is very similar to the initiation phase of
traditional project management. Let’s take a real
scenario to illustrate. Imagine that you
are brought on as a project manager for a
large travel company to help streamline and minimize
customer service wait times that have been surging due to a recent
sales promotion. Before you begin working
on tackling the issue, you’re going to need to define the project goal and talk to stakeholders about
expectations for the project. In this case, the goal is
to take average wait times down to less than 10 minutes on average compared
to 30 minutes. Next, it’s time to measure how the current
process is performing. In order to improve processes, DMAIC focuses on data. Here you want to map out the current process and
locate exactly where the problems are and what kind of effect the problems
have on the process. Using our example, you’re trying to figure out why it’s taking so long for the travel company to address a customer
service issue. To do this, you look at company data like
average wait times, number of customers per day,
and seasonal variations. Then you’ll set a plan
for how you’ll get that data and how
often to measure it. This could look something like having the company generate reports on a weekly,
monthly, quarterly basis. In other situations,
you might have employees or customers fill out surveys or look at inventory, shipping, and tracking
records, things like that. Once you have the data
and measurements, you can move on to the next
phase which is analyze. Here, you’ll begin to
identify gaps and issues. In our example, after mapping out the process
and data points, you may see that staffing is inadequate on days where
customers are the highest. Data analysis is important for project managers regardless of which method you
choose and we will learn more about that
in an upcoming course. From your data, you’ll have a strong understanding of causes and solutions to get to
the next stage, improve. Oftentimes, project managers may want to leap straight
to this phase but really projects in process
improvements should only be made after
a careful analysis. This is the point
where you present your findings and get ready
to start making improvements. In our example, this could be modifying staffing to
address customer needs. The last step of this
cycle is control. You’ve gotten the process
and project to a good place, and now it’s time to implement
it and keep it there. Controlling is all about
learning from the work you did up front to put new processes and documentation in place
and continue to monitor so the company doesn’t
revert back to the old, inefficient
way of doing things. To sum it all up, you can
remember DMAIC like this, defining tells you
what to measure, measuring tells you
what to analyze, analyzing tells you
what to improve, and improving tells
you what to control. Lean Six Sigma and the DMAIC approach are ideal when the project
goal includes improving the current
process to fix complex or high risk problems
like improving sales, conversions, or
eliminating a bottleneck, which is when things get
backed up during a process. Following the DMAIC process prevents the
likelihood of skipping important steps and increases the chances of a
successful project. As a way for your
team to discover best practices that your
client can use going forward, it uses data and focuses on the customer or end-user
to solve problems in a way that builds on previous
learning so that you can discover effective
permanent solutions for difficult problems. There are many ways out
there that break the flow of project management into
digestible phases and approaches, all with the same end goal of accomplishing the desired outcome as smoothly as possible and
delivering the best value. Like I said earlier, at Google we follow a lot
of different approaches. For instance, an
engineering team releasing a customer-focused product may primarily use Agile when
creating the product, but decide to plug in
some of the aspects of Waterfall project management for planning and documentation. A customer service team might focus on using Lean
Six Sigma to improve an experience for our users like offering new features based
on a recent analysis. But the team might
develop parts of the code and roll out
the features using Agile iterations and sprints
to allow for change. Or one of our internal
education and training teams may focus solely on Waterfall project management
to achieve a targeted goal of having all employees complete an annual
compliance training. Here, Waterfall makes sense
since the requirements of the training program are fixed and so is the deadline and goal. The biggest takeaway is to
know the various methods and tools to be able to confidently apply what
works best for you, your team, and the end goal. There is no real prescription for how to execute a project perfectly because there’re always pieces you can’t 100
percent control. But the good news is, you can
get pretty close with the skill sets you develop
through learning about these different frameworks.

Congrats on completing this module
on the project life cycle and project management methodologies. So what did you think? Hopefully, this introduction to a few of
the core project management methodologies and hearing from a Googler about the
way we approach project management here at Google has you interested and
excited to keep on learning. One of the great things
about project management is that it can be really creative and present you with challenging problems
to solve that have a rewarding impact. You get to work with teams full of
interesting, skilled, and dedicated people who help with the problem-solving and
idea-generating process. Every project is an opportunity
to learn and try something new. Waterfall, Agile, and Lean Six Sigma
are solid foundations from which to build your understanding
of project management. Each methodology has its own set
of rules, values, and processes. There is no such thing as a right or
a wrong methodology. There is no one-size-fits-all
approach to take, and there is almost no limit to the number
of ways you can blend different approaches to fit
the needs of your project. Your goal in choosing a methodology is to
maximize the use of resources and time. The method, or combination of methods, will help you reach your goal in the most efficient and effective way. This might feel like choice overload right
here, but hang in there. With time and practice, you will become more
comfortable with the benefits and limits of different methodologies, and you’ll be able to approach your
project assignments with confidence. Next, you’ll build on these foundations by
learning how an organization structure and culture can impact the way
you manage your project. See you soon.