Certification in Project Management

Virtued Academy International

Page 1 of 153
 Contents

Introduction to Project Management ................................................................... 6

The Project Phases ................................................................................................... 8
Project Management Office (PMO) .................................................................... 10
Introduction to the Project Initiation Phase ......................................................... 11
Elements of the Project Initiation Phase............................................................... 12
Defining Project Goals ........................................................................................... 13
Creating a Business Case ...................................................................................... 14
Doing Project Feasibility Study .............................................................................. 18
Doing Risk Assessment ........................................................................................... 21
Creating Project Charter....................................................................................... 22
Listing the Stakeholders ......................................................................................... 26
Introduction to the Project Planning Phase ........................................................ 27
Elements of the Project Planning Phase .............................................................. 28
Defining Project Scope.......................................................................................... 29
Project Plan and Schedule ................................................................................... 33
Gantt Chart ............................................................................................................ 38
Creating Communication Plan ............................................................................ 40
Setting a Budget .................................................................................................... 43
Defining Roles and Responsibilities ....................................................................... 45
Introduction to the Project Execution Phase ...................................................... 47
Elements of the Project Execution Phase ............................................................ 48
Allocating Project Resources ................................................................................ 49
Developing Products or Process ........................................................................... 50
Check Status and Track the Project .................................................................... 51
Setting KPIs .............................................................................................................. 52
Ensuring Quality ...................................................................................................... 53
Forecasting ............................................................................................................. 54
Meetings and Troubleshooting ............................................................................. 55
Introduction to the Project Monitoring and Controlling Phase ......................... 56
Elements of the Project Monitoring and Controlling Phase ............................... 57
Tracking Effort and Cost ........................................................................................ 58
Monitoring Project Progress................................................................................... 59
Page 2 of 153
Ensuring Adherence .............................................................................................. 60
Preventing any Chance for Disruption ................................................................ 61
Introduction to the Project Closing Phase ........................................................... 62
Elements of the Project Closing Phase ................................................................ 63
Handover of Deliverables ..................................................................................... 64
Reviewing Project Deliverables ............................................................................ 65
Getting Project Results Approved ........................................................................ 66
Documenting Project Learnings ........................................................................... 67
Project Leadership ................................................................................................. 68
Human Resource Management .......................................................................... 69
Public Relations Management ............................................................................. 70
Service Sector Management ............................................................................... 71
Cost Management ................................................................................................ 72
Procurement Management ................................................................................. 73
Risk Management .................................................................................................. 74
Performance Management ................................................................................. 75
Ethical Issues and Professionalism in Project Management .............................. 76
Introduction to Agile .............................................................................................. 77
Uses, Pros, and Cons of Agile ................................................................................ 78
Key Agile Principles and Concepts ...................................................................... 79
Agile Terminologies ................................................................................................ 80
Getting started with Agile ..................................................................................... 81
Career in Agile ....................................................................................................... 82
Professional Agile Leadership (PAL I) ................................................................... 83
Professional Agile Leadership - Evidence Based Management (PAL-EBM) ..... 84
Introduction to Scrum ............................................................................................ 85
Uses, Pros, and Cons of Scrum .............................................................................. 86
Key Scrum Principles and Concepts .................................................................... 87
Scrum Terminologies .............................................................................................. 88
Getting started with Scrum ................................................................................... 89
Career in Scrum ..................................................................................................... 90
Certified Scrum Master (CSM) .............................................................................. 91
Professional Scrum Master (PSM) .......................................................................... 92
Scrum Master Professional Certificate (SMPC).................................................... 93
Professional Scrum with User Experience (PSU) ................................................... 94

Page 3 of 153
Professional Scrum with Kanban (PSK) ................................................................. 95
Disciplined Agile Scrum Master (DASM) .............................................................. 96
Scaled Professional Scrum (SPS) ........................................................................... 97
Professional Scrum Developer (PSD) .................................................................... 98
Scrum Product Owner (PSPO) .............................................................................. 99
Introduction to Kanban ....................................................................................... 100
Uses, Pros, and Cons of Kanban ......................................................................... 101
Key Kanban Principles and Concepts ............................................................... 102
Kanban Terminologies ......................................................................................... 103
Getting started with Kanban .............................................................................. 104
Career in Kanban ................................................................................................ 105
Introduction to Scaled Agile Framework® (SAFe) ............................................ 106
Uses, Pros, and Cons of SAFe .............................................................................. 107
Key SAFe Principles and Concepts .................................................................... 108
SAFe Terminologies .............................................................................................. 109
Getting started with SAFe ................................................................................... 110
Career in SAFe ...................................................................................................... 111
Certified SAFe Practitioner (SP)........................................................................... 112
Certified SAFe Scrum Master (SSM) .................................................................... 113
SAFe Agilist (SA) .................................................................................................... 114
Certified SAFe DevOps Practitioner (SDP) ......................................................... 115
Certified SAFe Program Consultant (SPC) ......................................................... 116
Certified SAFe Product Owner/Product Manager (POPM) ............................. 117
Introduction to Jira............................................................................................... 118
Uses, Pros, and Cons of Jira................................................................................. 119
Key Jira Principles and Concepts ....................................................................... 120
Jira Terminologies ................................................................................................. 121
Getting started with Jira ...................................................................................... 122
Career in Jira ........................................................................................................ 123
Introduction to PRINCE2 ...................................................................................... 124
Uses, Pros, and Cons of PRINCE2 ........................................................................ 125
Key PRINCE2 Principles and Concepts .............................................................. 126
PRINCE2 Terminologies ........................................................................................ 127
Getting started with PRINCE2 ............................................................................. 128
Career in PRINCE2................................................................................................ 129

Page 4 of 153
Introduction to Oracle Primavera ...................................................................... 130
Uses, Pros, and Cons of Oracle Primavera ........................................................ 131
Key Oracle Primavera Principles and Concepts .............................................. 132
Oracle Primavera Terminologies ........................................................................ 133
Getting started with Oracle Primavera ............................................................. 134
Career in Oracle Primavera................................................................................ 135
Introduction to Trello ............................................................................................ 136
Uses, Pros, and Cons of Trello .............................................................................. 137
Key Trello Principles and Concepts .................................................................... 138
Trello Terminologies .............................................................................................. 139
Getting started with Trello ................................................................................... 140
Career in Trello ..................................................................................................... 141
Introduction to TILOS ............................................................................................ 142
Uses, Pros, and Cons of TILOS.............................................................................. 143
Key TILOS Principles and Concepts .................................................................... 144
TILOS Terminologies .............................................................................................. 145
Getting started with TILOS ................................................................................... 146
Career in TILOS ..................................................................................................... 147
The Project Management Institute (PMI) ........................................................... 149
Project Management Body of Knowledge (PMBOK) ....................................... 150
PMP Certification ................................................................................................. 151
CAPM Certification .............................................................................................. 152
P3O Certification .................................................................................................. 153

Page 5 of 153
 Introduction to Project Management

According to the Project Management Institute (PMI), a project is a "temporary

endeavour undertaken to create a unique product, service, or result."
For people who want to put their ideas into action, a project is a clearly
defined, interesting, and helpful instrument. It is a short-term effort with a clear
objective, typically including a number of tasks and resources that must be
coordinated to produce the required results. Projects differ from routine work,
such as marketing, sales etc. These routine jobs are continuous and they don't
have a clear start and end date.
Project management is the process of arranging, planning, and controlling
tasks and resources to execute a certain work or project. Simply put, it's like
overseeing a project as the "boss," ensuring sure everything goes according to
plan and is completed on schedule.
Assume trying to construct a treehouse. To manage the project, it would be
necessary to divide the large task of building the treehouse into smaller, more
manageable activities, such as obtaining supplies, designing the treehouse,
and constructing various components of it. Additionally, you'd need to
estimate the project's time and cost requirements, as well as make sure you
have the appropriate personnel or equipment on hand to assist you.
You would be in charge of monitoring the development, ensuring that
everyone is aware of their responsibilities, and resolving any issues that arise.
Make sure the treehouse is constructed effectively and according to schedule
and budget.
Project management in a professional setting might include everything from
developing a new product to planning an event. The key is to establish a well-
defined plan, maintain organisation, and lead the team toward project
success.
Project management is important in business settings. Organizations and
companies undertake projects to fulfil their strategic ambitions and aims,
which cannot be satisfied solely through routine operations. Projects are a sort
of investment that need time, money, and organisational resources to provide
the desired results, such as more income, more effective procedures, satisfied
customers, or non-profit objectives. Based on their prospective advantages
and compatibility with the company's business plan, projects are carefully
chosen. Resources are used up as the project moves forward, but the
advantages that result should outweigh the expenses in the long run and
continue to benefit the business. That’s why companies need project
managers, so that their investment are efficiently handled, and the project is
timely completed and that too in the budget.
Some common characteristics of projects include:

Page 6 of 153
  Unique: Every project is unique and distinctive from the others, Even if
they all have similar objectives.
 Temporary: Projects have a defined beginning and ending date, unlike
the routine operations or tasks.
 Goal-oriented: Projects have a clear objective or outcome that is to be
achieved.
 Resource constraints: Projects frequently have a limited amount of time,
money, or personnel, all of which must be handled well.
 Project scope: A project's output, sometimes referred to as the project
scope, can be a finished product, a service, or a result. Even if the final
output are similar, each project's scope is distinct. The distinctiveness is
found in elements like location or resources, which might alter how the
project is carried out.
 Triple constraint: There are three key attributes of projects (aka the "triple
constraint) - time, scope, and cost. These characteristics are
interrelated, so if one changes, it can have an impact on the others. For
example, if a project's completion date is advanced, it can need the
addition of more resources or a modification to the project's output.

In summary, a project is a planned endeavour to produce something new or

attain a particular outcome, typically within a predetermined timetable and
budget. Its distinct scope, specified timeline, and resource limitations set it
apart from routine business operations.

Page 7 of 153
 The Project Phases

The projects have 5 phases:

I. Project Initiation
II. Project Planning
III. Project Execution
IV. Project Monitoring & Control
V. Project Closure

I. Phase I - Project Initiation: The project initiation phase includes

establishing the project's goals and objectives, completing a feasibility
study, and developing a business case for the project. This phase also
includes developing a project charter, doing risk analysis, and identifying
stakeholder. During this phase, the project sponsor defines the objective,
budget, and timeframe, and selects the project manager.
II. Phase II - Project Planning: During this phase, a thorough plan is made,
which also defines the project's scope. As part of this, a project
timetable, budget, and roles and duties are all created. To ensure that
all stakeholders are kept informed throughout the project, a
communication plan is also prepared. This is the phase where you come
into full action as a project manager. You set the work and organize the
project team, define resources and risks, and create a project
management plan.
III. Phase III - Project execution: It includes assigning resources, creating the
project's product or method, and monitoring its development. To make
sure the project is accomplishing its aims and objectives, key
performance indicators (KPIs) are also established. During this phase,
forecasting is crucial to ensuring that the project maintains on track as
well as quality. In nutshell, this is the phase where the project team
creates the deliverables.
IV. Phase IV - Project Monitoring and Control: During this phase, effort and
costs are tracked, progress is observed, and the project's viability is
ensured. Preventing any potential disturbances that might occur is
another aspect of this phase. This phase actually runs in parallel with the
execution phase to track progress and ensure adherence to the plan. It
is a continuous process throughout the phase III (execution phase).
V. Phase V - Project Closing: During this phase, deliverables are handed
over, they are reviewed, the project's outcomes are approved, and any
lessons learned are recorded. This is the phase where you as the project

Page 8 of 153
manager, complete final tasks, hand over the project, and conduct a
meeting with the stakeholders to discuss the lessons learned.

Page 9 of 153
 Project Management Office (PMO)

A department or group inside an organisation known as the Project

Management Office (PMO) is in charge of creating and upholding the
organization's project management standards. The PMO may be in charge of
a number of tasks, such as:
 Creating and maintaining policies, processes, and guidelines for project
management.
 Supplying tools and training to project teams and management.
 Helping project managers and other stakeholders collaborate and
communicate.
 Monitoring project progress, recognising problems, and offering
direction and help as necessary. Supporting and supervising projects.
 Preserving a central location for all project records, including plans,
budgets, and status reports.
The PMO is crucial in assisting firms in successfully managing their projects and
achieving their strategic goals. The PMO assists in ensuring that projects are
completed successfully and efficiently by establishing and maintaining
standards for project management, offering training and tools, encouraging
communication and collaboration, and providing oversight and support.
Depending on the size and requirements of the company, a Project
Management Office's (PMO) organisational structure can change. Here is an
example of a potential PMO organogram:
 PMO Director: The PMO Director is in charge of the PMO's general
administration and strategic planning. They might answer to the CEO or
another senior executive directly.
 PMO Manager: The PMO Manager is in charge of running the PMO on a
daily basis. This includes managing the PMO team's activities and liaising
with other departments and stakeholders.
 Project Managers: Within an organisation, project managers are in
charge of overseeing certain projects. They could answer to the PMO
Director or the PMO Manager.
 Project Coordinators: Project managers receive assistance from project
coordinators with the planning, coordinating, and execution of projects.
They could also be in charge of collaborating with the project team and
keeping track of the project's documentation.
 Other Support Staff: Administrative assistants, project analysts, and other
support personnel who help with PMO day-to-day operations may be
considered PMO Support Staff.
This is just one example of a possible organogram for a PMO. The specific
structure of a PMO may vary depending on the needs and goals of the
organization.

Page 10 of 153
 Introduction to the Project Initiation Phase

The project management process begins with the project initiation phase. It
consists of the steps necessary to define the project's aims and objectives,
carry out a feasibility study, and create a business case for the initiative. A
project charter, risk analysis, and stakeholder identification are all included in
this phase.
Clarifying the project's scope and establishing specific goals and objectives
are crucial at the project phase. This will make it easier to make sure the project
stays on course and is finished in the allotted amount of time. Additionally, a
business case is developed to support the project, which includes a financial
study to ascertain the project's viability. To determine the project's economic
and technological viability, a feasibility study is also carried out.
The scope, goals, and stakeholders of the project are described in the project
charter. It is used to get key stakeholders' support and commitment and acts
as a resource all during the project.
Additionally crucial to the project initiation phase is risk assessment. It includes
determining potential risks and creating plans to reduce or control those risks.
Overall, laying the groundwork for a successful project depends on the project
initiation phase. It assists in making sure the project is well defined,
manageable, and has the backing of important stakeholders.

Page 11 of 153
 Elements of the Project Initiation Phase

The project initiation phase often includes a number of important components.

These consist of:
 Business case: A business case is a document that lists a project's
advantages, disadvantages, and risks. The project's justification is used
to win over key stakeholders and secure their support and commitment.
 Feasibility study: A feasibility study examines a project's technical and
financial viability. It assists in deciding whether the project is worthwhile
and highlights any potential risks or challenges.
 Goals and objectives: The project's goals and objectives must be spelled
out in detail during the project's initiation phase. This will make it easier
to make sure the project stays on course and is finished in the allotted
amount of time.
 Stakeholders: Identifying the project's stakeholders is a crucial step in the
project initiation phase. Anyone who will be linked with the project or
who has a stake in its success is considered a stakeholder.
 Project charter: Project charter is a document that includes the scope,
goals, and stakeholders of the project. It is used to get key stakeholders'
support and commitment and acts as a resource all during the project.
 Risk assessment: Assessing risks includes finding potential risks and
creating plans to control or lessen them. To ensure the project's success,
it is a crucial component of the project initiation phase.

Page 12 of 153
 Defining Project Goals

The first step of a project, known as the initiation phase, begins with an idea or
an organisational requirement. The project sponsor selects the project
manager and decides if a project may be carried out. A project has a clear
objective, and though that objective naturally is complex, it aligns with the
organization's strategy, and is beneficial to the organization. To ensure the
project's success, defining project goals during the project's initiation phase is
a crucial step.
The following advice will help you specify project goals:
 Set SMART goals: Make sure the objectives are specific, measurable,
achievable, relevant, and time-bound (SMART). This will ensure that the
objectives are specific and achivable.

 Include important stakeholders: Include important stakeholders in the

goal-setting process. This will make it easier to make sure that the
objectives meet the requirements and expectations of all stakeholders
involved.
 Establish the objective and scope: Establish the objective and scope of
the project. The project's objective is its final goal, while the scope
describes what will be covered by the project and what won't.
 Set both immediate and long-term objectives: Long-term goals will serve
to steer the general course of the project, while short-term goals will help
to keep the project on track and give a sense of accomplishment.
 Keep objectives practical: Make sure the objectives are practical.
Setting hard yet attainable goals is crucial.
 Specify the objectives in the project charter: The project's aims and
objectives should be clearly stated in the project charter. This will make
it easier to make sure that everyone is on the same page and pursuing
the same goals.

Page 13 of 153
 Creating a Business Case

A business case is a document that lists a project's advantages,

disadvantages, and risks. It is used to win over key stakeholders and secure
their support and commitment.
The business case is used to convince the board of directors to allocate
company resources to a particular project, so, you can see that it is an essential
step in project portfolio management. The project can officially begin once
the business case has been accepted. That’s why, the project's purpose for
the company, costs, and possible returns, as well as all financial analysis and
elements, must be explained in the business case.
You need to keep in mind the project’s scope while working on the business
case. Project scope simply means what the project includes and what it
doesn’t. During the planning stage, the project sponsor needs to have a clear
idea of what is involved in the project scope. This is why the project team,
including experts from different departments, works with the project manager
and sponsor to define the scope. The sponsor works with the team to find
answers to any queries or grey areas.
The following processes can be used to develop a business case at the project
initiation phase:
 Explain the issue or opportunity: Establishing a clear definition of the issue
or opportunity that the project is meant to address is the first stage in
developing a business case. In order to make sure that the business case
is pertinent and in line with their needs and expectations, this should be
done in partnership with key stakeholders.
 Determine the goals: The project's goals should then be determined.
These should be SMART goals.
 Create alternate remedies: It is crucial to take into account a variety of
potential solutions to the issue or opportunity. This will make it more likely
that the best option will be chosen.
 Analyze the alternatives: The possible advantages, disadvantages, and
risks of any alternative solution should be considered. This will make it
easier to choose the best option.
 Pick your desired course of action: The preferred option should be
chosen after evaluating the alternatives.
 Establish a financial analysis: It is necessary to do a financial analysis to
ascertain the advantages and disadvantages of the chosen option. This
will strengthen the project's justification and win over important
stakeholders.
 Prepare business case document: The project's goals, the alternatives
that were taken into consideration, the preferred solution, and the
financial analysis should all be summarised in the business case
document.

Page 14 of 153
  Inform the stakeholders: Stakeholders should be informed about the
business case in order to get their support and commitment for the
project.
Business Case Document Checklist:
To begin a business case, a business case checklist is necessary, and the
following elements may be included, based on the requirement of the project:
1. Executive Summary
2. Project Definition
3. Vision/Goals/Objectives
4. Project Scope
5. Background Information
6. Success Criteria and Stakeholder Requirements
7. Project Plan
8. Project Budget
9. Project Schedule
10. Project Governance
11. Communication Plan
12. Progress Reports
13. Financial Appraisal
14. Market Assessment
15. Competitor Analysis
16. SWOT (strengths, weaknesses, opportunities, and threats) Analysis
17. Marketing Strategy
18. Risk Assessment
Here is a sample template of project case document. It is important to
customize the elements relevant to the project stakeholders.

Business Case Document Template

Project Name: Write project's name.

Project Manager: Write project manager's name.
Client: Write client's name.
Duration: Write the duration of entire project.

Executive Summary: Provide a brief overview of all the sections in the

business case document.
Project Definition: Provide general information about the project,
such as business objectives and project plan
outline.

