Project Management Guidance

1. Project Management
Starters

2. Common Terms
Project manager -
A project manager is
the role a person plays
to ensure that a
project goes smoothly
from beginning to end.
Stakeholders -Project
stakeholders are the
people who are directly
impacted by the
project you are working
on. This could mean
the team directly
working on it, tertiary
teams who need to
learn a new process, or
the company CEO to
ensure that the
business continues to
run smoothly.
Deliverables -
Deliverables are the
product or products of
what you expect to
have at the end of your
project. Deliverables
can be a wide range of
assets, both internally
facing towards your
team members, or
externally facing
towards customers.
Some examples of
deliverables include an
entirely new product, a
sales deck, an increase
in traffic, or a feature
update.
Project timeline -
A project timeline is a
project management
tool that helps you
visualize how pieces of
your plan all fit
together. A project
timeline can help you
list out specific
dependencies during
the project planning
process.
Dependencies-
Dependencies are tasks
that rely on the
completion of other
tasks before they can
be performed. A good
example of this would
be legal review.
Certain tasks—like
presenting a sales
deck—cannot progress
further until they get
approval from the legal
team. That means the
sales deck presentation
task is dependent on
the legal team's
approval. .

3. Common Terms
DEPENDENCIES-
DEPENDENCIES ARE TASKS
THAT RELY ON THE
COMPLETION OF OTHER
TASKS BEFORE THEY CAN
BE PERFORMED. A GOOD
EXAMPLE OF THIS WOULD
BE LEGAL REVIEW.
CERTAIN TASKS—LIKE
PRESENTING A SALES
DECK—CANNOT PROGRESS
FURTHER UNTIL THEY GET
APPROVAL FROM THE
LEGAL TEAM. THAT MEANS
THE SALES
DECK PRESENTATION TASK
IS DEPENDENT ON THE
LEGAL TEAM'S
APPROVAL. .
GANTT CHART
:A GANTT CHART IS A
TYPE OF VISUAL
PROJECT
MANAGEMENT THAT
DISPLAYS A PROJECT IN
THE FORM OF A
TIMELINE. IT'S AN EASY
WAY TO TRACK A
PROJECT LIFECYCLE
AND ESTIMATE END
DATES FOR CERTAIN
PROJECT ACTIVITIES.
RESOURCE
MANAGEMENT
:RESOURCE
MANAGEMENT IS THE
PROCESS OF PLANNING
AND SCHEDULING YOUR
TEAM’S RESOURCES
AND ACTIVITIES. A
RESOURCE CAN
INCLUDE EVERYTHING
FROM EQUIPMENT AND
FINANCIAL FUNDS TO
TECH TOOLS AND
EMPLOYEE
BANDWIDTH—
BASICALLY, ANYTHING
THAT HELPS YOU
COMPLETE A PROJECT
PROJECT BUDGET
:A PROJECT BUDGET IS
THE SET AMOUNT OF
RESOURCES YOU'RE
ABLE TO USE FOR A
SPECIFIC PROJECT. A
PROJECT BUDGET CAN
BE SET IN HOURS, LIKE
IN THE AGENCY WORLD,
OR DOLLAR AMOUNT
PROJECT
PLAN:A PROJECT PLAN
(OR PROJECT
MANAGEMENT PLAN) IS
A DETAILED MAP OF ALL
OF THE ELEMENTS
YOUR TEAM NEEDS TO
ACCOMPLISH TO REACH
YOUR PROJECT'S
GOALS.
PROJECT OBJECTIVES
:A PROJECT
OBJECTIVE IS THE GOAL
YOU SET TO ACHIEVE
BY THE END OF A
SPECIFIC PROJECT.
THIS IS THE MAIN
REASON WHY A
PROJECT IS
HAPPENING.

4. Common Terms
Project objectives :
A project objective is the
goal you set to achieve by
the end of a specific
project. This is the main
reason why a project is
happening. A project
objective could be a
tangible finished asset, such
as a new product, or it
could be a specific goal you
want to accomplish, such as
increasing your social media
followers by 300%.
Key performance
indicators (KPI):A key
performance indicator
(KPI) is a metric that
showcases how your team is
progressing toward a
specific goal or project
objectives.
Project scope :A project
scope clearly identifies the
goals, deadlines, and
deliverables that a project
is set to complete in a
specific period of time.
Setting a project scope
ahead of time can help
team members individually
manage their time and
stakeholders will know
when to expect changes as
the project progresses.
Scope creep:Scope creep is
what happens when a
project's tasks and
deliverables begin to
exceed the allotted project
scope a project manager
has set. While scope creep
is not inherently bad, it can
drastically shift the amount
of time it takes to complete
a project if not monitored
and managed carefully.

5. Common Terms
Agile :The Agile methodology is an iterative form of project management. Software development
teams often run Agile, since their project needs can change very rapidly. Instead of working in one
big chunk of work, Agile instead focuses on smaller increments so that work can quickly shift towards
a different strategy if needed. This ensures that the changes made to the product are focused on
what's best for the end user.
Waterfall model: Waterfall project management is a linear form of project management in which
each step of the project is dependent on the previous step. The waterfall model often involves a
large amount of planning before the execution begins to ensure that all dependencies are accounted
for. The waterfall model is often visualized in a Gantt chart.
Kanban :Kanban is a form of visual project management often represented by Kanban boards. In a
Kanban board, work is displayed in a project board that is organized by columns, with each task
being a “card” in the appropriate column. Columns often represent a stage of work, and cards are
“pulled” from a backlog as they progress through the next stage of the process.
Scrum:Scrum is a subset of Agile methodology in which teams learn about past experiences to
influence the next steps of their project. In a Scrum team, there is one individual, known as the
Scrum master, who helps guide teams through each of the scrum stages.

10. PMBOK 7 guide

11. PMBOK-7 Principles
(Stewardship) Pay Attention/Care: Be a diligent, respectful, and caring steward. Carry out activities
with integrity, care, and trustworthiness while maintaining compliance with internal and external
guidelines. They demonstrate a broad commitment to the financial, social, and environmental
impacts of the projects they support.
Team: Create a collaborative project team environment. Project teams that work collaboratively can
accomplish a shared objective more effectively and efficiently than individuals working on their
own.
Stakeholders: Engage stakeholders to understand their interests and needs.
Value: Focus on value. Align the project with the objectives of the organization. Continually
evaluate and adjust project alignment to business objectives and intended benefits and value
System thinking: Recognize, evaluate, and respond to system interactions, with the aim to respond
to the dynamic circumstances within and surrounding the project in a holistic way to positively
affect project performance.
Leadership: Motivate, influence, train and learn. Demonstrate leadership behaviors in areas of
honesty, integrity, and ethical conduct and adapting leadership style to the situation.
Tailoring: Adapt the approach of deliveries according to the context. Adaptability is the key through
the use of an iterative approach.

12. PMBOK-7 Principles
Quality: Incorporate quality into processes and results. Maintain a focus on quality that
produces deliverables that meet project objectives and align to the needs, uses, and
acceptance requirements set forth by relevant stakeholders.
Complexity: Address complexity using knowledge, experience, and learning. Continually
evaluate and navigate project complexity so that approaches and plans enable the project team
to successfully navigate the project life cycle.
(Risk) Opportunities and threats: Optimize responses to opportunities and threats. Maximize
positive impacts and minimize negative impacts to the project and its outcomes.
Adaptability and resilience: Be adaptable and resilient depending on the context to help the
project accommodate change, recover from setbacks, and advance the work of the project.
Change management: Enable change to achieve the expected future state.

13. MS Project Tools