Page 15 of 153
Vision/Goals/Objectives: Define the project vision, goals, and objectives
to shape the project scope and identify
deliverables.
Project Scope: Determine all tasks and deliverables to execute
in the project to reach business objectives.

Background Information: Provide a context for the project and explain

how it aligns with the organization's vision and
strategic plan.
Success Criteria and Provide quality requirements critical to the
Stakeholder project's success and determine what
Requirements: determines success.
Project Plan: Create a plan of tasks to complete the project,
estimate task duration, and organize them into
a work breakdown structure.
Project Budget: Estimate project costs to complete the project
within the allotted time.
Project Schedule: Create a timeline for the project by estimating
how long it will take to complete each task.
Project Governance: Define project management rules, procedures,
and decision-making frameworks.
Communication Plan: Establish a plan for communication with
stakeholders to stay aware of progress.
Progress Reports: Provide how to monitor and track project
progress and performance, comparing planned
vs. actual progress.
Financial Appraisal: Explain how financial benefits outweigh costs
and compare financial costs and benefits.
Market Assessment: Research about the market, competitors, and
industry to identify opportunities and threats.
Competitor Analysis: Identify competitors and assess their products,
strengths, competitive advantages, and
business strategies.
SWOT Analysis: Identify strengths, weaknesses, opportunities,
and threats of the organization.
Marketing Strategy: Describe product, distribution channels, pricing,
target customers, and other aspects of the
marketing plan.
Risk Assessment: Identify and assess risks associated with project
activities.

Page 16 of 153
 Signature
Date

Page 17 of 153
 Doing Project Feasibility Study

A feasibility study examines a project's technical and financial viability. It assists

in deciding whether the project is worthwhile and highlights any potential risks
or challenges.
With a mid- to high-level analysis to confirm budget, time, and expertise
availability, as well as the procurement of partner companies, a feasibility
study analyses the objectives, scope, and resources to ascertain whether a
project's success is viable. Prior to beginning the project, it is crucial to do a risk
analysis and an expectation management process. Don’t worry! Its not you
who have to do it alone. But yes! It’s you who have to make sure that it is done.
It's the project sponsors who work with the project manager, the project team
and other stakeholders to undertake the feasibility study of a project.
To do a feasibility study during the project initiation phase, follow these steps:
 Set the project's parameters: Establishing a firm understanding of the
project's scope is the first stage in performing a feasibility study. This
includes describing the project's aims and objectives as well as the
deliverables that will be created.
 Identify the limitations and presumptions: It's critical to identify any
limitations or presumptions that could affect the project's viability. These
can be resource limitations, legal requirements, or technological
restrictions.
 Examine the technical viability: The technical viability of the project
should be evaluated to ascertain whether the necessary technology is
accessible and suitable for the project's requirements.
 Analyze the project's economic viability: To ascertain whether the
project is financially feasible, the project's economic viability should be
evaluated. Analyzing the project's expenses and prospective rewards is
part of this process.
 Analyze the operational feasibility: The project's operational viability
should be evaluated to see if it can be successfully incorporated into the
organization's operations.
 Create the report for the feasibility study: The analysis's results should be
condensed in the feasibility study report, together with suggestions for
how to proceed with the project.
 Discuss the feasibility study with the relevant parties: To get their
feedback and support for the project, important stakeholders should
examine the feasibility study.
Overall, the project initiation phase's feasibility assessment is a crucial stage. It
serves as a starting point for the project planning process and helps in
determining whether the project is technically, commercially, and
operationally viable.

Page 18 of 153
 Project Feasibility Study Template

I. Project Overview
Project Name:
Project Manager:
Client:
Description of the project and its
objectives:
Expected outcomes and benefits:
Target audience or beneficiaries:

II. Technical Feasibility

Technical requirements and
specifications:
Availability of technology and equipment:
Capacity and capability of the technical
team:
Compatibility with existing systems or
infrastructure:

III. Operational Feasibility

Analysis of operational requirements:
Availability of resources such as human,
financial, and material:
Potential impact on existing operations:
Potential disruptions and mitigating
measures:

IV. Economic Feasibility

Cost-benefit analysis of the project:
Calculation of expected return on
investment:
Analysis of potential risks and
uncertainties:
Assessment of the project's financial
viability:

V. Legal and Regulatory Feasibility

Compliance with local and national
regulations and laws:
Analysis of potential legal issues and
challenges:

Page 19 of 153
Identification of necessary permits and
licenses:
Assessment of any legal or regulatory
barriers:

VI. Environmental Feasibility

Assessment of potential environmental
impacts:
Identification of potential environmental
risks and challenges:
Analysis of necessary permits and
approvals:
Assessment of any environmental barriers:

VII. Schedule Feasibility

Determination of project timeline and
milestones:
Analysis of project schedule risks and
challenges:
Identification of necessary resources to
meet project schedule:
Assessment of any schedule barriers:

VIII. Conclusion
Summary of the project feasibility analysis:
Recommendation for project
implementation or not:
Key success factors and potential
challenges:
Next steps for project implementation or
further analysis:

Signature
Date

Page 20 of 153
 Doing Risk Assessment

The process of identifying potential risks and creating mitigation or

management measures for such risks is known as risk assessment. To ensure the
project's success, it is a crucial component of the project initiation phase.
Since uncertainty might affect a project's success, risks need to be recognised,
examined, and addressed prior to the project's commencement. To prevent
possible problems and tragic outcomes, it's crucial to address everyone's
expectations and make sure that everyone shares the same vision, resources,
and accountability. Spending time with stakeholders will allow the project
manager to spot any gaps in expectations and address them as soon as
possible.
In order to conduct a risk assessment at the project initiation phase, follow
these steps:
 Determine the risks: Finding the potential risks that might have an
influence on the project is the first stage in doing a risk assessment. This
can be accomplished by holding brainstorming meetings with the
project team, looking through previous projects, or using a tool for risk
assessment.
 Consider the risks: The possibility and impact of the risks should be
evaluated after they have been recognised. Prioritizing the risks and
concentrating on the biggest ones will be made easier by doing this.
 Create risk mitigation plans: Following analysis and identification of the
risks, strategies for managing or mitigating them should be created. This
could include putting in place risk controls, assigning the risk to another
person, or simply accepting it.
 Risk Assessment: Risks should be assessed and reviewed frequently
throughout the project to make sure they are being appropriately
handled.
 Update the risk registration: Throughout the project, the risk register
should be updated to reflect any changes to the risks, as well as their
likelihood and impact.
In general, risk assessment is a continuous process that helps in making sure
that possible risks are recognised and properly managed. The likelihood of
the project succeeding will rise as a result.

Page 21 of 153
 Creating Project Charter

The project owner typically creates the project charter, which is a high-level
document that includes important details about the project, such as the
project ID, name, organisation, aim, objectives, timeframe, scope,
stakeholders, risks, and budget. Anybody should be able to understand the
charter because it shouldn't be overly complicated. The project manager may
be chosen at any moment throughout the initiation phase, which is all about
evaluation and approval. The project's general vision and direction are
established by the studies conducted during this phase. It is used to get key
stakeholders' support and commitment and acts as a resource all during the
project.
In order to create a project charter, follow these steps:
 Set the project's scope: The project's scope should be well detailed. The
few things that should always be there are:
o What is in scope?
o What is out of scope?
o What is the timeframe?
o What are the deliverables?
o What are the key risks?
o What are the key issues?
o What are the key assumptions?
o What are the key constraints?
o What is the budget?
 Determine the parties involved: A list of the project's stakeholders, both
those who will be directly touched by it and those with a stake in its
success, should be included in the project charter.
 Outline the roles and responsibilities: Outline the roles and responsibilities
of the project team, including the project manager and any other
important stakeholders, in the project charter.
 Draft a project plan: Draft a project plan, indicating which activities will
be part of which phase.
 List the milestones: List the milestones and when you expect to achieve
them.
 Draft a financial plan: Draft a financial plan, indicating which activities
will consume how much financial resource. A rough estimate of the
project budget, including any funding sources and cost projections,
should be included in the project charter.
 Attach supporting documents: In the appendices, include all the
relevant supporting documents.
 Review and approval of the project charter: Prior to the start of the
project, the project charter needs to be examined and authorised by all
significant stakeholders.

Page 22 of 153
In general, the project charter is a crucial document that ensures the project
is clearly defined, gets the backing of important stakeholders, and continues
on course.

Project Charter Template

I. Project Overview
Project Name:
Project ID Number:
Client:
Project Sponsor:
Project Manager:
Description of the project and its
objectives:
Target Start Date:
Target End Date:

II. Executive Summary

III. Project Scope

In Scope:
Out of Scope:
List of Deliverables and Descriptions:
Key Risks:
Key Issues:
Key Assumptions:
Key Constraints:
Budget:

IV. Stakeholders
Stakeholder Interest
Stakeholder 1:
Stakeholder 2:
Stakeholder 3:
Stakeholder 4:
Stakeholder 5:

Page 23 of 153
 V. Roles & Responsibilities
Role Responsibilities
Role 1:
Role 2:
Role 3:
Role 4:
Role 5:

VI. Project Plan

Phase Task

VII. Milestones
Milestone Date

VIII. Financial Plan

Item/ Activity Cost

IX. Appendices
Appendix Document
Appendix 1:
Appendix 2:
Appendix 3:
Appendix 4:
Appendix 5:

Page 24 of 153
 Signature
Date

Page 25 of 153
 Listing the Stakeholders

A crucial step in the project initiation phase is identifying the project's

stakeholders. Anyone who will be touched by the project or who has a stake
in its success is considered a stakeholder. The following processes can be used
to create a list of the project's stakeholders:
 The internal stakeholders should be identified: The project team and the
project sponsor are examples of internal stakeholders because they are
actively engaged in the project. To make sure their wants and
expectations are taken into account, it is important to identify them early
on in the process.
 Determine the outside parties involved: External stakeholders are people
who may be touched by the project but are not directly participating in
it. Customers, suppliers, regulators, or the community may be included
in this.
 Identify the influence and interests of the stakeholder: In order to
understand how each stakeholder could affect the project, it is crucial
to ascertain their interests and spheres of influence.
 List the participants: The project charter or a stakeholder registration
should contain information about the stakeholders. This will make it easier
to ensure that all project stakeholders are kept updated and
participating.
In general, determining the project's stakeholders is a crucial stage in the
project commencement phase. It helps to make sure that the project receives
the support it needs to be successful as well as that the needs and
expectations of all stakeholders are taken into account.

Page 26 of 153
 Introduction to the Project Planning Phase

The second stage of the project management process is project planning. It is

detailed procedure that involves creating a thorough plan for how the project
will be finished. The project's scope, a project plan and timetable, a budget,
the assignment of roles and duties, and a communication plan are all part of
this phase.
It involves analyzing, evaluating, deciding and organizing activities in
advance. Planning involves defining the goal, evaluating options, and
choosing and confirming the best option to achieve the goal.
Clarifying the project's scope and creating a thorough strategy for how the
work will be carried out are crucial during the project planning phase. This
includes determining the tasks that must be finished, calculating the amount
of time and resources needed for each activity, and developing a schedule.
Along with defining the project team's roles and duties, the budget should be
established. To make sure that all stakeholders are kept updated throughout
the project, a communication plan should also be created.
In general, the project planning stage is essential to its success. It helps in
ensuring that the task can be accomplished effectively and efficiently and
that the project is clearly defined.

Page 27 of 153
 Elements of the Project Planning Phase

The project planning phase often includes a few important components. These
consist of:
1. Project timetable and plan: The tasks that must be done and the time
frames for doing so are outlined in the project plan and schedule. It
provides information on the necessary resources, task dependencies,
and any possible risks.
2. Budget: The project's budget needs to be determined during the
planning stage. Estimates for the price of labour, materials, and any
additional costs are included.
3. Responsibilities and roles: The planning stage should include a definition
of the project team's roles and duties. This covers both the duties of the
project manager and those of the other team members.
4. Plan of communication: To make sure that all stakeholders are kept
updated on the project's progress, a communication strategy should be
created. The methods of communication, the timing of
communications, and the individuals in charge of corresponding with
each stakeholder must all be specified.
5. Risk management strategy: To identify possible risks and create
mitigation or management methods, a risk management strategy
should be devised.
Overall, these components are essential to the project's success. They assist in
making sure the project is well defined, has a well-defined plan and timeframe,
and has the materials and assistance required to be finished effectively.

Page 28 of 153
 Defining Project Scope

The project planning phase includes a crucial stage called defining project
scope. It helps in ensuring that the task can be accomplished effectively and
efficiently and that the project is clearly defined. The following steps can be
used to specify a project's scope during the planning stage:
 Determine the aims and objectives of the project: Finding the project's
goals and objectives is the first step in establishing the scope of the
project. This will make it easier to make sure that the scope fits with the
project's ultimate goal.
 Specify the outputs: The exact goods or services that will be created as
a result of the project are known as the deliverables. To ensure that the
project team is aware of what has to be done, these should be precisely
outlined in the scope statement.
 Prioritize project requirements: A method for ranking project
requirements according to importance is called MoSCoW prioritising.
The most crucial needs can be incorporated in the project scope and
any non-essential requirements can be excluded by using MoSCoW
prioritising. This keeps the project on schedule and focused and ensures
that the most crucial objectives are met. Here's how to use it in project
scope:
o Listing potential requirements: Start by listing all of the potential
requirements for your project scope.
o Categorize: Categorize each requirement into one of four
categories: Must have, Should have, Could have, and Won't
have.
 Must have: These are requirements that are essential to the
success of the project. If they are not included, the project
cannot proceed.
 Should have: These are requirements that are important but
not critical. They can be left out if necessary, but it would be
preferable to include them if possible.
 Could have: These are requirements that would be nice to
have but are not necessary. They can be included if time
and resources permit.
 Won't have: These are requirements that will not be included
in the project scope, either because they are not relevant
or because there is not enough time or resources to include
them.
 Determine the limitations and exclusions: It is crucial to specify any
exclusions or restrictions that will not fall inside the project's scope. This
will make it possible for the project team to concentrate on the work that
needs to be done because they will know exactly what is outside of
scope.

Page 29 of 153
  Review the scope with the relevant parties: In order to make sure that
the project's scope matches the needs and expectations of the main
stakeholders, it should be evaluated with them.
 Document the scope: The project's scope statement should contain a
description of the project's scope. This will act as a point of reference for
the duration of the project and help to keep it on course.
In general, determining a project's scope is a crucial step in the project
planning stage. It helps in ensuring that the task can be accomplished
effectively and efficiently and that the project is clearly defined.

Project Scope Template

I. Project Overview
Project Name:
Project ID Number:
Client:
Project Sponsor:
Project Manager:
Description of the project and its
objectives:
Target Start Date:
Target End Date:

II. Executive Summary

III. MoSCoW prioritization

Must Have: Requirements essential to the
success of the project. If they
are not included, the project
cannot proceed.
Should Have: Requirements that are
important but not critical. They
can be left out if necessary,
but it would be preferable to
include them if possible.

Page 30 of 153
Could Have: Requirements that would be
nice to have but are not
necessary. They can be
included if time and resources
permit.
Won't Have: Requirements that will not be
included in the project scope,
either because they are not
relevant or because there is
not enough time or resources
to include them.

IV. Description of Scope

In Scope:
Out of Scope:

V. Objectives

VI. Deliverables

VII. Constrains

VIII. Assumptions

IX. Budget Estimation

Page 31 of 153
 X. Stakeholders

XI. Appendices
Appendix Document
Appendix 1:
Appendix 2:
Appendix 3:
Appendix 4:
Appendix 5:

Signature
Date

Page 32 of 153
 Project Plan and Schedule

An essential step in the project planning phase is the creation of a project plan
and timetable. It helps in ensuring that the task can be accomplished
effectively and efficiently and that the project is clearly defined. Here are
some procedures for developing a project schedule and plan during the
planning stage:
 Identify the tasks: Finding the tasks that must be accomplished as part
of the project is the first step in developing a strategy and timeline for it.
To ensure that all required work is included, this should be done in
coordination with the project team and key stakeholders.
 Calculate the necessary time and resources: The time and resources
needed to execute each task should be estimated. This will support
establishing the project's overall schedule and budget.
 Identify the dependencies: Some tasks might be dependent on other
tasks getting done first. The project plan and schedule should be
updated to reflect these dependencies.
 Create the project schedule: Create the project schedule, which should
include any important milestones as well as the deadline for finishing the
activities. Each task's start and finish dates as well as the materials
needed to do it should be listed.
 Assess the project plan and schedule: The project team and important
stakeholders should review the plan and schedule to make sure it is
feasible and attainable.
 Use project management tools or software: Project management tools
or software, such as Microsoft Project, should be used to record the
project plan and schedule. This will make it easier to keep the project on
schedule and to track and inform all stakeholders of its progress.
 Update the project plan and schedule: As the project moves forward, it
might be important to reflect any modifications or revisions in the plan
and schedule. This can include adding additional duties, modifying the
schedule or spending plan, or reallocating resources. To make sure that
the project stays on course and that all stakeholders are kept up to date
on any changes, it is crucial to routinely review and update the project
plan and schedule.
Overall, the phase of project planning requires the development of a project
plan and timetable. It helps in ensuring that the task can be accomplished
effectively and efficiently and that the project is clearly defined. The project
team can stay on track and ensure the project's success by routinely reviewing
and revising the project plan and timeline.

Project Plan Template

Page 33 of 153
 I. Project Overview
Project Name:
Project ID Number:
Client:
Project Sponsor:
Project Manager:
Description of the
project and its
objectives:
Target Start Date:
Target End Date:

II. Executive Summary

III. Description of Scope

In Scope:
Out of Scope:

IV. Milestones
Milestone Description Date of
Delivery

V. Phase I (Project Initiation)

Activity Task Sequence Effort (in Resource
days/
weeks)

VI. Phase II (Project Planning)

Page 34 of 153
Activity Task Sequence Effort (in Resource
days/
weeks)

VII. Phase III (Project Execution)

Activity Task Sequence Effort (in Resource
days/
weeks)

VIII. Phase IV (Project Monetoring and Control)

Activity Task Sequence Effort (in Resource
days/
weeks)

IX. Phase V (Project Closure)

Activity Task Sequence Effort (in Resource
days/
weeks)

X. Project Schedule

XI. Dependencies

Page 35 of 153
Task/ Activity Depends on Type of
Dependency

XII. Constrains

XIII. Assumptions

XIV. Project Budget

XV. Risk Log

Risk Impact Response Risk Level Risk Owner

XVI. Change Management

Change Impact Approval Start Date End Date
Status

XVII. Appendices

Page 36 of 153
 Appendix Document
Appendix 1:
Appendix 2:
Appendix 3:
Appendix 4:
Appendix 5:

Signature
Date

Page 37 of 153
 Gantt Chart

The tasks and timetable of a project are visually represented using a Gantt
chart, a common project management tool. It shows a timeline of the project's
activities, together with the start and end dates for each one. The chart is
made up of horizontal bars that represent the length of each task, with arrows
indicating dependencies between them.
Henry Gantt created Gantt charts in the early 1900s, and ever since then,
project managers have relied on them as a vital tool for managing and
tracking complex projects.

Gantt charts have the following essential attributes:

 Timeline: The Gantt chart shows a project's timetable, usually in days,
weeks, or months.
 Tasks: Project tasks are represented on the chart by horizontal bars, with
the length of the bar indicating the task's duration. The bars are
arranged according to their start date.
 Dependencies: You may use arrows to connect jobs on the Gantt chart
to show where there are dependencies between them. This displays
which activities must be finished before starting others.
 Milestones: On the Gantt chart, milestones are frequently represented
by diamonds or other symbols. Milestones are important events or
project deliverables.
 Resources: Gantt charts can also be used to monitor how people, tools,
and supplies are distributed across the project's many tasks.

Page 38 of 153
  Progress: The Gantt chart can be modified to reflect the actual start and
end dates of tasks as the project advances. This enables the project
manager to monitor development in relation to the original timeline and
make necessary adjustments.
Software tools like Microsoft Project, Excel, or specialised project management
software can be used to construct Gantt charts. They are an effective resource
for project managers because they let them plan, monitor, and share project
schedules with stakeholders.

Page 39 of 153
 Creating Communication Plan

A project's planning phase should include a communication plan. It helps in

ensuring that any possible concerns are promptly handled and that all
stakeholders are kept updated throughout the project. The following
procedures can be used to create a communication plan during the project
planning stage:
 Identify the stakeholders: Identifying all of the project's stakeholders is
the first stage in developing a communication plan. This covers all
internal and external stakeholders who will be influenced by the project,
as well as the project team and sponsor.
 Determine each stakeholder's communication requirements: Each
stakeholder's communication requirements should be identified and
taken into account while creating the communication plan. For
example, although the project team may require more frequent
communication to coordinate their work, the project sponsor may
require regular updates on the project's progress.
 Define the channels of communication: The communication plan should
specify the channels that will be used to communicate with each
stakeholder. Email, meeting, phone calls, and project management
tools may all fall under this category.
 Create a communication plan: The frequency and time of
communication with each stakeholder should be specified in the
communication schedule. Regular updates or more frequent contact,
as necessary, could be part of this.
 Create a communication plan document: The project charter or another
document should contain a description of the communication strategy.
This will act as a point of reference for all parties involved and help to
ensure effective and consistent communication throughout the project.
In general, a communication plans is crucial to the project planning stage. It
helps in making sure that all parties involved are kept informed and that any
possible problems are resolved quickly.

Communication Plan Template

I. Project Overview
Project Name:
Project ID
Number:
Client:
Project Sponsor:
Project Manager:

Page 40 of 153
Description of the
project and its
objectives:
Target Start Date:
Target End Date:

II. Executive Summary

III. Objectives
Objectives of
Communication:
Communication
Guidelines:

IV. Stakeholder Requirements

for Providing
Responsible
Information

Information

Information

Frequency
Source of
Required

Channel
Delivery
Person
Role

Name

V. Communication Events
Description

Frequency
Objective

Members

(Online/
Offline)
Mode

Date
Brief

Event / Meeting

VI. Communication Schedule

Page 41 of 153
 VII. Assumptions

VIII. Risks

IX. Appendices
Appendix Document
Appendix 1:
Appendix 2:
Appendix 3:
Appendix 4:
Appendix 5:

Signature
Date

Page 42 of 153
 Setting a Budget

Budgeting is a crucial element in the project planning process. It helps in

ensuring that the project has the resources required for a successful
completion. In order to establish a budget during the project planning stage,
follow these steps:
 Identify the constraints: The first step in creating a budget is to identify
the constraints that will have an impact on it. The availability of funds,
any applicable regulations, and any other outside circumstances that
can have an impact on the budget are examples of this.
 Calculate the expenses: The cost estimates for each item in the project
plan are the next phase. The price of labour, supplies, and any
additional costs should be included in this. To make sure that the budget
is reasonable and attainable, it is crucial to estimate expenditures as
precisely as possible.
 Create a spending plan: The budget plan should include a breakdown
of the prices for each project assignment as well as the project's overall
budget. It should also include a backup strategy to pay for any
unforeseen costs.
 Stakeholders’ budget review: To make sure the budget is reasonable
and suits the demands of the project, it should be evaluated with
important stakeholders, such as the project sponsor.
 Budget documentation: The project charter or a separate document
should contain a budget description. This will act as a point of reference
for the project team and support maintaining the budget throughout
the project.
Setting a budget is a critical first step in the project planning process. It helps in
ensuring that the project has the resources required for a successful
completion and that the budget is reasonable and doable.

Budget Template

I. Project Overview
Project
Name:
Project ID
Number:
Client:
Project
Sponsor:
Project
Manager:

Page 43 of 153
Project
Descriptio
n&
Objectives
:
Target
Start Date:
Target End
Date:

II. BUDGET
Cost Cost
Constrain / Constrain /
Person Responsible

Item I Item I

Budgeted Cost
Planned Units
Planned Units

Actual Units

Actual Units

Actual Cost

Difference
Cost/ Unit

Cost/ Unit

Remark
Task

TOTAL:

Signature
Date

Page 44 of 153
 Defining Roles and Responsibilities

During the project planning phase, it's crucial to clearly define roles and
responsibilities. It helps to make sure that everyone in the project team is aware
of what is expected of them and that everyone is aware of who is in charge of
what part of the project. The following stages can be used to specify roles and
responsibilities during the project planning stage:
 Choose the project's team: Identifying the project team is the first stage
in establishing roles and responsibilities. All parties who will be
participating in the project, including the project manager, team
members, and any contractors or vendors, should be listed here.
 Determine each team member's roles and responsibilities: Each team
member's roles and responsibilities should be distinctly stated and
recorded. This could contain the particular duties that each team
member has as well as their overall impact on the project.
 Give roles and responsibilities to people: Once each team member's
roles and responsibilities have been established, they should be given to
the right people. Each team member must have the knowledge and
experience necessary to carry out their responsibilities successfully.
 Explain the roles and responsibilities: To make sure that everyone in the
project team is aware of their roles and responsibilities, it is important to
review them together.
 Document the roles and responsibilities: The project charter or a different
document should contain a list of the roles and responsibilities. The
project team will use this as a point of reference, which will help to ensure
that the project is finished quickly and successfully.
Overall, the project planning phase's step of defining roles and responsibilities
is crucial. It helps to make sure that everyone in the project team is aware of
what is expected of them and that everyone is aware of who is in charge of
what part of the project.

Roles and Responsibilities Template

I. Project Overview
Project
Name:
Project ID
Number:
Client:
Project
Sponsor:
Project
Manager:

Page 45 of 153
Description
of the
project
and its
objectives:
Target Start
Date:
Target End
Date:

II. Executive Summary

III. Roles and Responsibilities

Key Performance
Indicators (KPIs)
Responsibilities

Reporting to
Timeline

Remark
Targets
Role

IV. Appendices
Appendix Document

Signature
Date

Page 46 of 153
 Introduction to the Project Execution Phase

The work indicated in the project plan is finished during the project execution
phase. It includes all of the tasks necessary to create the process or product
indicated in the project plan. Allocating project resources, creating the
product or process, monitoring project progress, establishing key performance
indicators (KPIs), ensureing quality, and forecasting are some examples of
what this could entail.
The success of the project depends on how well it is carried out. To ensure that
the project is finished on schedule, within budget, and to the requisite quality
standards, rigorous planning, coordination, and management are necessary.
The project's longest phase, execution, calls for careful coordination between
the project team and important stakeholders to ensure that the task is carried
out properly and efficiently.

Page 47 of 153
 Elements of the Project Execution Phase

Depending on the precise nature and objectives of the project, different

components of the execution phase are used. However, the execution step
usually includes a few standard components as well:
 Allocating project resources: During the execution phase, the project
team and any other resources needed to finish the work should be
determined. This includes determining the precise knowledge and
abilities needed for each work and assuring the availability of the
necessary resources.
 Building the product or process: This is the execution phase's main goal
and includes carrying out the tasks listed in the project plan. This could
involve tasks like creating, developing, testing, and putting the product
or process into use.
 Monitoring the progress: Monitoring the project's progress to make sure
it is on schedule and within budget requires regular monitoring and
tracking of its status. To monitor progress and spot any possible problems,
this may include useing project management software or other tools.
 Choosing key performance indicators (KPIs): KPIs are measurements
that assess the project's success. They ought to be established during the
execution stage and used to monitor development and pinpoint
potential improvement areas.
 Assuring quality: To make sure the project meets the necessary
requirements, the quality should be periodically reviewed and tested.
This can include performing routine quality assurance inspections and
carrying out any required corrective measures.
 Forecasting: To identify any potential problems or risks that could affect
the project's timeline or budget, the project team should frequently
analyse and forecast the project's progress. This will make it easier to
ensure that the project continues on course and that any possible
concerns are dealt with right away.
In general, the project execution phase is when the tasks listed in the project
plan are finished. It takes careful planning, coordination, and management to
ensure that the project is finished on schedule, within budget, and to the
needed quality standards. It involves all of the actions necessary to construct
the product or process indicated in the project plan. Allocating project
resources, creating the product or process, monitoring project status and
progress, setting key performance indicators (KPIs), ensureing quality, and
forecasting are all components of the project execution phase. The project
team may improve the likelihood of project success and make sure the project
produces the anticipated results by managing the execution phase properly.

Page 48 of 153
 Allocating Project Resources

The project execution phase includes a crucial stage called resource

allocation. It includes determining the precise knowledge and abilities needed
for each project activity and making sure the necessary tools are on hand to
finish the assignment. The following procedures can be used to allocate
project resources during the execution phase:
 Determine the necessary resources: Finding the precise resources
needed for each project activity is the first step in allocating project
resources. This could refer to the project crew, tools, supplies, and any
other resources required to finish the job.
 Determine the resources' availability: Once the resources necessary for
each activity have been identified, it is time to assess their availability.
This include assessing the project team's present workload, availability,
and any further resources required.
 Give the resources a home: Based on the resources' availability and the
knowledge and abilities needed to do the work, the resources should be
assigned to the relevant tasks. To increase the likelihood that the project
will succeed, it is crucial to make sure that the resources are allocated
effectively and efficiently.
 Examine the resource distribution: To ensure that the project team has
the resources necessary to do the task on time and within budget, the
resource allocation should be reviewed on a regular basis. Any problems
or restrictions should be noted and dealt with as necessary.
In the grand scheme of things, allocating project resources is a significant
stage in the project execution phase. It raises the likelihood that the project will
be successful by ensuring that the project team has the resources needed to
finish the work on schedule and within budget.

Page 49 of 153
 Developing Products or Process

The project execution phase's main goal is to build the product or process. It is
often the longest phase of the project and includes finishing the tasks included
in the project plan. In the execution phase, the following steps can be taken
to develop the product or process:
 Review the project plan: Reviewing the project plan is the first stage in
creating the product or process to make sure that all required tasks are
understood and that a clear path to completion exists.
 Give the resources a home: During the execution phase, it is important
to identify and assign the resources needed to do the task. This includes
determining the precise knowledge and abilities needed for each work
and assuring the availability of the necessary resources.
 Finish the assignments: The project plan's responsibilities should be
carried out in accordance with the timetable and financial constraints
specified in the plan. To ensure that the task is carried out properly and
efficiently, this may include collaborating closely with the project team,
important stakeholders, and any contractors or vendors.
 Routinely check its progress: To make sure the project is on track and
under budget, it is important to routinely check its progress. To monitor
progress and spot any possible problems, this may include using project
management software or other tools.
 Address any risks or issues that may develop: To make sure they don't
affect the schedule or budget, any risks or difficulties that may arise
during the execution phase should be addressed as soon as possible.
This can include making changes to the project plan or looking for more
resources.
In general, the success of the project depends on developing the product or
process during the execution phase. In order to ensure that the work is finished
on schedule, within budget, and to the specified quality standards, thorough
planning, coordination, and administration are necessary.

Page 50 of 153
 Check Status and Track the Project

Monitoring the project's progress and keeping track of it are crucial parts of the
execution phase. It enables the project team to quickly identify and handle
any potential problems or risks, helping to ensure that the project is completed
on time and within budget. Following are some steps for tracking the project's
execution phase status check:
 Identify tracking strategies: Establishing the techniques to be used to
track the project's development is the first stage. Using project
management software, producing progress reports, or scheduling
frequent status meetings are a few examples of how to do this.
 The key performance indicators (KPIs): The project's key performance
indicators (KPIs) should be identified and established during the
execution phase. Metrics like project cost, schedule, quality, and
customer satisfaction may be among them.
 Measure progress: Using the techniques and KPIs established in the
earlier steps, the project's progress should be monitored on a regular
basis. This could include gathering information, producing reports, and
examining the outcomes to spot any potential problems or dangers.
 Keep stakeholders in loop: Project team members and important
stakeholders should be kept continuously informed of the project's
progress. This could include sharing updates through project
management software, creating progress reports, or giving updates at
status meetings.
 Identify and deal with difficulties or risks: To make sure that they don't
affect the schedule or budget, any issues or risks that are discovered
throughout the tracking process should be dealt with right away. This
can include making changes to the project plan or looking for more
resources.
Overall, monitoring the project's state and progress is a crucial part of the
execution phase. It makes sure the project is moving forward and enables the
project team to quickly identify and handle any potential problems or risks.

Page 51 of 153
 Setting KPIs

The project's success is gauged using measurements called key performance

indicators (KPIs). They are often established during the execution stage and
are used to monitor development and pinpoint potential improvement areas.
The following steps can be used to set KPIs during the execution phase:
 Determine the project's goals: Identifying the project's goals is the first
step in defining KPIs. These goals must be specific, measurable,
achievable, relevant, and time-based (SMART).
 Identify the suitable KPIs: The proper KPIs should be chosen once the
project's goals have been established. These should be used to track
advancement towards the project's goals and should be directly tied to
those goals.
 Establish goals for the KPIs: To offer a benchmark against which progress
can be measured, targets should be defined for each KPI. These
objectives should be in line with the project's overarching goals and be
both difficult and reachable.
 Track and report on the KPIs: The KPIs should be tracked and reported
on a regular basis to make sure that the targets are being reached. This
could include gathering information, creating reports, and assessing the
outcomes to find areas that need improvement.
 Review and modify KPIs: KPIs should be reviewed and modified as
necessary based on the findings of the tracking and reporting process.
To properly reflect the project's progress, this can include changing the
targets or KPIs.
Setting KPIs throughout the execution phase is, in general, a crucial step in
assuring the project's success. The project team may find opportunities for
improvement and take corrective action to keep the project on track to meet
its goals by frequently monitoring and reporting on the KPIs.

Page 52 of 153
 Ensuring Quality

A crucial component of the project execution phase is ensuring quality. It

includes creating and upholding the project's necessary quality standards as
well as making sure the work complies with them. Here are some measures to
take to ensure quality during the execution stage:
 Determine the criteria for quality: Finding the precise quality standards
needed for the project is the first step in assuring quality. Industry
standards, legal requirements, or internally set standards by the
organisation are some examples of these.
 Create a strong plan: To specify the precise measures that will be
followed to ensure that the project achieves the necessary quality
standards, a quality plan should be prepared. This could include
developing quality control procedures, outlining the ways in which
quality will be measured and tracked, and defining the roles and
responsibilities of the project team.
 Put the quality plan into action: To make sure the project complies with
the necessary quality standards, the quality plan should be put into
practice during the execution phase. This might include completing
tests, conducting inspections, and taking appropriate corrective action.
 Monitor and report on project quality: To make sure the project is
adhering to the necessary standards, the project's quality should be
regularly monitored and reported on. This could include gathering
information, producing high-quality reports, and examining the
outcomes to spot any problems or potential development areas.
 Address any quality problems: To make sure the project complies with
the necessary standards, any problems or defects found during the
quality monitoring process should be fixed as soon as possible. This can
include making necessary corrections or modifying the project plan.
Overall, the project execution phase's focus on quality assurance is a crucial
one. The project team can ensure that the project produces the anticipated
results by setting and upholding quality standards, as well as by routinely
monitoring and reporting on quality.

Page 53 of 153
 Forecasting

Forecasting is the practice of making future predictions using facts from the
past and present. It is a crucial component of the project execution phase
since it helps in the identification of potential problems and risks and enables
the project team to take corrective action to keep the project on track. The
following are some forecasting steps for the execution phase:
 Data collection: Data collection is the initial step in the forecasting
process. This could include information on the status of the project, the
budget, available resources, and any other pertinent details.
 Data analysis: Data analysis is necessary to find trends and patterns that
might be predictive of future results. This could include identifying trends
and making predictions using statistical techniques or other tools.
 Create the forecast: The forecast needs to be created using data
analysis. Making projections for the budget, schedule, and other crucial
project variables may be required.
 Review and update the forecast: In order to keep the forecast accurate
and timely, it should be reviewed and updated frequently. This can
include adding new information or modifying existing data in response
to project changes.
 Communicate the forecast: The project team and other stakeholders
should be informed of the forecast so that everyone is aware of the
potential outcomes and can take the necessary steps to keep the
project on track.
Forecasting is a crucial component of the project execution phase overall. It
assists in identifying potential problems and risks and enables the project team
to take remedial action to keep the project on schedule.

Page 54 of 153
 Meetings and Troubleshooting

During the project execution phase, critical tasks like meetings and
troubleshooting are frequently carried out. For meetings and troubleshooting
during the execution phase, keep the following in mind:
 Plan routine meetings: Throughout the execution phase, regular
meetings should be planned to go over the project's status, identify any
risks or concerns, and make any necessary changes to the project plan.
These meetings may consist of team meetings, status meetings, and
meetings with important stakeholders.
 Clarify the agendas: To ensure that meetings are successful and
effective, agendas should be concise and targeted. The agendas
should list the precise subjects that will be covered in detail as well as the
meeting's objectives.
 Take a moment: Meeting minutes should be taken to record significant
decisions, action items, and any other pertinent data. To make sure that
everyone is aware of the meeting's findings, these minutes should be
distributed to the project team and other stakeholders.
 Troubleshoot problems: To make sure they don't affect the timetable or
budget, any problems or risks that surface during the execution phase
should be dealt with as quickly as possible. This can include investigating
the issue, identifying a fix, or modifying the project strategy.
 Record troubleshooting procedure: The troubleshooting procedure
should be recorded so that there is a record of the procedures that were
done to resolve the problem. You can refer to this material in the future
and use it to spot any potential problems.
Meetings and problem-solving are crucial tasks that are frequently carried out
during the project execution phase. The project team may make sure that the
project stays on track and produces the required results by arranging regular
meetings, making clear agendas, taking minutes, and fixing issues as
necessary.

Page 55 of 153
 Introduction to the Project Monitoring and Controlling

Phase

The process of frequently assessing the project's progress and making any
required modifications to keep it on track is known as the project monitoring
and controlling phase. Normally, this phase starts during the execution phase
and lasts until the project is finished. The monitoring and controlling phase's
mission is to make sure the project stays on course and achieves its stated goals
and objectives.
The project team will keep track of the project's advancement throughout this
phase and compare it with the original project plan. The project will be put
back on track if any deviations from the plan are found and corrected. In order
to make sure that resources are being used effectively and efficiently, the
project team will also keep an eye on the budget.
The project team and important stakeholders must actively participate in the
ongoing monitoring and controlling phase. The project team may make sure
that the project stays on track and produces the anticipated results by
periodically monitoring the status of the project and taking corrective action
as necessary.

Page 56 of 153
 Elements of the Project Monitoring and Controlling Phase

The following components make up the project monitoring and controlling

phase:
 Project tracking: To make sure the project is moving forward as intended,
its progress is periodically reviewed and measured against the project
plan. The project is brought back on track by identifying any deviations
from the plan and taking the necessary corrective action.
 Monitoring of the project's budget and resources: To make sure they are
being used effectively and efficiently, a regular evaluation of the
project's budget and resources is conducted. The project is brought
back on track by identifying any problems or deviations from the plan
and taking the necessary corrective action.
 Control of quality: The project's quality is routinely examined to make sure
it adheres to the necessary requirements. Corrective action is
conducted to rectify any problems or defects that are found.
 Risk management: The project team keeps track of the risks connected
to it and takes appropriate action to reduce or eliminate them. This can
include putting risk-reduction plans into action or modifying the project
plan.
 Stakeholder communication: To keep them updated on the project's
progress and any problems or risks that can affect it, the project team
regularly communicates with important stakeholders.
In general, the project monitoring and controlling phase's components are
made to make sure the project stays on course and produces the desired
results. The project team may make sure that the project stays on track and
achieves its set goals and objectives by routinely analysing the project's
progress, keeping an eye on the budget and available resources, and
managing risks.

Page 57 of 153
 Tracking Effort and Cost

An important part of the project monitoring and controlling phase is keeping

track of effort and expenditure. It includes periodically assessing the amount
of time and resources being put into the project and compareing it with the
initial project plan. The following steps can be used to measure effort and
expense during the monitoring and controlling phase:
 Identify a starting point: Setting up a baseline is the first step in tracking
effort and cost. This include defining the project's scope, establishing the
budget and schedule, and figuring out the resources that will be
needed to finish the project.
 Follow developments: To make sure the project is moving along as
planned, its progress should be checked frequently. This can include
keeping track of the time and resources spent on each activity and
comparing it to the original plan.
 Determine deviations: Any variations from the original plan should be
noted and their causes examined. This could include assessing the
project's progress, looking at the finances and available resources, or
figuring out any problems or risks that might affect the project.
 Take corrective action: If deviations from the plan are found, the project
should be brought back on track by taking corrective action. This can
include changing the budget or timeframe, reallocating resources, or
putting risk-reduction measures into place.
 Review and update the project plan: To make sure the project plan is
correct and current, it should be reviewed and updated on a regular
basis. This can include adding new information or modifying existing
data in response to project changes.
The monitoring and controlling phase of the project, in general, places a lot of
importance on tracking effort and cost. The project team may make sure that
the project stays on track and produces the anticipated results by periodically
monitoring the status of the project and taking corrective action as necessary.

Page 58 of 153
 Monitoring Project Progress

An essential component of the project monitoring and controlling phase is

tracking project progress. It includes periodically assessing the project's
advancement and comparing it with the original project plan. The following
actions can be taken to keep track of project progress during the monitoring
and controlling phase:
 Create a baseline: Creating a baseline is the first step in keeping track of
a project's progress. This include defining the project's scope,
establishing the budget and schedule, and figuring out the resources
that will be needed to finish the project.
 Establish key performance indicators (KPIs): Establish key performance
indicators (KPIs) to gauge the project's progress. These could be
measurements of the project's budget, schedule, quality, client
satisfaction, or other pertinent elements.
 Measure progress: Using the established KPIs, the project's progress
should be periodically monitored. This can include gathering information
on the KPIs and comparing it with the original strategy.
 Determine deviations: Any variations from the original plan should be
noted and their causes examined. This could include assessing the
project's progress, looking at the finances and available resources, or
figuring out any problems or dangers that might affect the project.
 Take corrective action: If deviations from the plan are found, the project
should be brought back on track by taking corrective action. This can
include changing the budget or timeframe, reallocating resources, or
putting risk-reduction measures into place.
 Review and update the project plan: To make sure the project plan is
correct and current, it should be reviewed and updated on a regular
basis. This can include adding new information or modifying existing
data in response to project changes.
In general, tracking project progress is crucial to the phase of project
monitoring and controlling. The project team may make sure that the project
stays on track and produces the anticipated results by periodically monitoring
the status of the project and taking corrective action as necessary.

Page 59 of 153
 Ensuring Adherence

An important part of the project monitoring and controlling phase is making

sure the project plan is followed. To make sure the project is on track, it includes
periodically monitoring its progress and comparing it to the initial project plan.
The following actions can be taken to ensure plan adherence throughout the
monitoring and controlling phase:
 Regularly review the project plan: Regular reviews of the project plan
are necessary to make sure it is correct and current. This could include
assessing the project's advancement, looking over the finances and
available resources, and locating any deviations from the original plan.
 Engage in dialogue with the project team: The project team should be
kept up to date on the project's development and any plan
modifications. This will make it easier to make sure that everyone is aware
of the project's goals, objectives, and tasks.
 Follow the project's development: To make sure the project is moving
forward as planned, it should be often followed. This can include
keeping track of the time and resources spent on each activity and
comparing it to the original plan.
 Determine any deviations and deal with them right away: To keep the
project on track, any deviations from the original plan should be found
and dealt with very away. This can include changing the budget or
timeframe, reallocating resources, or putting risk-reduction measures
into place.
 Revise the project plan: Any changes to the project should be included
in the project plan as needed. This can include adding new information
or making modifications in response to project changes.
Overall, a key component of the project monitoring and controlling phase is
assuring adherence to the project plan. The project team may make sure that
the project stays on track and produces the anticipated results by periodically
monitoring the status of the project and taking corrective action as necessary.

Page 60 of 153
 Preventing any Chance for Disruption

The project monitoring and controlling phase includes preventing any

potential disruptions. It includes locating and addressing potential problems or
dangers that might affect the project. Here are some measures to take in order
to avoid any potential disruptions during the monitoring and controlling phase:
 Identify potential risks: Identifying potential risks that might have an
impact on the project is the first step in preventing any likelihood for
disruption. This could include going over the project plan, looking at the
finances and available resources, and analysing any potential problems
or difficulties that might appear.
 Analyze the impact and likelihood of risks: Potential risks should be
evaluated for likelihood and impact on the project when they have
been identified. By doing so, it will be easier to rank the risks and choose
the best course of action.
 Create risk-reduction strategies: To address the identified risks, risk
mitigation methods should be created. This could include allocating
resources differently, modifying the budget or timeframe, or putting
emergency preparations into action.
 Review and monitor risks: To make sure that project-related risks are
being effectively managed, they should be reviewed and kept track of
on a regular basis. When creating risk mitigation measures, any changes
in the possibility or consequences of the risks should be taken into
consideration.
 Stakeholder communication: Stakeholder communication is important.
The project team should inform important stakeholders about the risks
that have been identified and the measures being taken to reduce
them. This will make sure that everyone is aware of the potential
problems and the steps being taken to minimise the possibility of a
disruption.
In general, minimising the possibility of disruption is a crucial component of the
project monitoring and controlling phase. The project team can make sure
that the project stays on track and produces the expected results by
recognising and resolving any risks.

Page 61 of 153
 Introduction to the Project Closing Phase

The project management process ends with the project closing phase. It
includes performing all of the last-minute jobs and activities needed to finish
the project. The closing phase's mission is to confirm that all project goals have
been met, deliverables have been given to the right parties, and the project
team has been disbanded.
The project manager should make sure that all project deliverables have been
finished and reviewed during the closing phase, that the project has been
officially closed out with the stakeholders, and that any outstanding problems
or risks have been resolved. The project manager should also keep track of the
project's ultimate outcomes, as well as any lessons learned, and perform a final
evaluation of the project to determine its overall success.
The project closing phase is a significant stage in the project management
process overall. It ensures that the project has been effectively finished and
that all project goals have been met.

Page 62 of 153
 Elements of the Project Closing Phase

Project closing phase components include the following:

 Complete any outstanding tasks: In order to close the project, the
project team must finish all outstanding tasks. This can include doing any
last-minute tasks, tying up any loose ends, and finishing any outstanding
paperwork.
 Deliverables distribution: The right stakeholders should receive the
project deliverables. This could be tangible items, written materials, or
any other things created as a result of the project.
 Review project deliverables: It is important to check that the project
deliverables adhere to the quality standards and specifications
provided in the project plan.
 Get the project's final results approved: The stakeholders should be
shown the project's results and given their approval. This can include
delivering a final report or presentation that summarises the project's
results.
 Identify and record project learnings: The project team should identify
and record any project-related learnings. This might cover any
recommendations, difficulties, or other learnings from the project.
 Disband the project team: Any resources that were used for the project
should be released together with the project team.
These are the main components of the Project closing phase, in general. The
project manager can ensure that the project has been effectively finished and
that all project objectives have been met by completing these duties.

Page 63 of 153
 Handover of Deliverables

The Project closing phase includes a crucial step called the delivery of project
deliverables. It includes giving the right stakeholders ownership of the project
deliverables and ensuring that they are aware of how to use and maintain
them. Following are some procedures for transferring deliverables at the
closing phase:
 Who are the recipients: Finding the receivers is the initial stage in
distributing the deliverables. Any stakeholders who will get the
deliverables, such as the product's final consumers, the client or
customer, or another group, may be included in this.
 Get the deliverables ready: The products should be ready for transfer.
This can include assembling paperwork, packaging tangible goods, or
carrying out any necessary testing or quality control.
 Share information about the handover: The project team needs to share
information about the handover with the beneficiaries. This can include
sending a reminder email or calling a meeting to go over the
deliverables.
 Transferring ownership: The project team should give the receivers
ownership of the deliverables. This could include handing over any
required paperwork or granting access to any required resources.
 Training or support: To ensure that the receivers are able to use and
maintain the deliverables, the project team should ensure that they
receive any necessary training or support. This can include holding a
training session, offering written materials, or putting in place a support
structure.
In general, transferring the deliverables is a crucial step in the project closing
process. The project team may ensure that the deliverables are used
effectively and that the project objectives are met by creating the
deliverables and offering the required assistance and training to the recipients.

Page 64 of 153
 Reviewing Project Deliverables

An essential stage in the Project closing phase is reviewing the project

deliverables. It includes assessing the outputs' efficacy and quality to make
sure they adhere to the project plan's specifications. The following steps can
be used to review the project deliverables during the closure phase:
 Choose the reviewers: Who are the reviewers? Choosing the reviewers is
the first stage in the deliverables review process. The project team, the
client or customer, or any other stakeholders who will be reviewing the
deliverables could all fall under this category.
 The deliverables should be ready for evaluation: The deliverables must
to be ready for evaluation. Organizing documentation, finishing any
necessary testing or quality assurance, or creating any necessary
presentations or demonstrations could all fall under this category.
 Describe the review: The reviewers should be informed about the review
procedure by the project team. This can include sending a reminder
email or calling a meeting to go over the deliverables.
 Conduct the review: The reviewers should check the deliverables to
make sure they adhere to the project plan's quality criteria and
requirements. This could include carrying out an official evaluation
procedure or giving feedback on the deliverables.
 Describe any problems: The project team should rectify any problems or
discrepancies found throughout the evaluation process. Making any
essential alterations or updates to the deliverables may fall under this
category.
In terms of the Project closing phase, reviewing the project deliverables is a
crucial stage. The project team can ensure that the deliverables are of good
quality and that the project objectives are met by making sure that the
deliverables fulfil the necessary criteria.

Page 65 of 153
 Getting Project Results Approved

An essential step in the Project closing phase is getting approval for the project
results. It includes informing the stakeholders of the project's final results and
obtaining their consent to close the project. The following measures can be
taken to obtain project results approval at the closing phase:
 Determine the parties involved: Finding the stakeholders that must be
involved in the approval process is the first step in getting the project
results authorised. The project team, the client or customer, and any
other important stakeholders may be included in this.
 Get ready to present the findings: Prepare the project results for
presentation to the stakeholders. This can include preparing a final
report or presentation that summarises the project's results.
 Share the presentation: The project team should share the presentation
of the results with the stakeholders. This can include notifying everyone
through email or calling a meeting to go over the findings.
 Results presentation: The project team should inform the stakeholders of
the results. This could be making a presentation, showing the finished
item or method, or offering any required paperwork.
 Obtain approval: The project's stakeholders should study the findings and
give their consent before the project can be closed. This can include
giving your approval in writing or orally.
Overall, approving the project results is a crucial step in the closing phase of
the project. The project team can make sure that the project has been finished
effectively and that the project objectives have been met by presenting the
project's final results to the stakeholders and getting their approval.

Page 66 of 153
 Documenting Project Learnings

The project closure phase includes a crucial step called documenting the
project learnings. In order to improve the entire project management process,
it includes documenting the insights, best practices, and lessons discovered
throughout the project. Following are some procedures for recording project
learnings during the closing phase:
 Find the main lessons learned: Finding the most important insights, best
practices, and lessons learnt throughout the project is the first step in
recording the project learnings. To determine the most important lessons
learned, this can include holding a formal review or debrief with the
project team.
 Summarises the main lessons: The project learnings should be arranged
so that they are simple to grasp and easy to find again. This can include
drafting a report or other paper that summarises the main lessons.
 Share the lessons learned: The project team needs to share the lessons
learned with the appropriate stakeholders. Sharing the report or
document with the stakeholders or presenting the lessons learned in a
meeting could be part of this.
 Keep records: Keep the lessons learned in one place so they are
accessible and can be used as references in the future. The project
learnings should be kept in one central area. This can include keeping
them in a specialised knowledge management system or in a project
management tool.
Overall, a crucial stage in the Project closing phase is documenting the project
learnings. The project team may enhance the overall project management
process and ensure that future projects are more successful by documenting
the main insights and lessons learnt throughout the project.

Page 67 of 153
 Project Leadership

Gaining leadership abilities is crucial for project management success. Here

are some pointers for growing your project management leadership:
 Communicate effectively: Effective communication is essential for
effective leadership in project management. This comprises the
capacity to pay attention to and understand the demands and worries
of team members as well as the capacity to articulate expectations and
project objectives in a clear manner.
 Develop trust: Successful leadership requires a high level of trust. Being
open and honest with team members as well as keeping your word and
taking responsibility for your actions are key to developing trust.
 Establish clear expectations: It's crucial for team leaders to establish
clear expectations for their subordinates. Setting project goals and
objectives, creating project timeframes, and defining roles and
responsibilities are all part of this.
 Promote teamwork: Project management leadership includes
encouraging cooperation and teamwork among team members. This
can be accomplished by fostering open communication, fostering a
supportive team environment, and acknowledging team members'
accomplishments.
 Give members freedom to take responsibility: As a leader, it's crucial to
provide your team members the freedom to take responsibility for their
work and make decisions. This can be done by giving team members
the tools and encouragement they need to lead the project while also
encouraging them to do so.
Overall, acquiring leadership abilities is crucial for project management
success. Project managers can effectively lead and steer their teams to
accomplish project goals and objectives by communicating clearly,
cultivating trust, establishing clear expectations, encouraging teamwork, and
giving team members the freedom to make decisions.

Page 68 of 153
 Human Resource Management

Project management success depends on having strong human resource

management skills. Here are some pointers for project managers looking to
improve their human resource management abilities:
 Recognize each team member's duties and responsibilities: It's critical
for project managers to understand the duties and obligations of each
team member. You may assign assignments more successfully and make
sure team members have the resources and abilities they need to finish
their work by doing this.
 Talk to your team members: The secret to good human resource
management is effective communication. This comprises the capacity
to pay attention to and understand the demands and worries of team
members as well as the capacity to articulate expectations and project
objectives in a clear manner.
 Manage team performance: In order to make sure that the team is
accomplishing the project's goals and objectives, it is crucial for project
managers to manage the performance of their teams. This can be
accomplished by giving regular feedback, establishing performance
goals, and offering assistance and resources as required.
 Promote teamwork: Managing human resources also includes
encouraging cooperation and teamwork among team members. This
can be accomplished by fostering open communication, fostering a
supportive team environment, and acknowledging team members'
accomplishments.
 Develop team skills: It's crucial for project managers to recognise the
training and skill requirements of their teams, as well as to offer chances
for growth and learning. Training courses, mentoring relationships, and
other growth opportunities can help with this.
In general, acquiring human resource management skills is necessary for
project management success. Project managers may effectively manage the
human resources inside their projects by understanding the roles and duties of
team members, communicating clearly, managing team performance,
encouraging teamwork, and improving team skills.

Page 69 of 153
 Public Relations Management

Project management success depends on having strong public relations

management skills. Here are some pointers for project managers looking to
develop their public relations management abilities:
 Recognize the requirements and problems of stakeholders:
Understanding the requirements and worries of stakeholders, such as the
project team, clients, customers, and other crucial stakeholders, is
crucial for project managers. This will enable you to handle any potential
problems and engage with stakeholders in an effective manner.
 Talk to the stakeholders: The secret to good public relations
management is effective communication. This involves the capacity to
pay attention to and understand the wants and worries of stakeholders
as well as the capacity to articulate expectations and project objectives
in a clear manner.
 Establish a good rapport with stakeholders: It's critical for project
managers to establish a good rapport with stakeholders. Regular
communication, prompt problem-solving, and attention to the
demands of stakeholders are all ways to do this.
 Manage stakeholder expectations: Managing stakeholder expectations
is a part of public relations management. This can be done by outlining
clear expectations for the project, communicating with stakeholders
regularly about its status and any potential problems, and being open
and honest about the decision-making procedures.
 Answer questions from stakeholders: It's critical for project managers to
be ready to answer questions from stakeholders concerning their
projects. This could be sharing updates on the project's status,
addressing issues, or responding to inquiries.
In general, mastering public relations management techniques is necessary for
project management success. Project managers may effectively manage the
public relations components of their projects by understanding the
requirements and concerns of stakeholders, communicating clearly,
establishing relationships with stakeholders, managing stakeholder
expectations, and responding to stakeholder queries.

Page 70 of 153
 Service Sector Management

Project management success depends on having the right abilities for the
service sector. Here are some pointers for project managers looking to develop
their service sector management abilities:
 Recognize client needs: It's crucial for project managers to recognise
client demands and make sure the project satisfies them. To understand
client requirements, this may include gathering feedback or doing
customer research.
 Communicate with customers: Customers must be effectively
communicated with in order for service sector management to be
successful. This involves the capacity to pay attention to and understand
the demands and worries of clients as well as the capacity to effectively
communicate updates on the project and its status.
 Manage customer expectations: Managing client expectations is a
component of service sector management. Clear expectations for the
project, regular communication with clients about its status and any
potential problems, and openness regarding decision-making
procedures are all ways to achieve this.
 Encourage customer relationships: It's critical for project managers to
have a good rapport with clients. This can be accomplished by
consistent communication, prompt problem-solving, and attention to
client demands.
 Constantly enhance customer service: Service sector management
includes working to continually enhance the client experience. This
could include putting new procedures or technology into place to boost
productivity, getting consumer input to pinpoint potential improvement
areas, and making adjustments in response to client demands.
Overall, acquiring abilities in service sector management is crucial for project
management success. Project managers can successfully manage the service
components of their projects by understanding client demands, effectively
communicating, controlling customer expectations, cultivating customer
relationships, and consistently improving service.

Page 71 of 153
 Cost Management

Project management success depends on having the right project cost

management abilities. Here are some pointers for project managers looking to
improve their project cost management abilities:
 Recognize project costs: Understanding the project's costs, including the
price of supplies, labour, and any other charges, is crucial for project
managers. This will assist you in efficiently managing the project's
budget.
 Calculate project expenses: In order to stay within budget, it is crucial to
calculate project costs accurately. To generate precise figures, this may
include consulting a financial professional or useing cost estimation
software.
 Control project expenses: Project cost management includes actively
controlling project expenses to keep them within budget. This could
include negotiating agreements with vendors or suppliers, keeping an
eye on costs, and adjusting the budget as necessary.
 Routinely check the project budget: To make sure that expenditures are
on schedule and within budget, it is crucial to routinely check the project
budget. This can include keeping track of expenditures, comparing
actual costs with projections, and locating potential cost-cutting
opportunities.
 Communicate with stakeholders: It's critical for project managers to
keep stakeholders informed about the project budget and any
necessary adjustments. This includes informing stakeholders of budget
changes and any potential problems.
In general, mastering project cost management techniques is crucial for
project management success. Project managers may efficiently handle the
financial aspects of their projects by understanding project expenses, precisely
estimating project costs, managing project costs, overseeing the project
budget, and interacting with stakeholders.

Page 72 of 153
 Procurement Management

Project management success depends on having strong procurement

management abilities. Here are some pointers for project managers looking to
develop their procurement management abilities:
 Understand the procurement procedure: Understanding the
procurement process, including the processes needed to acquire
supplies and services for the project, is crucial. By doing this, you can
efficiently oversee the procurement process and make sure everything
goes according to plan.
 Find the needs of the project: It's critical to determine the products and
services required for the project in order to handle procurement
successfully. The project team may need to be consulted in order to
determine the necessary materials and resources.
 Create a procurement strategy: The measures that will be taken to get
the supplies and services required for the project are described in a
procurement strategy. This could include locating possible suppliers,
settling agreements, and creating a schedule for the procurement
procedure.
 Source providers: Finding vendors for the products and services required
for the project is crucial after the procurement plan has been created.
To do this, requests for proposals (RFPs) or requests for quotes may be
sent (RFQs).
 Contract negotiations: You can be in charge of doing so as a project
manager with suppliers. It's critical to bargain for terms that are
advantageous to the project, such as the price, the delivery schedule,
and any other clauses.
 Monitor the procurement process: Monitoring the procurement process
is essential to ensuring that it is going well and that the supplies and
services required for the project are being procured on schedule.
In general, mastering procurement management abilities is necessary for
project management success. Project managers may efficiently handle the
procurement component of their projects by understanding the procurement
process, defining project needs, creating a procurement plan, locating
suppliers, negotiating contracts, and monitoring the procurement process.

Page 73 of 153
 Risk Management

Project management success depends on having strong risk management

abilities. Here are some pointers for helping project managers strengthen their
risk management abilities:
 Determine project risks: It's critical to determine the risks the project may
face. Conducting a risk assessment to identify prospective dangers, their
likelihood, and their impact may be required.
 Analyze project risks: After risks have been found, it's crucial to assess
them to see how they might affect the project. This can include assessing
the likelihood that a risk will materialise as well as any potential negative
effects.
 Prioritize project risks: Project risks should be prioritised based on their
likelihood and possible impact after they have been thoroughly
examined. This will assist you in putting the greatest risks first.
 Create a risk management strategy: A risk management strategy
describes the actions that will be performed to manage and reduce
risks. This can include figuring out ways to reduce risks, assigning money
to do so, and setting up a procedure for keeping track of and evaluating
risks.
 Monitor and review risks: In order to make sure that risks are being
effectively managed, it is crucial to routinely monitor and review risks.
This can include keeping track of how risk mitigation techniques are
working and spotting any potential new threats.
In general, mastering risk management techniques is necessary for project
management success. Project managers may manage the risks connected
with their projects successfully by identifying, evaluating, and prioritising project
risks, creating a risk management plan, and continuously monitoring and
reviewing risks.

Page 74 of 153
 Performance Management

Project management success depends on having strong performance

management skills. Here are some pointers for project managers who want to
improve their performance management abilities:
 Set project objectives: Setting up specific, quantifiable goals for the
project is crucial. This will make it easier to keep the project on course
and track advancement.
 Create a plan for performance evaluation: The metrics that will be used
to monitor the project's progress and evaluate the performance of the
project team are described in a performance measurement plan.
Metrics like project budget, schedule, and quality may be included in
this.
 Routinely monitor and assess project performance: To make sure the
project is moving forward and that any problems can be found and
dealt with right away, it is crucial to routinely monitor and assess project
performance.
 Analyze the project's performance: Regular evaluations of the project's
and the project team's performance are crucial. In order to do this, it
may be necessary to evaluate performance, analyse data and metrics,
and pinpoint problem areas.
 Give the project team feedback and support: In order to help the team
perform better, it is crucial for the project manager to give the team
feedback and support. This might include offering direction and
mentoring as well as locating chances for learning and growth.
Overall, improving performance management abilities is crucial for project
management success. Project managers may effectively manage the
performance of their projects and project teams by defining project goals,
creating a performance measurement plan, monitoring and tracking project
performance, reviewing project performance, and offering feedback and
assistance.

Page 75 of 153
Ethical Issues and Professionalism in Project Management

In project management, professionalism and ethical issues are crucial factors.

Some significant moral dilemmas and professional matters in project
management include:
 Conflicts of interest: It's critical to make sure there aren't any that could
have an impact on the project. This can include outlining any
interpersonal or professional connections that might have an impact on
the endeavour.
 Professionalism: When interacting with team members, stakeholders,
and clients, project managers should follow the rules of professional
behaviour. This may include preserving privacy, acting honourably, and
respecting the rights of others.
 Potential social and environmental effects: Project managers have a
responsibility to consider the potential social and environmental effects
of their work and work to reduce any unfavourable effects. In order to
do this, project decision-making may take sustainability, community
involvement, and environmental effect into account.
 Ensure compliance: Project managers must make sure that the project
complies with all applicable laws and regulations. This can include
getting the required licences, adhering to safety rules, and making sure
that contracts and agreements are legitimately binding.
Overall, professionalism and ethical issues are crucial factors in project
management. Project managers can make sure that their projects are ethical
and professional by taking into account conflicts of interest, upholding
professional conduct, taking into account social responsibility, and making
sure there is legal compliance.

Page 76 of 153
 Introduction to Agile

The goal of agile project management is to quickly and incrementally provide

working software while maintaining a flexible and iterative project
management process. The Agile Manifesto, a set of beliefs and principles that
direct the development of Agile techniques, serves as the foundation for agile
project management.
The following are some of the fundamentals of agile project management:
 Placing a priority on customer happiness through regular software
release that works
 Allowing for change, even when it's late in the project
 Relying primarily on face-to-face interaction for communication
 Progress evaluation using functional software
 Maintaining a work rate that is manageable for the team.
There are several Agile methodologies that are commonly used in project
management, including Scrum, Lean, and Extreme Programming (XP). Each of
these Despite the fact that each methodology has its unique set of processes
and procedures, they all follow the guidelines in the Agile Manifesto.
Although it can be used for various kinds of projects, agile project
management is frequently used in software development projects. It is best
suited for projects that are intricate, fraught with ambiguity, or necessitate
regular communication with the client.
The ability of the project team to react fast to changes in the project
environment is one of the key advantages of Agile project management.
Additionally, it helps in ensuring that the project provides value to the client as
soon as feasible, which may boost client satisfaction.

Page 77 of 153
 Uses, Pros, and Cons of Agile

Uses:
 Although it can be used for various kinds of projects, agile project
management is frequently used in software development projects. It is
best suited for projects that are intricate, fraught with ambiguity, or
necessitate regular communication with the client.
Pros:
 Gives room for adaptability and flexibility on providing value to the
customer.
 Promotes face-to-face interaction and teamwork
 Enables the quick and regular release of functional software
 Can result in higher client satisfaction
Cons:
 Not necessarily appropriate for all projects.
 Requires great teamwork and leadership abilities.
 Possibly calls for a change in the organization's culture
 It might be challenging to estimate time and resources accurately.
 Those who are unfamiliar with agile approaches could have a learning
curve.

Page 78 of 153
 Key Agile Principles and Concepts

Agile project management is based on a number of essential ideas and tenets.

These consist of:
 Lean Manifesto: A set of ideals and guiding principles known as the Agile
Manifesto directs the creation of Agile techniques. Customer happiness,
functional software, and cooperation are given precedence over
processes and tools.
 Iterative and incremental approach to development: Agile approaches
rely on an iterative and incremental approach to development, which
means the project is divided into manageable pieces and delivered in
instalments. Each advancement builds on the one before it and gives
the customer more value.
 Self-organizing: Agile teams are self-organizing, which means they
decide how to carry out the work in the most effective way possible.
Strong teamwork and collaboration abilities are needed for this.
 Working software: Agile places a strong emphasis on creating usable
software as soon as possible. This makes it possible to ensure that the
project provides value to the client as quickly as possible.
 Face-to-face communication: Agile places a strong emphasis on face-
to-face communication as the main channel for team collaboration.
 Sustainable rate of production: Agile teams should strive to maintain a
sustainable rate of production over the long haul. This keeps the
workforce motivated and ensures dependable performance.
 Receptive and ready: Agile teams should be receptive to continual
improvement and ready to adjust to change. A culture of ongoing
research and experimentation is necessary for this.

Page 79 of 153
 Agile Terminologies

Numerous words are frequently used in Agile project management. Some of

these consist of:
 Scrum: Scrum is an Agile framework that is frequently applied in the
creation of software. It is founded on the ideas of openness, scrutiny, and
adaptation.
 Product owner: The product owner is in charge of outlining the features
and priorities for the final product. To ensure that the product fits the
needs of the consumer, they collaborate closely with the development
team.
 Scrum master: The scrum master is in charge of directing the Scrum
process and making sure the team follows the Scrum tenets.
 Sprint: A sprint is a predetermined amount of time (often two to four
weeks) during which a particular set of tasks gets finished. The team
should have a working product increment at the conclusion of the sprint.
 Sprint planning: is a meeting that is done before each sprint to decide
what tasks will be accomplished during the sprint.
 Daily stand-up meeting: This quick meeting is held each day to discuss
the team's success and any challenges they may be having.
 Sprint reviews: Sprint reviews are meetings held at the conclusion of
each sprint to assess the work that has been done and to make plans
for the following sprint.
 Retrospective: Meeting held at the conclusion of each sprint to discuss
what went well and what could be improved for the following sprint is
known as a retrospective.

Page 80 of 153
 Getting started with Agile

There are a few crucial steps you can take to get started if you are new to
Agile project management. These consist of:
 Learn the fundamentals and guiding principles of Agile: This will assist you
in understanding the core principles of Agile and how they differ from
more conventional project management techniques.
 Determine which Agile framework is best for your project: You have a
number of options, including Scrum, Lean, and Kanban.
 Create a cross-functional team: Create a cross-functional team with the
knowledge and abilities required to finish the project.
 Create a product backlog: Create a product backlog with user stories
and specify the product's vision and goals.
 Value cooperation and improvement: Create an atmosphere at work
that values cooperation and improvement over time.
 Have regular planning and meetings: To keep the project on track and
continuously enhance the procedure, have regular sprint planning, daily
stand-up, sprint review, and retrospective meetings.
 Track progress: Track progress and manage the project using project
management tools like Trello or JIRA.
 Continually modify: Continually modify the project strategy in light of
criticism and evolving conditions.

Page 81 of 153
 Career in Agile

Agile project management may be a lucrative and difficult professional path.

Cross-functional teams under the direction of agile project managers are
tasked with producing high-quality goods and services. They must be able to
adapt to change, communicate well, and think outside the box to find
solutions.
Scrum Master, Product Owner, Agile Coach, and Agile Project Manager are
just a few of the roles and designations used in Agile project management.
Depending on the particular organisation and project, each function may
have a varied set of obligations and needs.
It is frequently beneficial to acquire professional credentials to advance in an
Agile career. Certified ScrumMaster (CSM), Professional ScrumMaster (PSM),
and Certified Agile Coach are a few well-known Agile credentials (CAC). To
qualify for these certificates, you must show that you have the necessary
education, work history, and Agile project management abilities through an
assessment procedure.
Project management, communication, leadership, and technical expertise in
the relevant business or subject are additional advantageous traits for an Agile
profession. Maintaining current with the newest Agile methods and trends can
also be benefited by continuing education and professional development.

Page 82 of 153
 Professional Agile Leadership (PAL I)

The Agile Leadership Institute offers the Professional Agile Leadership (PAL I)
certification (ALI). Professionals that desire to advance their leadership abilities
and methods in an Agile environment should use it.
The following leadership competencies are the ones that the PAL I certification
focuses on building:
 Vision: The capacity to formulate a compelling vision for a project or
organisation and to successfully convey it to others.
 Strategy: the capacity to create a strong strategic plan and to match
the project or organisation with the broader goals and vision.
 Culture: the capacity to promote an environment that supports Agile
techniques and concepts.
 People: the capacity to build and lead a high-performing team and to
promote team members' personal and professional development.
Candidates must finish a three-day training programme and an exam to be
qualified as a PAL I. Agile concepts and principles, leadership styles,
communication, and team development are among the subjects covered in
the programme. The evaluation, which is a multiple-choice test, gauges
candidates' knowledge and comprehension of the PAL I competencies.
Professionals who wish to enhance their careers in Agile leadership and have
a positive impact on their businesses or projects should earn the PAL I
certification.

Page 83 of 153
 Professional Agile Leadership - Evidence Based

Management (PAL-EBM)

The Agile Leadership Institute offers a credential called Professional Agile

Leadership - Evidence Based Management (PAL-EBM). It is made with a focus
on leveraging data and evidence to guide decision-making for professionals
who wish to advance their leadership practices in an Agile environment.
The following leadership competencies are the ones that the PAL-EBM
certification focuses on building:
 Evidence: the capacity to gather, examine, and use information and
proof to guide decisions and solve problems.
 Experimentation: the capacity to plan and carry out experiments to
validate assumptions and test hypotheses.
 Learning: the capacity to improve procedures and practices by
continual learning from experience.
 Collaboration: the capacity to create mutual respect and trust amongst
members of different teams as well as within them.
To become certified as a PAL-EBM, candidates must complete a three-day
training course and pass an assessment. The training covers topics such as
Agile values and principles, evidence-based management, experimentation,
and learning organizations. The assessment is a multiple-choice exam that tests
knowledge and understanding of the PAL-EBM competencies.
Professionals who wish to enhance their careers in Agile leadership and use an
evidence-based strategy to decision-making and problem-solving may
consider earning the PAL-EBM certification.

Page 84 of 153
 Introduction to Scrum

Although Scrum is a popular Agile framework for software development, it may

also be used for other kinds of projects. It encourages the creation of functional
products through a series of brief, iterative cycles known as sprints and is built
on the ideas of transparency, inspection, and adaptation.
At the conclusion of each sprint in Scrum, a cross-functional team collaborates
to deliver a product increment. The team is self-managed and organised, with
a priority on providing value to the client.
Scrum framework’s three roles:
1. Product owner
2. Development team
3. Scrum master
Scrum framework’s five events:
1. Sprint planning
2. Daily stand-up
3. Sprint review
4. Sprint retrospective
5. Backlog refinement
Scrum framework’s three artifacts of
1. Product backlog
2. Sprint backlog
3. Increment
Scrum is a versatile and adaptable framework that can be used to swiftly
create value and manage complex projects. It has been successfully used to
assist firms in increasing their effectiveness, quality, and customer satisfaction.
It is commonly used in the software sector.

Page 85 of 153
 Uses, Pros, and Cons of Scrum

Scrum has a variety of uses, including software development, but it can also
be used for other kinds of projects, including event planning, product
development, and marketing campaigns. It is ideally suited for projects that
are complicated, unclear, or have requirements that change quickly.
Pros of Scrum:
 Increases accountability and transparency
 Enhances cooperation and communication
 Improves client satisfaction
 Quickly delivers value
 Increases team spirit
Cons of Scrum:
 Requires the team to be extremely dedicated and disciplined.
 In a conventional, hierarchical company, it can be difficult to
implement. It might need more resources and training.
 Not necessarily appropriate for all projects.

Page 86 of 153
 Key Scrum Principles and Concepts

The following are some essential Scrum ideas and principles:

 Empiricism: Scrum is built on the idea that experience is the best teacher
and that decisions should be made based on the information available
at the moment. Throughout the project, the Scrum team collects input
and data in order to make educated decisions and adjust to changing
circumstances.
 Self-organization: Scrum encourages team members to work
independently. Each team member is in charge of doing their own work
and working together to produce value.
 Cross-functional team: Scrum teams are cross-functional, which means
they possess all the knowledge and abilities required to deliver a product
increment.
 Timeboxed events: Events that are timeboxed are those that have a set
duration, such as sprint planning, the daily stand-up, and the sprint
review. This assists in concentrating the team's efforts and ensuring
project continuity.
 Incremental delivery: Scrum places a strong emphasis on delivery in
increments, in which the team provides a working product increment at
the conclusion of each sprint. By doing so, risk is reduced and customers
receive benefit more rapidly.
 Adaptive planning: Scrum uses an iterative, adaptive planning method
in which the team replans at the start of each sprint in light of the most
recent information. By doing so, the team is better equipped to focus on
things that are most important to them and adjust as needed.

Page 87 of 153
 Scrum Terminologies

Here are a few terms used frequently in Scrum:

 Product backlog: The work that has to be done as part of a project is
listed in the product backlog. The product owner prioritises it and it
consists of user stories, flaws, and technical tasks.
 Sprint backlog: It is a list of tasks that the team intends to do over the
course of a sprint. It is derived from the product backlog, and the team
is in charge of managing and owning it.
 User story: A description of a feature from the viewpoint of the user is
known as a user storey. The team uses it to understand the value the
product will provide to the user and to capture the functionality that is
needed.
 Velocity: Velocity is a measurement of how much work a team can
accomplish in a sprint. It is used to anticipate how much work the team
can finish in upcoming sprints and to spot areas for development.
 Burn-down chart: A burn-down chart is a visual depiction of the amount
of work still in the sprint backlog over time. It helps in tracking
development and spotting future problems for the team.
 Definition of Done: A product increment must satisfy a set of
requirements known as the Definition of Done in order to be deemed
complete. It makes sure that the group produces high-caliber work.

Page 88 of 153
 Getting started with Scrum

Here are some actions to take to begin using Scrum:

 Gather the team: Since Scrum is a team-based methodology, the first
step is to put together a group of individuals who will be in charge of
delivering the product. The group should be cross-functional and
comprise all the necessary knowledge and abilities.
 Find the owner of the product: The task of establishing the features and
priorities for the product falls to the product owner. To make sure the
product satisfies the needs of the consumer, they collaborate closely
with the development team.
 Choose a scrum master: The scrum master is in charge of assisting the
Scrum process and making sure the team follows its rules.
 Create product backlog: The work that needs to be done as part of the
project is listed in the product backlog. The product owner should
prioritise it and include user stories, defects, and technical tasks in it.
 Plan the first sprint: The first sprint is an opportunity for the team to
familiarise themselves with the Scrum process and to deliver a brief
portion of work. To determine the tasks that will be accomplished during
the sprint and to construct the sprint backlog, the team should
collaborate with the product owner.
 Conduct the sprint: The team should concentrate on finishing the tasks
on the sprint backlog during the sprint. Daily stand-ups should be
facilitated by the scrum master in order to monitor progress and spot any
problems that need to be fixed.
 Review and retrospect: At the conclusion of the sprint, the team should
meet with the product owner to discuss the work that has been
performed and hold a retrospective to consider what went well and
what could be improved for the following sprint. The team should make
use of this input to modify their procedures and perform better in
upcoming sprints.
 Repeat the process: The team should repeat these processes for each
sprint until the project is finished because Scrum is an iterative
methodology. The product backlog will change as the project goes
along, and the team will keep delivering tiny pieces of functional
software.

Page 89 of 153
 Career in Scrum

Scrum offers a variety of career paths, including those for the Scrum master,
product owner, and development team member. Software development is
where Scrum experts often work, however Scrum can be used on any kind of
project in any sector.
 Certified Scrum Master (CSM): For Scrum practitioners, the Certified
Scrum Master (CSM) certification is a widely recognised credential.
People must finish a training programme and pass an exam to become
CSMs.
 Professional Scrum Master (PSM): Scrum offers a higher level of Scrum
certification called Professional Scrum Master (PSM). People must pass a
series of examinations to prove they understand Scrum in order to
become a PSM.
 Scrum Master Professional Certificate (SMPC): The Scrum Alliance offers
the Scrum Master Professional Certificate (SMPC) as a qualification. It is
intended for seasoned Scrum masters who wish to showcase their
superior knowledge and abilities.
 Professional Scrum with User Experience (PSU): Professionals who wish to
show that they can apply Scrum concepts to user experience design
can get the Professional Scrum with User Experience (PSU) certification
from.
 Professional Scrum with Kanban (PSK): Scrum offers the Professional
Scrum with Kanban (PSK) certification to professionals who want to
demonstrate their proficiency in combining Scrum and Kanban.
 Disciplined Agile Scrum Master (DASM): The Disciplined Agile Consortium
offers the Disciplined Agile Scrum Master (DASM) certification to
professionals who want to prove their proficiency in integrating Scrum
with disciplined agile concepts.
 Scaled Professional Scrum (SPS): Scrum organization offers the Scaled
Professional Scrum (SPS) certification to professionals who want to prove
their proficiency in using Scrum at scale.
 Professional Scrum Developer (PSD): Professionals who want to show that
they can apply Scrum principles to software development can earn the
Professional Scrum Developer (PSD) certification from Scrum
 Product Owner for Scrum (PSPO): For professionals that want to prove
their competence as a Scrum product owner, Scrum organization offers
the Scrum Product Owner (PSPO) certification.

Page 90 of 153
 Certified Scrum Master (CSM)

A certification programme called Certified Scrum Master (CSM) is available to

professionals who want to prove they have a thorough grasp of the Scrum
framework. People must successfully finish a CSM training course and an exam
in order to become CSMs. A scenario-based simulation and multiple-choice
questions are frequently included in assessments.
A CSM certification can help people showcase their Scrum knowledge and
enhance their use prospects. Additionally, it can aid businesses in finding
personnel who are knowledgeable about Scrum and capable of successfully
implementing the framework inside their teams.

Page 91 of 153
 Professional Scrum Master (PSM)

The independent organisation Scrum organization, which offers training,

exams, and certification in Scrum, offers the Professional Scrum Master (PSM)
credential. Professionals that are in charge of facilitating Scrum within their
organisations are eligible for the PSM certification. Candidates for the
certification must possess a thorough understanding of Scrum's guiding
principles and values, as well as the abilities and methods required to
successfully implement Scrum in a range of situations. Candidates for the PSM
certification must pass an online exam that gauges their comprehension of
Scrum and their aptitude for using it in practical settings. Professionals wishing
to enhance their careers in project management or agile development may
find the highly acclaimed PSM certification to be an invaluable asset.

Page 92 of 153
 Scrum Master Professional Certificate (SMPC)

For people who have a thorough understanding of the Scrum framework and
who wish to demonstrate their capacity to use Scrum in a professional setting,
the Scrum Master Professional Certificate (SMPC) is a professional credential.
Individuals must demonstrate their knowledge and understanding of Scrum
through a combination of classroom study and practical experience in order
to acquire the SMPC. They can take an online exam to obtain the SMPC after
completing the appropriate education and gaining the necessary
experience. The Scrum Alliance, a specialised group that promotes the use
and use of Scrum in businesses all around the world, has acknowledged the
SMPC.

Page 93 of 153
 Professional Scrum with User Experience (PSU)

A certification course called Professional Scrum with User Experience (PSU)

teaches professionals how to incorporate Scrum methods and principles into
user experience (UX) design. The certification focuses on user research and
testing's critical role in producing successful products, as well as the Scrum
Master's role in promoting the integration of UX design into the development
process. People must have a solid grasp of Scrum and UX design in addition to
completing a course or training programme provided by an authorised
training provider in order to become PSUs. They must pass a certification test
after completing the programme in order to earn the PSU designation. Scrum
organization, an organisation that offers training, certification, and tools for
professionals interested in implementing Scrum in their work, is the provider of
the certification.

Page 94 of 153
 Professional Scrum with Kanban (PSK)

Scrum organization's Professional Scrum with Kanban (PSK) certification

programme is geared toward combining the Scrum framework and Kanban
techniques. The certification's objective is to assist individuals and companies
in enhancing their capacity to produce value by combining Scrum with Lean
and Kanban principles. The certification covers subjects like the ideas,
methods, and techniques of Kanban as well as how to combine Kanban and
Scrum to improve delivery efficiency. Individuals must successfully complete a
two-day course and a multiple-choice exam to obtain the PSK certification.

Page 95 of 153
 Disciplined Agile Scrum Master (DASM)

The Disciplined Agile Scrum Master (DASM) certification is a professional

credential for Scrum Masters who want to show that they have the knowledge
and abilities to use the Disciplined Agile (DA) framework to help firms adopt
and enhance their agile practices. The Disciplined Agile Consortium, an
independent company that offers direction and support to businesses and
individuals interested in utilising the DA framework, offers the DASM
certification. People must finish a training programme and ace a certification
exam to become DASMs. The training programme covers the DA framework's
guiding concepts and practices as well as how to put them to use in a Scrum
environment. The certification exam gauges a candidate's proficiency with
the DA framework and their ability to apply it in practical situations.

Page 96 of 153
 Scaled Professional Scrum (SPS)

A framework for scaling Scrum to significant and complicated projects is called

Scaled Professional Scrum (SPS). It is intended to assist firms in successfully
implementing Scrum at the corporate level and in managing the difficulties
that can occur while scaling agile methods. SPS offers instructions on how to
implement the transparency, inspection, and adaptation principles in the
context of significant, complex projects. Best practices are included for
managing dependencies and team integration as well as for dealing with
multiple Scrum teams, coordinating work across teams, and working with
multiple Scrum teams. Organizations aiming to scale agile initiatives or those
already utilising Scrum that want to improve their scaling strategy may consider
SPS. In order to provide a thorough approach to scaling agile methods, it is
generally used in concert with other Scrum frameworks, such as Scrum@Scale
or Large Scale Scrum (LeSS).

Page 97 of 153
 Professional Scrum Developer (PSD)

Professional Scrum Developer (PSD) is a certification programme provided by

Scrum organization to honour people who have proven a thorough
comprehension of the Scrum framework and know how to use it effectively to
create software utilising contemporary development techniques. Individuals
must successfully finish a two-day course and a demanding exam to obtain
this certification. Software developers, testers, and other technical
professionals who wish to advance their knowledge of using Scrum to produce
high-quality software products should consider earning this certification. The
PSD certification focuses on the technical methods, such as test-driven
development, continuous integration, and refactoring, that are crucial to
Scrum and Agile software development. Professionals can prove their
knowledge in these areas and their capacity to collaborate successfully in a
Scrum team by obtaining this certification.

Page 98 of 153
 Scrum Product Owner (PSPO)

The Scrum organization organisation offers the Scrum Product Owner (PSPO)
certification as a professional credential. It is intended for people who are
primarily in charge of overseeing the product backlog and making sure the
final product provides value to the client. People who want to become
certified as product owners (PSPOs) must pass an exam and show that they
have a solid grasp of the Scrum framework's tenets, processes, and roles. The
certification is valid for two years after which time persons must go through the
renewal process in order to keep their certification.

Page 99 of 153
 Introduction to Kanban

The Kanban technique is a way to control how work is done in a team,

especially in manufacturing and software development. It was created by
Toyota industrial engineer Taiichi Ohno to increase the productivity of the
company's production line. Just-in-time (JIT) production, which strives to
decrease waste by only manufacturing what is required, when required, is the
foundation of the Kanban system.
Kanban uses cards on a board to represent work, with each column denoting
a different step of the work process. The card is transferred to the following
column as work is finished. The team is able to examine the work's current state
and pinpoint any bottlenecks or delays thanks to this visual representation of
the project.
The needs of the team and the project can be catered to using the flexible
Kanban method. It frequently works in tandem with other Agile techniques like
Scrum. Improved collaboration, better process visibility, and increased
adaptability to changing requirements are a few advantages of implementing
Kanban.

Page 100 of 153

 Uses, Pros, and Cons of Kanban

Uses of Kanban:
Kanban is a project management technique that is frequently used in
manufacturing and software development. It is built on the just-in-time (JIT)
production tenets and intended to assist teams in providing goods or services
more successfully and efficiently.
Pros of using Kanban:
 Kanban assists teams in locating and removing bottlenecks in their
workflow, which can increase productivity and decrease waste.
 Teams may monitor the status of their work in real-time, which can speed
up the identification and resolution of problems.
 Kanban is adaptable and simple to tailor to the requirements of various
teams and projects.
 It is easy for teams to get started with because it is straightforward to
learn and apply.
Cons of using Kanban:
 Not all project types can benefit from kanban, and it might not be the
best option for projects with stringent deadlines or those that demand a
high degree of predictability.
 Team members must be extremely dedicated and disciplined in order
for it to be successful.
 For teams who are not accustomed to working in an Agile setting,
Kanban might not be the best option.
 Kanban project management techniques may make it more
challenging to evaluate a team's performance than other project
management techniques.

Page 101 of 153

 Key Kanban Principles and Concepts

An approach to project management called Kanban places a strong

emphasis on continuous delivery, continuous improvement, and task visibility.
Here are some essential Kanban tenets and ideas:
 Visualize the work: The progress of the task is shown on Kanban visual
boards. This makes the work more transparent and understandable.
 Limit work in progress: Teams are encouraged by Kanban to keep their
work-in-progress (WIP) to a minimum. This encourages the team to
concentrate on finishing tasks rather than beginning new ones.
 Manage flow: Instead of focusing on controlling individual tasks, Kanban
manages the flow of work through the system. This facilitates process
optimization and accelerates value delivery.
 Continuous improvement: Teams are encouraged by Kanban to
continuously improve the process by evaluating performance, locating
bottlenecks, and implementing adjustments.
 Collaboration: To make sure that the work is in line with corporate
objectives and customer expectations, Kanban promotes collaboration
between team members and stakeholders.
 Adaptability: Teams can respond to environmental changes and modify
the process thanks to the flexibility and adaptability of Kanban.

Page 102 of 153

 Kanban Terminologies

Several terms that are frequently used in Kanban include:

 The Kanban board: The work and its progress are shown visually on a
Kanban board. Typically, it has cards for each piece of work and
columns for each step in the process.
 WIP limit: The most objects that can be actively being worked on at once
is known as the WIP limit. Setting WIP limitations encourages the team to
focus on finishing projects rather than beginning new ones.
 Pull system: Work is only started under a pull method of workflow
management when there is capacity to finish it. This keeps the system
from becoming overloaded and ensures that the work is done
effectively.
 Cadence: The rhythm or frequency of work in the system is referred to as
cadence. The frequency of planning meetings, review meetings, and
delivery intervals are a few examples of this.
 Value stream: The process that a piece of work goes through from
conception to completion is known as the value stream. By locating
bottlenecks and enhancing the flow of work, Kanban helps in value
stream optimization.
 Lead time: Lead time is the amount of time that passes between the
commencement of a project and its conclusion. By streamlining the
process and minimising waste, Kanban reduces lead time.

Page 103 of 153

 Getting started with Kanban

Using these methods, you can begin using Kanban:

 Define your process: Start by outlining each phase of your process, from
beginning to end. This will enable you to understand the workflow and
spot any inefficiencies or bottlenecks.
 Set up a Kanban board: Create a Kanban board after that to see the
work in progress. This might be a real-world board or a computer
programme like Trello. The board should have cards for each task and
columns for each process phase.
 Set WIP limits: Limit the amount of tasks that can be active at once to
help the team stay focused on finishing projects rather than beginning
new ones. As a result, the work flow will be improved, and delivery times
will increase.
 Start using the Kanban board: Move the matching cards across the
board as work is finished to demonstrate progress. By doing so, it will be
easier to keep track of what has been finished and what is still being
worked on.
 Measure and improve: Utilize metrics to gauge the efficiency of the
process, such as lead time and cycle time. To enhance flow and delivery
speed, identify any bottlenecks or inefficiencies and alter the
procedure.
 Review and adjust: Review the Kanban board frequently and make
necessary adjustments to the procedure. This will ensure that the work is
in line with the company's objectives and its clients' requirements.

Page 104 of 153

 Career in Kanban

For those interested in project management and continuous development, a

career in Kanban might be an interesting and fulfilling option. There is a rising
need for experts with Kanban knowledge and abilities as agile approaches
gain popularity.
People may think about enrolling in a Kanban training course to master the
concepts and methods of the approach before beginning a career in the
methodology. Building competence and reputation in the sector can also
benefit from certification programmes like the Kanban Coaching Professional
(KCP) or the Kanban Management Professional (KMP).
Kanban coaches, trainers, consultants, and project managers are just a few of
the career options open to those with these skills. These specialists may operate
in a range of sectors, including manufacturing, healthcare, and software
development.
People interested in a career in Kanban should have excellent
communication, cooperation, and problem-solving skills in addition to their
technical knowledge and skills in order to succeed in their positions.

Page 105 of 153

 Introduction to Scaled Agile Framework® (SAFe)

A framework for implementing agile methods throughout a whole enterprise is

the Scaled Agile Framework (SAFe). By coordinating strategy, execution, and
delivery across several teams, it is intended to assist enterprises in delivering
complex products and systems more quickly and effectively. Lean, Agile, and
systems thinking are the foundations of SAFe, which strives to establish a culture
of ongoing learning and development. SAFe has grown to be a well-liked
framework for businesses wishing to scale up agile techniques. In order to apply
agile techniques in a way that is in line with their business goals and objectives,
it contains a set of principles, roles, procedures, and structures.

Page 106 of 153

 Uses, Pros, and Cons of SAFe

A project management framework called Scaled Agile Framework® (SAFe) is

intended to support organisations in scaling Agile techniques to big,
complicated projects. It offers a framework for organising the work of
numerous Agile teams and is founded on the principles of Lean, Agile, and
systems thinking.
Several industries, including software development, manufacturing, banking,
and healthcare, can use SAFe. It is especially well suited for organisations that
need a mechanism to coordinate and harmonise the work of several Agile
teams working on various projects.
Some of the pros of using SAFe include:
 Scaling Agile methodologies to large, complicated projects is beneficial.
 It offers a structure for coordinating the efforts of various Agile teams.
 It encourages cooperation and dialogue amongst groups of people
and different stakeholders.
 It promotes ongoing development and assists teams in completing tasks
more quickly.
Some of the cons of using SAFe include:
 It may be challenging to implement successfully and call for support and
training.
 It might not be appropriate for businesses that aren't prepared to
completely commit to an agile strategy.
 It might call for considerable adjustments to current procedures and
organisational frameworks.
 It can call for the use of fresh equipment and technology.

Page 107 of 153

 Key SAFe Principles and Concepts

In order to scale Agile methods and provide value more effectively and
efficiently, businesses might use the Scaled Agile Framework (SAFe), a project
management framework. SAFe's fundamental ideas and tenets include the
following:
 Lean-Agile principles: Based on Lean-Agile concepts, SAFe emphasises
speedy value delivery, ongoing process improvement, and giving teams
decision-making authority.
 Value streams: Work is divided into value streams by SAFe, which are
end-to-end value flows from conception to delivery. This facilitates
coordinating activities with organisational objectives and client
demands.
 Agile release trains: SAFe uses Agile release trains (ARTs) to manage
collaboration across many teams. ARTs are self-managing, self-
organizing teams that collaborate to provide value.
 Lean-Agile leaders: SAFe places a strong emphasis on the value of Lean-
Agile leaders who can forge a climate of constant improvement and
enable teams to produce results.
 Lean-Agile portfolio management: Lean-Agile portfolio management is
a component of SAFe that helps organisations in setting priorities and
selecting investments wisely.
 Lean-Agile governance: SAFe incorporates a Lean-Agile governance
mechanism that helps organisations in coordinating strategy with
execution and selecting investments and risks with knowledge.

Page 108 of 153

 SAFe Terminologies

The Scaled Agile Framework, sometimes known as SAFe, is a framework for

putting Agile practices into practice at the corporate level. Here are several
SAFe terms that are frequently used:
 Agile Release Train (ART): A long-lasting team that works on a constant
flow of value is known as an Agile Release Train. It comprises of numerous
Agile teams cooperating to provide value to the client.
 Program Increment (PI): When the Agile Release Train produces a full
increment of value during a time-boxed iteration of work, it is known as
a programme increment.
 Value Stream: The entire process of producing value for the client, from
conception to delivery, is known as a value stream.
 Portfolio: SAFe's Portfolio level serves as the organization's strategic level.
Its duties include establishing the strategic vision and coordinating the
business with client needs.
 Solution: In SAFe, the architectural level of the organisation is
represented by the Solution level. It is in charge of defining the technical
vision and making sure the solution fits the needs of the business.
 Team: The tactical level of the organisation in SAFe is represented by the
Team level. It is in charge of providing value to the client by creating
functional software.

Page 109 of 153

 Getting started with SAFe

The following actions must be taken in order to begin using SAFe:

 Review the SAFe framework and its principles: It's crucial to understand
the SAFe framework and its guiding principles before putting it into
practice. You need to learn how SAFe functions and how it can help
your organisation from doing this.
 Identify your business objectives: Identifying your business goals is the first
step in implementing SAFe. This will assist you in understanding what you
hope to accomplish with SAFe and how it can assist you in achieving
your objectives.
 Assess your current state: The next step is to evaluate where you are right
now. This will make it easier for you to see where you are right now and
how far you still have to go to achieve your goals.
 Define your Lean-Agile transformation: Your Lean-Agile transformation
will need to be defined based on your business goals and existing
situation. Making a strategy to accomplish the changes you need to
make to your business will include determining what needs to change.
 Implement SAFe: You can start implementing SAFe in your company
after defining your Lean-Agile transformation. This will include teaching
SAFe to your team members, building up your Lean-Agile framework,
and putting SAFe concepts and tools into practice.
 Measure and improve: It's crucial to track your development and
pinpoint opportunities for improvement as you apply SAFe. This will
enable you to achieve your company goals and continuously enhance
your Lean-Agile transformation.

Page 110 of 153

 Career in SAFe

Professionals interested in Agile project management may find a satisfying

career path in the SAFe (Scaled Agile Framework). With the use of the SAFe
framework, organisations may apply Agile principles to bigger projects and
programmes. It offers a set of ideas and standards that can be modified to
meet the unique requirements of an organisation.
Professionals have a variety of roles within SAFe to choose from. These consist
of:
 SAFe Program Consultant: A SAFe Program Consultant assists
organisations with the implementation of SAFe and offers advice on how
to tailor the framework to meet their particular requirements. Teams may
receive coaching and training from them as well.
 SAFe Agile Coach: A SAFe Agile Coach helps teams and people in
implementing Agile principles inside the SAFe framework. They could
additionally train and guide team members.
 SAFe Product Manager/Product Owner: The features and requirements
for a product inside the SAFe framework must be defined and prioritised
by a SAFe Product Manager or Product Owner. To ensure that the
product fits the needs of the consumer, they collaborate closely with the
development team.
 SAFe Scrum Master: Within the SAFe framework, a SAFe Scrum Master is
in charge of facilitating the Scrum process and making sure the team
adheres to the Scrum principles.
For people interested in pursuing a career in SAFe, a number of certifications
are available, including SAFe Program Consultant (SPC), SAFe Agile Coach
(SAC), SAFe Scrum Master (SSM), and SAFe Product Manager/Product Owner
(SPMPO). These credentials prove a professional's proficiency with the SAFe
framework.

Page 111 of 153

 Certified SAFe Practitioner (SP)

Scaled Agile, Inc. offers the Certified SAFe Practitioner (SP) credential. The
Scaled Agile Framework (SAFe) implementation course is intended for
professionals who wish to understand how to do so in their company. People
must finish a two-day training and pass an exam to become Certified SAFe
Practitioners. Lean-Agile leadership, Agile development approaches, and
other SAFe principles and practices are covered in the course. Multiple-choice
questions are asked during the online exam. Individuals who pass the exam
receive the Certified SAFe Practitioner (SP) credential. The renewal of this
certification, which has a two-year expiration date, requires meeting
continuing education criteria.

Page 112 of 153

 Certified SAFe Scrum Master (SSM)

The Scaled Agile Framework's developers, Scaled Agile, Inc., provide the
Certified SAFe Scrum Master (SSM) certification (SAFe). It is intended for
professionals who wish to understand how to assist the growth of high-
performing Agile teams by applying the SAFe concepts and practices.
Individuals must successfully complete a two-day training session and exam to
become a Certified SAFe Scrum Master. Lean-Agile principles and practices,
SAFe Scrum Master roles, and methods for assisting Agile teams are all covered
in the programme. With the help of the SAFe framework, it is intended to equip
participants with the knowledge and abilities they need to successfully lead
and facilitate Agile teams.

Page 113 of 153

 SAFe Agilist (SA)

Professionals who have earned the SAFe Agilist certification are known as SAFe
Agilists (SA). This certification is intended for individuals who are in charge of
overseeing enterprise-level Lean-Agile development initiatives. SAFe Agilists
are highly knowledgeable about the SAFe framework and how to use it to
support businesses in achieving their goals. They are adept at directing Lean-
Agile transformations, mentoring teams and leaders in Lean-Agile techniques,
and directing agile ceremonies and events. SAFe Agilists are also capable of
assisting organisations in building Lean-Agile ideals, concepts, and practices in
order to enable Lean-Agile development. They are often seasoned
professionals with training in software development, project management, or
similar disciplines.

Page 114 of 153

 Certified SAFe DevOps Practitioner (SDP)

The Certified SAFe DevOps Practitioner (SDP) credential honours people who
have proven their expertise in implementing DevOps practices and concepts
in a SAFe context. Individuals must finish a training programme and pass an
exam to become SDP certified. The training programme covers subjects like:
 Recognizing the DevOps tenets and practices and how they relate to a
SAFe environment
 putting continuous integration, delivery, and deployment into practice
 Collaboration and communication between the development and
operations teams should be improved.
 Agile quality practices implementation
 Measuring and enhancing the value stream's flow
Professionals that are in charge of establishing and keeping a DevOps culture
inside their firm should consider earning the SDP certification. This could involve
positions like:
 Those on the development team
 operatives on the team
 engineers for test automation and testers
 product supervisors
 Architects
 Project directors
 Alternate agents

Page 115 of 153

 Certified SAFe Program Consultant (SPC)

A professional qualification for people with experience implementing the

Scaled Agile Framework (SAFe) in their organisations is the Certified SAFe
Program Consultant (SPC). People must successfully finish a SAFe training
course and a test in order to become SPCs. The SPC certification proves a
person's proficiency in applying and leading SAFe transformations in
organisations, as well as their knowledge and comprehension of the SAFe
concepts and practices. SPCs can assist organisations in implementing and
customising SAFe to suit their unique requirements. They can also coach and
mentor other professionals in the SAFe framework.

Page 116 of 153

 Certified SAFe Product Owner/Product Manager (POPM)

A professional certificate that displays one's knowledge and abilities in the

capacities of product owner or product manager in a SAFe (Scaled Agile
Framework) environment is the Certified SAFe Product Owner/Product
Manager (POPM) certification. The POPM certification is intended for
specialists who in a SAFe context are in charge of defining and prioritising the
features and capabilities of the product or solution. It is designed for those who
want to demonstrate their knowledge and skills in the SAFe framework and
have expertise in product management or product ownership. Individuals must
take a SAFe training course and pass an exam to become POPM certified. A
person must fulfil continuing education requirements to maintain their
certification once it expires after two years.

Page 117 of 153

 Introduction to Jira

Teams frequently use Jira, a project and issue tracking programme, to

organise, monitor, and distribute software. It is created by Atlassian and is
offered in on-premises and cloud-based versions. Jira is made to be versatile
and adjustable, and it provides a wealth of features and integrations to aid
teams in efficiently managing their workload. Jira's most important
characteristics include:
 Agile tools: Jira comes with a variety of templates and features to
support agile development methods, such as burndown charts, Scrum
and Kanban boards, and velocity tracking.
 Issue tracking: Teams can generate, monitor, and fix issues for their
projects using Jira. Defects, bugs, feature requests, and tasks are all
examples of issues.
 Project planning: Jira offers project management capabilities, including
the capacity to create user stories, epics, and sprints as well as assign
tasks to team members.
 Collaboration: Jira offers a variety of collaboration options, including the
capacity to assign tasks, comment on issues, and set deadlines.
Additionally, it interfaces with other applications like Slack and
Confluence.
 Reporting: Jira offers a variety of pre-built and adaptable reports to help
teams monitor their development and success.
 Integration: Code repositories, continuous integration systems, and
customer support platforms are just a few of the many products and
services that Jira interacts with.

Page 118 of 153

 Uses, Pros, and Cons of Jira

Many firms use Jira, a well-liked project management and problem tracking
platform, to schedule, monitor, and release software. Here are some Jira uses,
benefits, and drawbacks:
Uses: Jira is used for many different things, such as agile project management,
bug tracking, and customer support. It may be used to manage projects of
any scale and across a range of sectors, including marketing, finance, and
software development.
Pros: Jira can be highly customised to meet the demands of various teams and
projects. It offers several capabilities, including as reporting, integrations with
other applications, and agile tools. Jira is simple to use and has an intuitive UI.
Cons: Jira can be pricey, particularly for bigger enterprises. Additionally, it has
a challenging learning curve and would need assistance getting up and
running. Jira has a lot of functionality and can be challenging to use, which
some users may find overwhelming.

Page 119 of 153

 Key Jira Principles and Concepts

Jira is a project management platform made to assist teams in organising,

monitoring, and debating their work. It is used by businesses of various sizes in
numerous industries. Jira's guiding principles and ideas include the following:
 Issue tracking: Teams can track and handle problems with Jira, including
bugs, tasks, and other work items. Issues can be prioritised, monitored
through various stages of development, and allocated to team
members.
 Agile tools: A variety of tools are available in Jira to help Agile
approaches like Scrum and Kanban. Agile boards, sprint planning, and
retrospective tools are some of them.
 Collaboration: Jira includes built-in collaboration capabilities to facilitate
team communication and task tracking, including comments, mentions,
and notification settings.
 Customization: Jira allows teams to develop custom fields, processes,
and reports to meet their unique needs because it is very adaptable.
 Integrations: Jira may be coupled with a range of additional tools to
enable a smooth workflow, including source control systems and chat
applications.
 Reporting: Jira offers a variety of reporting tools to assist teams in
monitoring progress and locating potential areas for improvement, such
as burn-down charts, cumulative flow diagrams, and velocity graphs.

Page 120 of 153

 Jira Terminologies

Agile teams frequently use Jira, a project and problem tracking tool. Here are
a few terms used frequently in Jira:
 Project: In Jira, a project is a group of tasks that are tracked, such as a
software development initiative or a marketing campaign.
 Issue: A specific task that must be finished as part of a project is referred
to in Jira as an issue. Bugs, tasks, and user stories are examples of issues.
 Board: The work being done on a project is visually represented on a
board in Jira. It can display how problems develop during various
workflow phases.
 Sprint: In Jira, a sprint is a predetermined time frame (often two to four
weeks) within which a certain collection of tasks is finished. Agile
software development frequently uses sprints to produce functional
product increments.
 Epic: In Jira, an epic is a substantial piece of work that is divided into
smaller problems. Epics are used to chart the development of significant
pieces of work and to put related topics together.
 Story point: Jira uses story points as a unit of measurement to gauge the
scope or complexity of an issue. They are frequently used in agile
software development to assist teams in estimating how much work can
be finished in a sprint.

Page 121 of 153

 Getting started with Jira

To begin using Jira, take the following actions:

 Open a new account: Jira offers both a free trial period and paid
subscription options.
 Organize your project: Make a new project and tailor it to your
requirements. The project specifics, work processes, and issue categories
are all customizable.
 Add people: By including their email addresses, invite your team
members to participate in the project.
 Create an issue: A task, defect, or other item of work that needs to be
finished is referred to as an issue. A team member can be given the task
of creating an issue.
 Track progress: Use Jira to keep an eye on the status of your project and
the development of your issues. Additionally, you may use it to assess
your team's performance and pinpoint any problems that require
attention.
 Work together as a team: To communicate and work together as a
team, use Jira. You can discuss work using the built-in chat feature,
attach files, and add comments to issues.
 Customize: Jira may be modified to meet your unique requirements by
adding plugins and integrations, generating new fields, and designing
unique processes.

Page 122 of 153

 Career in Jira

For those that are knowledgeable about Jira, there are numerous options
available. Several instances include:
 Jira administrator: A Jira administrator is in charge of overseeing the
organization's Jira instance. This covers creating projects, setting up
workflows, and controlling users.
 Jira developer: To satisfy the unique requirements of an organisation, a
Jira developer is in charge of developing bespoke plugins and
integrations for Jira.
 Jira consultant: A Jira consultant assists businesses with the
implementation and optimum use of Jira. Users may need to be trained,
workflows may need to be set up, and Jira may need to be integrated
with other systems.
 Jira trainer: A Jira trainer helps users of the tool become more adept at
using it by offering training and support.
 Jira support specialist: A Jira support specialist assists users with any
inquiries or issues they might have with Jira as well as with troubleshooting
any issues they might have.

Page 123 of 153

 Introduction to PRINCE2

A framework for managing all types of projects is provided by the project

management technique known as PRINCE2 (Projects IN Controlled
Environments). It was created in the UK in the 1990s by the Office of
Government Commerce, and it has subsequently gained widespread global
adoption. A process-based methodology called PRINCE2 places emphasis on
the value of segmenting a project into manageable and controllable parts. It
offers a collection of guidelines, procedures, and themes that can be modified
to fit the particular requirements of the project. Especially in the UK, the public
sector makes extensive use of PRINCE2, and the business sector does as well. It
is acknowledged as a best practice standard for project management in the
UK and elsewhere. The approach is founded on the notion that tasks should be
divided into smaller, more manageable phases, with each stage having
clearly defined objectives, outputs, and resources. This makes it possible for
projects to be well-managed, regulated, and produce the required outcomes.
A set of principles, procedures, and themes provided by PRINCE2 can be
customised to meet the unique requirements of a project. It is a versatile
approach that may be used for tasks of any scale or complexity.

Page 124 of 153

 Uses, Pros, and Cons of PRINCE2

Uses: Many different businesses, including government, banking, IT, and

construction, use PRINCE2. It is particularly effective at managing projects that
are big in scope, risky, or need a lot of collaboration between several teams
and stakeholders.
Pros:
 Defined framework and structure: It offers a defined framework and
structure for managing projects, assisting in making sure that projects are
finished on schedule, within budget, and to a high standard.
 Communication and collaboration: It encourages open lines of
communication and collaboration between team members and
stakeholders, which can lessen the likelihood of miscommunications and
delays.
Cons:
 Bureaucratic: The fact that PRINCE2 can be rather bureaucratic and
requires a lot of paperwork and processes to be followed is one potential
drawback. As a result, compared to certain other project management
approaches, it may take longer to adopt.
 Highly prescriptive: Due to the highly prescriptive nature of PRINCE2's
structure and processes, it can also be more challenging to adapt to
projects that include a significant level of uncertainty.

Page 125 of 153

 Key PRINCE2 Principles and Concepts

A process-based project management approach called PRINCE2 (Projects IN

Controlled Environments) places a strong emphasis on the business case, risks,
and organisation. It is frequently used both domestically and abroad.
Some key principles of PRINCE2 include:
 Continued business justification: The project should always be in line with
the needs and business goals of the firm.
 Learn from experience: PRINCE2 advocates informing current and future
initiatives with the knowledge gained from past projects.
 Defined roles and responsibilities: To make sure that the project is
effectively controlled and managed, PRINCE2 establishes explicit roles
and responsibilities for project management and governance.
 Manage by stages: The project is divided into manageable stages by
PRINCE2, with reviews at the conclusion of each stage to evaluate
progress and decide whether to move further or call it quits.
 Tailor to suit the project environment: The modification and flexibility
features of PRINCE2 help to make it suitable for the particular project
context.
Some key concepts of PRINCE2 include:
 Themes: The seven themes of PRINCE2—business case, organisation,
quality, planning, risk, change, and progress—must be addressed
throughout the project.
 Processes: Starting a project, initiating a project, directing a project,
controlling a stage, managing product delivery, managing a stage
border, completing a project, and starting a new project are the eight
processes that must be followed throughout the project.
 Products: A business case, project plan, risk register, and stage report are
just a few examples of the specific products that PRINCE2 specifies to be
created at different stages of the project.

Page 126 of 153

 PRINCE2 Terminologies

The project management methodology known as PRINCE2, has seven

principles, seven themes, and seven processes, and it is built on a process-
based methodology.
Some key PRINCE2 terminologies include:
 Project: A project is a special, transient undertaking made to provide a
good, service, or outcome.
 Business Case: The business case is a document that details the reasons
behind a project, along with its advantages, disadvantages, and risks.
 Product-based planning: A technique for defining, organising, and
controlling project work in terms of the goods that must be delivered is
called "product-based planning”.
 Project board: A group of people in charge of the project's overall
direction and governance is known as the project board. The project
sponsor, project manager, and other stakeholders are often included.
 Stages: A project is broken down into a number of stages by PRINCE2,
each with its own set of deliverables and goals.
 Products: The deliverables of a project are products. They may be
concrete or immaterial, such as a physical good (e.g. a report).
 Quality: The requirement to ensure that goods fulfil the necessary
standards and satisfy the needs of stakeholders is a major PRINCE2
theme.

Page 127 of 153

 Getting started with PRINCE2

You must understand the PRINCE2 methodology's guiding concepts, topics,

and processes in order to begin using it. Here are some actions to take:
 Learn about the PRINCE2 guiding principles: The methodology of
PRINCE2 is built around seven guiding principles. Continued business
rationale, learning from experience, clearly defined roles and duties,
stage-based management, exception-based management, a focus on
products, and adaptation to the project environment are some of these
principles.
 Understand the PRINCE2 themes: PRINCE2 has seven themes that
address important aspects of project management. Business case,
organisation, quality, plans, risk, change, and progress are some of these
themes.
 Understanding the PRINCE2 processes: PRINCE2 is divided into eight
procedures that address every stage of a project's lifetime. Initiating a
project, leading a project, controlling a stage, managing product
delivery, managing a stage border, concluding a project, and
concluding a product are some of these activities.
 Become licenced: You might want to think about being certified so that
you can show that you understand PRINCE2. PRINCE2 Foundation and
PRINCE2 Practitioner are the two certification levels.
 Put PRINCE2 into action: Putting PRINCE2 to use on a real project is the
greatest way to learn it. You can accomplish this by taking part in a
PRINCE2 project or by assuming a project management position inside
your company.

Page 128 of 153

 Career in PRINCE2

For people interested in project management and desiring to work in a

structured, process-driven setting, a career in PRINCE2 can be gratifying. A
well-known project management technique called PRINCE2 is used in a
number of sectors, including manufacturing, IT, and construction. Those with a
PRINCE2 certification may find it easier to find work and may be able to
demand greater compensation. It is advised to first earn the PRINCE2
Foundation and Practitioner level certifications before beginning a career in
PRINCE2. These credentials show a thorough knowledge of the PRINCE2
methodology and the capacity to apply it to actual projects. Professionals with
PRINCE2 certification may hold positions such as project manager, project
coordinator, and project support officer.

Page 129 of 153

 Introduction to Oracle Primavera

Oracle Primavera is project management software that helps in the planning,

scheduling, and management of projects for businesses. It is frequently used in
fields including engineering, oil & gas, and construction. The programme has
tools for managing resources, managing a project portfolio, and collaborating
on projects. Project managers may schedule projects, monitor their progress,
and spot and address problems as they arise with Oracle Primavera. Tools for
cost management and risk management are also included in the software.
Both an on-premises version and a cloud-based version of Oracle Primavera
are accessible.

Page 130 of 153

 Uses, Pros, and Cons of Oracle Primavera

Uses:
 Project planning and scheduling: You can use Oracle Primavera to
construct a thorough project schedule that lists all the tasks,
dependencies, and resources needed to finish the project. It also has
resources for monitoring development and predicting project
completion.
 Resource management: Oracle Primavera has capabilities for allocating
resources among several projects and managing them. This includes the
capacity to monitor resource usage, spot bottlenecks, and improve
resource distribution.
 Project control: Oracle Primavera offers tools for tracking and managing
the progress of projects. This includes the capability to monitor actual
progress in comparison to the project plan, spot deviations, and make
necessary corrections.
Pros:
 Comprehensive project management capabilities: Oracle Primavera
has a wide range of tools and functions for planning, scheduling, and
controlling projects. It has comprehensive project management
capabilities. Because of this, it's a terrific option for businesses who
require a single, integrated solution to manage all facet of their projects.
 Scalability: From small projects to large, complicated programmes,
Oracle Primavera can be used to manage projects of any size. This
makes it a fantastic option for businesses that need to manage several
projects at once.
 Customization: Oracle Primavera offers several customization options,
including the capacity to design unique fields, workflows, and reports.
As a result, businesses can modify the software to suit their own
requirements.
Cons:
 Complexity: Oracle Primavera is a comprehensive product, yet using it
can be challenging. For new users, there can be a big learning curve,
and it might need more help and assistance.
 Cost: Since Oracle Primavera is a piece of commercial software, its price
may be higher than that of some alternative project management
solutions. Because of this, groups with low funds can find it less desirable.
 Compatibility: Oracle Primavera is compatible with a particular range of
platforms and technologies. Its compatibility with other products and
systems that a company already uses could be constrained as a result.

Page 131 of 153

 Key Oracle Primavera Principles and Concepts

Oracle Primavera is a project management tool made to assist businesses with

project planning, scheduling, and control. It works especially effectively for big,
complicated projects with lots of teams and stakeholders. Oracle Primavera's
fundamental tenets and ideas include:
 Resource management: Oracle Primavera enables users to coordinate
the usage of equipment, supplies, and labour across many projects. To
ensure that resources are used effectively and efficiently, it offers tools
for resource planning, scheduling, and levelling.
 Cost management: To assist enterprises in keeping project costs under
control, Oracle Primavera offers capabilities for budgeting, cost
tracking, and deviation analysis. It enables users to create cost
accounts, keep tabs on spending, and assess actual expenditures
against projected sums.
 Risk management: Oracle Primavera has a risk management feature
that enables users to recognise, evaluate, and reduce risks in their
projects. Users can establish risk categories, provide risks probability and
implications, and develop risk response strategies.
 Collaboration: Oracle Primavera offers capabilities, such as project
dashboards, document management, and communication tools, for
interacting with team members and stakeholders. Users can
communicate about projects and work together in real time on tasks.
 Reporting and analytics: Oracle Primavera comes with a number of
reporting and analytics capabilities that let users keep tabs on the
progress of their projects, spot patterns and trends, and make informed
decisions. It offers a selection of standard reports as well as the option to
design unique reports.

Page 132 of 153

 Oracle Primavera Terminologies

Oracle Primavera is a project management tool made to assist businesses with

project planning, scheduling, and management. It is frequently used in fields
including engineering, oil & gas, and construction. The following terms are
frequently used with Oracle Primavera:
 Activity: An activity denotes a task that must be finished as a component
of a project. It can depend on other activities and is typically divided
into smaller jobs.
 Project: A project is a collection of actions that are planned and
managed to produce a particular outcome or deliverable.
 Work breakdown structure (WBS): The project's hierarchy is represented
by the work breakdown structure, which demonstrates how the work is
divided into more manageable, smaller chunks.
 Critical path: The sequence of tasks that take the longest time to
accomplish and must be done in a precise order is known as the critical
path. The whole project schedule may be significantly impacted by
delays on the critical path.
 Baseline: The baseline is the project's original plan, which included its
scope, budget, and timetable. It serves as a benchmark for tracking
development and locating plan discrepancies.
 Earned value: A measure of project progress based on the worth of
completed work is known as earned value. It is used to monitor how the
project is performing in comparison to the baseline and find any
problems or deviations.

Page 133 of 153

 Getting started with Oracle Primavera

In order to begin using Oracle Primavera, you must do the following actions:
 Oracle Primavera installation: Installing Oracle Primavera on your
computer is the first step. A current licence is required to use the
software.
 Create a new project: It is as simple as clicking the "New Project" button
after Oracle Primavera has been installed. The project needs to have a
name, a description, a start date, and an end date entered.
 Add tasks to your project: The next step is to add tasks to your project.
You can accomplish this by selecting "Add Task" and inputting the task's
information, including its name, duration, and dependencies.
 Assign resources: Assigning resources to tasks is necessary after you've
added them. To accomplish this, select the "Resources" tab and add the
necessary resources to each task.
 Set dependencies: You can set dependencies between activities by
selecting the tasks that must be finished before one activity can begin
on the "Predecessors" page.
 Track progress: Update the status of each job and keep an eye on the
project timeline to track progress as you work on your project.
 Report and analyze: Reporting and analysis tools include Gantt charts,
resource usage, and cost analysis in Oracle Primavera. These tools are
all available for reporting and evaluating project data. These resources
can help you understand the state of your project and spot any
problems or areas for development.

Page 134 of 153

 Career in Oracle Primavera

Professionals with Oracle Primavera experience have a wide range of job

options, including project management positions across numerous industries
and use in project management software firms. Professionals with Oracle
Primavera skills may hold positions such as project manager, planner,
scheduler, and engineer for project control, among others. These experts may
work in a variety of fields, including IT, manufacturing, oil and gas, and
construction. They might be in charge of developing and managing project
schedules, monitoring project progress, examining project data, and informing
stakeholders of project status. Professionals may decide to earn certifications
like the Oracle Primavera Certified Professional or the Oracle Primavera Unifier
Certified Implementation Specialist in order to advance their professions.

Page 135 of 153

 Introduction to Trello

A project management application called Trello is a web-based, kanban-style,

list-making application, that helps teams in prioritising and organising their
work. It is based on the Kanban methodology and represents the work and its
progression using visual boards. Trello boards are made up of cards that stand
in for individual tasks, and these cards can be moved between lists to reflect
the progress of a task. Trello is well-liked for being straightforward and simple to
use, making it a fantastic option for small teams and individual projects.

Page 136 of 153

 Uses, Pros, and Cons of Trello

Teams can organise and prioritise their work using the project management
application Trello. It represents tasks and their progression visually using a board
in the Kanban manner. Here are some uses, benefits, and drawbacks of Trello:
 Uses: Teams use Trello to keep track of and manage their workload, work
together on projects, and communicate with one another. It can be
used in a range of sectors and is appropriate for teams of all sizes.
 Pros: Trello's simplicity and usability, visual user interface, and
connectivity with other programmes like Google Drive and Slack are
some of its benefits. Teams can access and update their work easily
while on the go thanks to Trello's mobile compatibility.
 Cons: Trello's limited capabilities in comparison to more sophisticated
project management systems and the possibility that it may not be
appropriate for large and complex projects are some potential
downsides. Trello is also less customisable than some other project
management systems, making it potentially less ideal for organisations
who must strictly adhere to security and compliance regulations.

Page 137 of 153

 Key Trello Principles and Concepts

Teams can track and manage their work using the visual board structure in
Trello, a project management and organising application. Here are some of
the fundamental ideas behind Trello:
 Cards: Trello represents distinct projects or pieces of work using cards.
These cards, which can also have extra details like attachments,
comments, and checklists, can be moved between lists to demonstrate
progress.
 Lists: Trello groups related cards together by using lists. These lists may
indicate several work phases, including "To Do," "In Progress," and "Done."
 Boards: Trello organises lists and cards using boards. Each board, which
may contain many lists, represents a particular undertaking or area of
works.
 Labels: Trello gives users the option to label cards in order to add more
context or categorization. These labels may be used to denote the
importance or kind of work that the card represents.
 Members: Trello users can invite team members to work together on a
board. Members can be allocated to particular cards to indicate who is
in charge of each task.
 Power-Ups: To improve a board's usefulness, Trello provides a variety of
"power-ups" that can be applied. Integrations with other programmes,
extra features like the calendar view, or personalization choices like
background graphics are some examples of these power-ups.

Page 138 of 153

 Trello Terminologies

Trello is a project management solution that prioritises work using a visual

interface. The following are some essential terms that are used in Trello:
 Boards: Lists and cards arranged on a board to depict a project or
procedure.
 Lists: A list is a vertical column of cards that stand in for tasks or other
objects.
 Cards: A card is a discrete piece of work that includes text, annotations,
attachments, and labels.
 Labels: You can add labels as tags to cards to offer more information or
to indicate categories or priorities.
 Checklists: Lists of items that can be crossed off when they are
accomplished are called checklists.
 Members: People who have been added to a board and have the right
to view and update the board are known as members.
 Power-Ups: A board's functionality can be improved by adding Power-
Ups, which are extra functions.

Page 139 of 153

 Getting started with Trello

 Create account: You must create a account on the Trello website in

order to use the service.
 Create a new board: After completing that, you can start by making
your first board. A Trello board is made up of a number of lists, each of
which has a number of cards on it. Click the "Create a new board"
button in the top right corner of the screen to start a new board. You will
be requested to pick whether you want your board to be public or
private as well as to give it a name. You will then be brought to your new
board after completing that.
 Make lists: The next step is to make some lists. To do this, select "Add a
list" from the list options on the right side of the screen. Your board can
hold as many lists as you like, and you can reorder them by clicking and
dragging.
 Include cards: After making a few lists, you may begin including cards.
To accomplish this, select "Add a card" from a list at the bottom and give
your card a name. To your card, you may also add a description and
attachments.
 Customize: From here, you may add different backgrounds, labels, and
other features to your board to make it your own. Inviting others to join
your board and work alongside you is another option.

Page 140 of 153

 Career in Trello

Trello is a project management and organisation tool that is widely used in

many different industries, therefore it is feasible to make a career out of it. The
following are some probable career pathways in Trello:
 Project manager: The project manager uses Trello to manage projects,
assign tasks, track progress, and communicate with team members.
 Team leader: Team leaders use Trello to manage and organise their
team, assign tasks, and monitor progress.
 Product manager: Project managers use Trello to manage product
development, measure progress, and interact with team members.
 Business analyst: Business analysts use Trello to track projects' progress,
find and fix problems, and interact with stakeholders.
 Consultant: Consultants with Trello experience can provide Trello training
and consulting services to businesses wishing to advance their project
management procedures.

Page 141 of 153

 Introduction to TILOS

A project management tool called TILOS (TIme, LOcation System) assists users
in organising, scheduling, and coordinating challenging tasks. It is frequently
used in the building and infrastructure sectors as well as other industries where
managing large, complex projects is necessary. Users using TILOS can construct
thorough project timetables, monitor development, and spot potential
problems in advance. Additionally, it provides resources for cost tracking, risk
analysis, and resource management. Because TILOS is flexible and adaptable,
customers can customise it to meet their unique project management
requirements.

Page 142 of 153

 Uses, Pros, and Cons of TILOS

A project management tool made exclusively for building and infrastructure

projects is called TILOS. It is used to produce a visual depiction of the project
schedule that shows where each work is to be completed and how long it will
take. TILOS is mostly used for things like:
Uses:
 Planning and scheduling: TILOS gives project managers the ability to
make a thorough plan of all the duties and activities that must be carried
out during the project. This includes allocating resources, establishing
due dates, and figuring out how various tasks are interconnected.
 Visualization: TILOS offers a visual depiction of the project schedule,
making it simpler for team members and project managers to
understand how the project is progressing and spot any problems.
 Collaboration: TILOS provides collaboration capabilities that make it
simpler for team members to work together and share information, such
as project dashboards and communication tools.
Pros:
 Provide a thorough perspective of the project schedule, including
information about the location and length of tasks.
 Enables simple team cooperation and communication.
 Enables real-time monitoring and project progress updates.
Cons:
 Setting it up and using it can be challenging, especially for big projects.
 For new users, there could be a long learning curve.
 Compared to other project management software solutions, it may be
pricey.

Page 143 of 153

 Key TILOS Principles and Concepts

A project management tool called TILOS assists teams in organising and

visualising tasks in a timeline manner. TILOS's main ideas and principles include
the following:
 Time-based planning: TILOS enables teams to schedule projects using a
timeline, with resources and tasks displayed in a linear way. This makes it
easier to see how the job will develop over time and spots dependencies
or conflicts that might arise.
 Resource management: TILOS's resource management feature enables
teams to allocate resources to tasks and monitor their availability and
usage. This promotes efficient resource allocation and ensures timely
and cost-effective project completion.
 Collaboration: TILOS offers capabilities for team collaboration, including
as document and project sharing, progress monitoring, and team
member communication.
 Integration with other software: To import and export data and
synchronise plans, TILOS can be integrated with other project
management tools, such Microsoft Project.
 Customization: TILOS enables teams to tailor the design and presentation
of the project timeline to suit their own requirements. To represent various
jobs or resources, you can add custom fields, make custom reports, and
use various colours and symbols.

Page 144 of 153

 TILOS Terminologies

The terms and expressions used within the TILOS project management software
are referred to as TILOS terminologies. Typical TILOS jargon includes the
following:
 Activity: An activity is a specific task or piece of work that must be
finished as part of a project.
 Resource: A resource is something that is needed to finish a job, such as
a person, piece of machinery, or piece of material.
 Work package: A work package is a certain scope of work that has
been divided up into smaller, more manageable tasks.
 Time axis: The time axis is a graphic representation of the project timeline
that displays the beginning and ending dates of every activity as well as
their connections.
 Gantt chart: A Gantt chart is a kind of bar graph that displays each task's
start and end dates as well as the dependencies between them.
 Network diagram: A network diagram is a graphic representation of a
project's tasks and their interdependencies that demonstrates the flow
of work.
 Critical path: Because they take the longest to complete and have an
impact on the project's overall timing, the critical path is a set of tasks
that must be finished in a specified order.
 Resource histogram: A resource histogram displays the workload of each
resource within the project and provides a visual depiction of resource
use over time.

Page 145 of 153

 Getting started with TILOS

You must set up your project and install the necessary software before you can
begin using TILOS. Here are some actions to take:
 Installing the programme: From the official website, you may download
and set up TILOS on your PC.
 Create your project: After installing TILOS, you may begin creating your
project. This includes making a new project file, entering the information
for your project, and adding any resources or activities you plan to use.
 Establish a schedule: By adding your tasks and resources, establishing
dependencies, and imposing limits, you may use TILOS to construct a
schedule for your project.
 Track progress: Use TILOS to keep track of progress while you work on
your project and adjust the timetable as appropriate.
 Communicate with stakeholders: TILOS offers a variety of tools and
capabilities, including project reports and Gantt charts, that you may
use to communicate with your team and stakeholders.
 Review and analysis: After your project is finished, you may use TILOS to
assess the management of your project and the effectiveness of your
findings. This can assist you in determining any future improvement areas.

Page 146 of 153

 Career in TILOS

TILOS, which stands for Time-Location Planning Software, is a project

management tool that is particularly useful for linear infrastructure projects
such as roads, railways, pipelines, and other construction projects. It combines
the time and location aspects of a project into a single visual representation,
making it easier to plan, execute, and monitor project progress. Here's how
TILOS can help various project management personnel carry out their duties
and grow:
Project Manager:
 Enhanced planning: TILOS allows project managers to create a
comprehensive plan that integrates time and location data, enabling
better decision-making and resource allocation.
 Improved communication: Visual representations in TILOS can help
project managers communicate complex project information to
stakeholders more effectively.
 Progress tracking: TILOS provides tools to track and compare actual
progress against planned progress, allowing project managers to
identify potential delays and take corrective actions.
 Risk management: By identifying potential bottlenecks and risks, TILOS
enables project managers to develop mitigation strategies and
contingency plans.
Team Leader:
 Resource management: TILOS allows team leaders to allocate resources
(such as labor, equipment, and materials) effectively along the project
timeline and location, ensuring optimal utilization.
 Task coordination: Team leaders can use TILOS to coordinate tasks
between team members, providing clear visibility of responsibilities and
deadlines.
 Collaboration: TILOS promotes collaboration among team members by
sharing real-time project information and facilitating communication.
Product Manager:
 Product lifecycle management: TILOS can help product managers
monitor and control product development throughout the project,
ensuring that the end product meets quality and functionality
requirements.
 Integration with other systems: Product managers can integrate TILOS
with other project management and product development tools,
ensuring seamless data flow and efficient communication.
Business Analyst:

Page 147 of 153

  Data analysis: TILOS provides data visualization tools that can help
business analysts identify trends, patterns, and discrepancies, making it
easier to develop insights and recommendations.
 Decision support: By analyzing project data in TILOS, business analysts
can support decision-making processes by providing insights on cost,
schedule, and resource allocation.
Consultant:
 Expert advice: TILOS allows consultants to leverage their expertise in
linear projects and provide valuable recommendations based on the
software's comprehensive planning and analysis capabilities.
 Customization: Consultants can customize TILOS to meet the specific
needs of their clients, creating tailored solutions that address unique
project challenges.
 Training: Consultants can also help project management personnel
learn how to use TILOS effectively, fostering growth in their skills and
capabilities.
By using TILOS, project management personnel can benefit from improved
planning, communication, resource allocation, and risk management,
ultimately leading to better project outcomes and growth in their professional
roles

Page 148 of 153

 The Project Management Institute (PMI)

An international organisation for project management professionals is called

the Project Management Institute (PMI). The leading non-profit professional
membership organisation in the world for project, programme, and portfolio
management is this one. To support its members and the project management
community, PMI offers publications, standards, research, and professional
development.
More than 3 million people worldwide have credentials from PMI, which was
created in 1969. The goal of PMI is to advance project management as a
practice, science, and profession. It accomplishes this by creating project
management standards, such the Project Management Body of Knowledge
(PMBOK), which outlines principles and best practices for managing projects.
Project Management Professional (PMP) and Certified Associate in Project
Management are just two of the project management-related professional
certifications that PMI offers (CAPM). These credentials are regarded as
symbols of excellence in the field of project management and are
acknowledged on a global scale.
Providing professional development, standards, research, and publications to
assist advance the practice and profession of project management, PMI is a
valuable resource for anyone working in the field of project management.

Page 149 of 153

 Project Management Body of Knowledge (PMBOK)

The Project Management Institute (PMI) created a manual called The Project
Management Body of Knowledge (PMBOK) that lists principles and best
practices for managing projects. The PMBOK is widely regarded as a standard
in the project management industry and is built on the pooled experiences
and expertise of PMI members.
There are nine knowledge areas in the PMBOK:
 Project integration management: This subject area deals with the
procedures necessary to make sure that all of the project's components
are correctly coordinated.
 Project scope management: This subject area deals with the procedures
required to specify and regulate the project's scope.
 Project time management: Planning, scheduling, and controlling the
project timetable are all covered in this knowledge area on project time
management.
 Project cost management: The procedures required to plan, estimate,
budget for, and control project costs are covered in this knowledge
area.
 Project quality management: This subject area includes the procedures
required to ensure that the project satisfies the necessary standard of
quality.
 Project resource management: The procedures required to recruit, train,
and oversee the project team are covered in this knowledge area.
 Project communication management: This knowledge area addresses
the procedures required to ensure successful communication among
project team members and with stakeholders.
 Project risk management: This subject area deals with the procedures
required to recognise, evaluate, and deal with project risks.
 Project procurement management: The procedures required to get
goods and services from outside providers are covered in this
knowledge area.
Periodically, the PMBOK is updated to reflect the most recent best practices in
project management. It is frequently a necessary resource for the professional
certifications offered by PMI and is commonly used as a reference by project
management experts.

Page 150 of 153

 PMP Certification

The Project Management Institute (PMI) offers the Project Management

Professional (PMP) certification, a widely regarded professional project
management credential (PMI). The PMP certification acknowledges
knowledge and abilities that have been shown in leading and managing
project teams and completing projects within the parameters of schedule,
money, and resources.
For someone to be qualified for the PMP certification, they must:
 A secondary education (high school diploma, associate's degree, or its
equivalent in a different country)
 7,500 hours spent managing and overseeing projects, at least 5 years of
experience in project management, and 35 hours of project
management training
An individual can additionally qualify for the PMP certification by:
 Four years of education
 A minimum of three years of experience in project management, 4,500
hours spent leading and overseeing projects, and 35 hours of formal
project management training
An individual must pass the PMP exam, a multiple-choice test with 200
questions, in order to obtain the PMP certification. These topics are covered by
the exam:
 Start of the project (13 percent )
 Creating a project plan (24 percent )
 Carrying out the project (31 percent )
 Keeping an eye on and managing the project (25 percent )
 The project's completion (7 percent )
The three-year validity of the PMP certification: An individual must accumulate
60 professional development units (PDUs) during that time in order to keep their
certification active.
Users frequently prefer or demand the PMP certification since it is widely
regarded as a symbol of expertise in the field of project management. In the
area of project management, it may also result in more work options and
higher pay.

Page 151 of 153

 CAPM Certification

The Project Management Institute offers a professional certification called

Certified Associate in Project Management (CAPM) (PMI). The CAPM is made
for people who are brand-new to project management and wish to show that
they understand the essential concepts, terms, and procedures of efficient
project management.
For someone to be qualified for the CAPM certification, they must:
 Secondary education (high school diploma, associate's degree, or
country-specific equivalent)
 Alternatively, a person can qualify for the CAPM certification by
completing the following: 23 hours of project management training
 A person must pass the 150-question CAPM test with multiple-choice
answers in order to receive the CAPM certification. The Project
Management Body of Knowledge (PMBOK), a publication by PMI that
offers standards and best practices for project management, is covered
in the exam.
The five-year validity of the CAPM certification: An individual must accumulate
15 professional development units (PDUs) during that time in order to keep their
certification active.
For those who are new to project management and wish to show that they
have a solid grasp of the principles of the field, the CAPM certification is an
entry-level credential. The Project Management Professional (PMP) credential,
a more advanced qualification for seasoned project management
professionals, is frequently a stepping stone to this one.

Page 152 of 153

 P3O Certification

The Office of Government Commerce (OGC) in the United Kingdom provides

the Portfolio, Programme, and Project Offices (P3O) certification. The portfolio,
programme, and project management offices (PMOs) inside a company must
be established and maintained by people who hold the P3O certification.
There are three stages of P3O certification:
 P3O Foundation: The P3O Foundation level is created for people who are
unfamiliar with PMOs and who wish to learn the fundamentals and
procedures of efficient PMO management.
 P3O Practitioner: The P3O Practitioner level is intended for people who
are in charge of running a PMO on a daily basis and want to show off
their expertise in this field.
 P3O Advanced Practitioner: This level is intended for people who are in
charge of creating and maintaining PMOs and who want to show off
their advanced knowledge and expertise in this field.
A person must pass the P3O Foundation exam, a multiple-choice test with 40
questions, in order to achieve the P3O Foundation level certification. A person
must pass the P3O Practitioner exam, a multiple-choice test with 40 questions,
in order to achieve the P3O Practitioner level certification. An individual must
pass both the P3O Foundation and Practitioner tests in addition to finishing a
practical assignment in order to receive the P3O Advanced Practitioner level
certification.
The three-year validity of the P3O certification: A person must accumulate 35
professional development units (PDUs) during that time in order to keep their
certification active.
The P3O certification is frequently needed or requested by companies as a
symbol of competence in the PMO management industry. Additionally, it may
result in more career prospects and higher pay in this industry.

Page 153 of 153