Introductionto Project Management
Introductionto Project Management
TO PROJECT
MANAGEMENT
COURSE WRITERS
Mr. Manoj Y. Parab, PMP Mr. Ramesh Pattnaik, PMP
EDITOR
Mr. Yogesh Bhosle
Acknowledgement
Every attempt has been made to trace the copyright holders of materials reproduced in this book. Should any
infringement have occurred, SCDL apologises for the same and will be pleased to make necessary corrections
in future editions of this book.
PREFACE
We are glad to write this SLM on “Project Management” for the students of SCDL. With economic
growth and globalization, the businesses are expanding. This results in new projects as well as expansion
of projects being undertaken by the industry and infrastructure projects being implemented by the
Government. The growth in software industry requiring implementation of software projects and ever
used market research projects has resulted in increasing the demand for project managers. In fact,
project management is required in every facet of life; right from construction of house to completion
of education, at each step, we are required to do project management. If done in a systematic manner,
the probability of success of project improves and results can be better. To manage these projects, the
Finally, our heartfelt thanks to our parents for their valuable encouragement and inspiration. Last but
their entertainment and outings during the time the SLM was being written. Thanks to all those, who
directly or indirectly helped us in completing our work.
iii
ABOUT THE AUTHORS
(ID) from IICA (India), Internal Auditor from Broad beach (UK), having Analytical thinking and
decision making ability in Digital Technology and Complex business environment. He is having
He worked for Service, IT, Marine, Shipping, Education &Training, Real estate, and NGOs having
expertise of Strategic Planning, Stakeholder Management, Management of Multiple & Complex
Microsoft Project, Primavera P6, Since 2011. He has completed Coaching and Training for 150 plus
He has Undertaken projects in Software Designing, Process Mapping, Business process Reengineering,
Company SMS Preparation, Classroom Training on project management to Government Trainees,
Seminar Coaching to Pvt. Co. on Project Management.
His Software Expertise are project management & PMS like MS Project, Primavera P6, JIRA, Marine
positions as project director, Additional director, project Head, Technical manager, Regional Manager,
He worked for Service, IT, Marine, Shipping, Education &Training, Real estate, and NGOs having
expertise of Strategic Planning, Stakeholder Management, Management of Multiple & Complex
Microsoft Project, Primavera P6, Since 2011. He has completed Coaching and Training for 150 plus
He has Undertaken projects in Software Designing, Process Mapping, Business process Reengineering,
Company SMS Preparation, Classroom Training on project management to Government Trainees,
Seminar Coaching to Pvt. Co. on Project Management.
His Software Expertise are project management & PMS like MS Project, Primavera P6, JIRA, Marine
iv
CONTENTS
Unit No. TITLE Page No.
1 Project Management: Genesis, History & Evolution 1-26
1.1 Overview
1.2 Genesis and History
1.3 Types & Approach
1.4 Needs
1.5 Applications & Industry
Summary
Keywords
Self-Assessment Questions
Answers to Check your Progress
Suggested Reading
2 Project Phases and Organization 27-54
2.1 Overview
2.2 Initiation
2.3 Planning
2.4 Execution
2.5 Monitoring & Control
2.6 Closing
2.7 Organizational Theory
Summary
Keywords
Self-Assessment Questions
Answers to Check your Progress
Suggested Reading
3 Understanding and Meeting Client Expectations 55-76
3.1 Clients Importance and Expectations
3.2 Client Meeting & Project Requirements
3.3 Client Approval on Project Requirements
3.4 Acceptable Delivarables
3.5 Clinent Satisfactions
Summary
Keywords
Self-Assessment Questions
Answers to Check your Progress
Suggested Reading
v
Unit No. TITLE Page No.
4 Project Planning 77-104
4.1 Start Milestone & Project Planning
4.2 Feasibility Study
4.3 Requirements Gathering
4.4 Preparation of Project Plan
4.5 Change Request & Client Approved Project Plan
Summary
Keywords
Self-Assessment Questions
Answers to Check your Progress
Suggested Reading
5 Working with People on Projects 105-126
5.1 Human Resources Plan
5.2 Accquring Project Team
5.3 Developing Project Environments
5.4 Managing Project Team
5.5 Human Resources Motiventional Theroy
Summary
Keywords
Self-Assessment Questions
Answers to Check your Progress
Suggested Reading
6 Networks for Project Management 127-146
6.1 Networking Concents
6.2 Introduction to pert Calculations
6.3 Development of Network Diagram
6.4 Introduction Critical Path Methods (CPM)
6.5 Advantages and Applications of CPM
Summary
Keywords
Self-Assessment Questions
Answers to Check your Progress
Suggested Reading
7 Resource Levelling and Project Crashing 147-166
7.1 Project Schedule
7.2 Critial Path
7.3 Resource Assignments
7.4 Schedule Management Techniques
7.5 Resource Levelling
7.6 Project Crashing
Summary
Keywords
Self-Assessment Questions
Answers to Check your Progress
Suggested Reading
vi
Unit No. TITLE Page No.
8 Project Implementation and Monitoring 167-190
8.1 Approved Project Documents
8.2 Project Executions
8.3 Project Monitoring
8.4 Project Updates & Monitoring Tools
Summary
Keywords
Self-Assessment Questions
Answers to Check your Progress
Suggested Reading
9 Controlling Projects 191-216
9.1 Project Progress
9.2 Montioring Tools & Techniques
vii
Unit No. TITLE Page No.
11 Focused Areas From PMBOK 6 & 7 241-274
11.1 Project Life Cylce - EEF & OPA
11.2 Project Scope Management
11.3 Project Schedule Management
11.4 Project Cost Management
11.5 Project Quality Management
11.6 Project Resource Management
11.7 Project Communication Management
11.8 Project Risk Management
11.9 Project Procurement Management
11.10 Project Stakeholder Management
Summary
Keywords
Self-Assessment Questions
Answers to Check your Progress
Suggested Reading
12 Introduction of Other Useful Frameworks 275-293
12.1 Agile Project Management
12.2 Scrum Proect Management
12.3 Kanban Framework
12.4 Lean Methodology
12.5 Critical Chain Project Management (CCPM)
Summary
Keywords
Self-Assessment Questions
Answers to Check your Progress
Suggested Reading
viii
ix
x
Project Management: Genesis, History & Evolution
UNIT
1
Structure:
1.1 Overview
1.2 Genesis and History
1.3 Types & Approach
1.4 Needs
1.5 Applications & Industry
Summary
Keywords
Self-Assessment Questions
Answers to Check your Progress
Suggested Reading
1.1 OVERVIEW
Project Management is the process of leading the work of a team to
achieve all project goals within the given constraints. The primary constraints
are scope, time, and budget the secondary challenge is to optimize the allocation
2
This information is usually described in project documentation, created
at the beginning of the development process. The objective of project
management is to produce a complete project which complies with the client’s
objectives.
In many cases, the objective of project management is also to shape or
reform the client’s brief to feasibly address the client’s objectives.
A project is a temporary and unique endeavour designed to produce a product,
3
Project planning (Project)
a. Create WBS
WBS
b. Estimate Activity Duration
c. Estimate Activity Budget
An activity is typically one stage of a project management plan. Each
activity consists of one or more actions that, upon completion, will lead to the
4
Stakeholders: Who are the major players who have an interest in this project?
Project manager: Who is going to make sure everything that needs to be
completed gets completed?
Activity 1
5
Till 19th century, all engineering projects were generally managed by
creative architects, engineers, and master builders themselves, In the 1950s,
organizations started to systematically apply project-management tools and
techniques to complex engineering projects.
While it all started with large projects such as the Great Pyramids of Giza,
the Great Wall of China, and the Transcontinental Railroad, we step into what
project management is today with Henry Gantt and the Gantt Chart in the 1910s.
It was and to many still is the quintessential tool of project management
that changed the way we perform and manage all of our tasks. After this, it
took almost another 50 years for Bernard Schriever to coin the term ‘Project
management’ in 1954, and from then on, we got moving.
While today most of us are familiar with the term ‘Project Management,’
each task and the minimum time needed to complete the whole project.
1965 marked the founding of the International Project Management
Association (IPMA). It started as a way for Pierre Koch of France, Dick
Vullinghs from the Netherlands, and Roland Gutsch from Germany to
people or customers.
Reliance Industries Limited is amongst the fortune 500 companies and
the largest business house in India. For two consecutive years, Reliance has
been amongst the top 25 fastest growing companies in the world. Some of the
projects by Reliance which show their project management abilities to the world
etc. The scale of the project has always been the focal point for the company.
It is always a prime consideration for all of their projects, but was never run
on a project management basis. Duplicity and a lack of systematic tracking
resulted in a lot of redundant applications and issues of quality. Project delays,
7
More important to manage all projects in a systematic manner with real time
information on progress available at any given time. IT teams started with labour
intensive manual processes and Excel sheet based practices initially. However,
of projects and associated issues itself became an issue for the company.
sector. For example, the construction industry, which focuses on the delivery
of things like buildings, roads, and bridges, has developed its own specialized
form of project management that it refers to as construction project management
8
Biotechnology project management focuses on the intricacies of
biotechnology research and development. Localization project management
includes application of many standard project management practices to
translation works even though many consider this type of management to be a
There is public project management that covers all public works by the
government, which can be carried out by the government agencies or contracted
This allows project plans to become very thorough and highly repeatable, with
9
Aim & Expectations: What are the aims & expectations of the project.
Plan: The planning and forecasting activities.
Process: The overall approach to all activities and project governance.
People: Including dynamics of how they collaborate and communicate.
Power: Lines of authority, decision-makers, policies for implementation
and the like.
Traditional project management is an approach executed in a linear
sequence. The basic model includes initiation, planning, execution, monitoring,
project outcomes in terms of requirements, but Meredith and Mantel also added
a fourth aspect of project management— the expectations of the client.
10
This study portrays a knowledge base and may be helpful in improving
as the waterfall methodology the traditional method for managing projects and
the one that is simplest to understand.
Have to complete one task before the next one begins in a connected
sequence of items that add up to the overall deliverable. It’s an ideal method
for projects that result in physical objects (buildings, computers), and you can
easily replicate project plans for future use.
The power of this methodology is that every step is pre-planned and
laid out in the proper sequence. While this may be the simplest method to
implement initially, any changes in stakeholders’ needs or priorities will disrupt
bottlenecks and delays. The goal is to do more with less — to deliver value to
the customer using less manpower, less money, and less time.
11
Check your Progress 3
1.4 NEEDS
organisation.
12
Fig. 7: Needs of Project Management Professionals
A social organisation, such as a hospital, may build a new wing, introduce
a new service, or design new work processes to reduce costs. A government
organisation may introduce a new software program that handles public records
to reduce costs.
management, projects are handled best by people who are trained in project
management. This expertise can be obtained by hiring an outside consulting
13
build a sales system that doesn’t integrate with your sales process and sales
organization. It wouldn’t add much value. Integration is often key to project
Controls cost
so on budget performance is essential. Using project management strategies
greatly reduces the risk of budget overruns.
Manages change – projects always happen in an environment in which
nothing is constant except change. Managing change is a complex and daunting
task. It is not optional. Project management manages change.
Managing quality – It’s the value of what you produce. Project
volume in last few years in India, the work is still highly labour intensive with
low level of training to workers, poor labour welfare programs and facilities,
lack of proper environment health & safety regulations resulting in many
accidents and injuries to workers during development.
Project management on the other hand also helps in this case by bringing
adequate balance between men & machinery, proper induction and training of
workers and safe work practices through work method statements ensuring safe
working environment on projects.
14
Check your Progress 4
15
Project Management can provide the much-wanted structure to the
construction sector and with the help of this structure, the industry should be
able to overcome the associated problems on scope, time, budget, stakeholders,
teams, communications, and risk and be better prepared for future challenges.
“India will require 70 lakh new project managers in next 10 years. India
will emerge as the fastest growing country in the world for project management-
oriented employment,” according to Project Management Institute’s (PMI)
report - Project Management Job Growth and Talent Gap 2017-2027.
work included all activities associated with reducing the use of fossil fuels and
reliance on imported energy.
16
Development of each of the major components became a project for the
that the success or failure of one of their other job responsibilities would.
Therefore, project managers create clear goals and clear expectations for
team members and tie project success to the overall success of the organisation.
Project managers are goal directed and milestone oriented.
While there are, many skills needed by a project manager that are the
same as an operations manager, because project managers generally operate
in an environment that is more time sensitive and goal driven, the successful
project manager requires additional knowledge, skills, and abilities.
17
Fig. 8: Project Management Applications
insurance.
Activity 2
that maximizes the use of organisational resources and provides the greatest
return to the organisation.
rather than products or outputs and then measuring the degree to which that is
happening to keep a project on track.
This can help to reduce the risk of a completed project being a failure by
delivering agreed upon requirements (outputs) i.e. project success but failing to
requirements of the project and their achievement monitored throughout the project.
In addition, BRM practices aim to ensure the strategic alignment between
project outcomes and business strategies.
19
Most projects big or small, have their own share of Risks which are
advantage. There are many tools and techniques available to manage schedules,
much of it connected to overall project planning and sequencing of activities.
Project Managers emphasize on resource based scheduling to enable
planning of realistic timelines to projects making it easier to also understand
the factors driving success of deadlines.
Project Implementation
20
The components in an implementation plan include:
accomplished, who will be impacted, and how the plan will improve
Summary
Project Management is the process of leading the work of a team to
achieve all project goals within the given constraints. The primary
constraints are scope, time, and budget the secondary challenge is to
optimize the allocation of necessary inputs and apply them to meet pre-
21
1970 brought the Waterfall method by Winston W. Royce. Instead of
looking at the project as a whole, it was divided into stages that should
Controls cost
on budget performance is essential. Using project management strategies
greatly reduces the risk of budget overruns.
Manages change – projects always happen in an environment in which
nothing is constant except change. Managing change is a complex and
daunting task. It is not optional. Project management manages change.
Managing quality–it is the value of what you produce. Project
Allocation of resources.
Planning milestone.
Designation of responsibilities.
Keywords
Project management: The practice of planning, executing, and
23
Waterfall model: A traditional project management approach that
follows a linear sequence of phases, with each phase building upon
the previous one.
Agile methodology: A project management approach that emphasizes
Self-Assessment Questions
1. Write Small paragraph in which you describe each area of project
management & its Applications
a Operation?
3. How you describe Project, WBS and Activity in Project Management
4. Describe history of Project Management in brief?
24
Check your Progress 3
Fill in the blanks.
1. ‘a set of techniques and tools that
2. streamlining and cutting out waste.
identify and eliminate bottlenecks and delays
Suggested Reading
1. Project Management Institute, Inc., A Guide to the Project Management
Body of Knowledge (PMBOK Guide), 4th Ed. (Newtown Square, PA:
Project Management Institute, Inc., 2008), 6.
2. Jack R. Meredith and Samuel J. Mantel, Jr., Project Management: A
Managerial Approach (Hoboken, Nj: Wiley, 2006), 8.
3. Russell W. Darnall, The World’s Greatest Project (Newtown Square, PA:
Project Management Institute, Inc., 1996), 48–54
4. An Introduction to the History of Project Management: from the Earliest
Time to ad 1900 by Y. C. Chiu, Netherlands, Eburon Academic Publishers.
5. Introduction to Project Management by Kathy Schwalbe, Thomson
Course Technology, 2006.
6. Project Management by K. Nagarajan, New Age International (P) Limited.
7. Project Management Absolute Beginner’s Guide (4th Edition)” by Greg
Horine
8. The Art of Project Management” by Scott Berkun.
25
26
Project Phases and Organization
UNIT
2
Structure:
2.1. Overview
2.2. Initiation
2.3. Planning
2.4. Execution
2.5. Monitoring & Control
2.6. Closing
2.7. Organizational Theory
Summary
Keywords
Self-Assessment Questions
Answers to Check your Progress
Suggested Reading
2.1 OVERVIEW
Project management is often done in phases to improve control and quality.
This means a large project is broken down into more manageable stages, each
28
Projects vs. Operations
a hybrid. The initial design and marketing of these three models are unique
projects. However, the actual assembly of the cars is considered an operation—a
repetitive process that is followed for most makes and models.
Project Characteristics
Projects are unique.
date.
Projects are completed when the project goals are achieved or it’s
determined the
Project is no longer viable.
A successful project is one that meets the expectations of your
stakeholders.
Projects initiate change in the organization.
Projects bring about business value creation.
A phase represents a grouping of similar activities that has a very loosely
phase is essentially complete before the beginning of the next phase; however,
phases do not have clear-cut end dates and some activities in an early phase of
the project will continue into the later phases.
This is in contrast to project beginning and ending dates and milestone
will be met.
29
Project life cycle in project management
The project life cycle refers to the various stages that a project goes
through from its inception to its completion. These stages typically include
initiation, planning, execution, monitoring and control, and closure. The project
life cycle provides a structured approach to managing projects and helps ensure
that projects are completed on time, within budget, and with the desired quality.
Initiation:
project’s goals, objectives, scope, and stakeholders. The feasibility of the project
is also assessed during this stage to determine if it is viable and worth pursuing.
Planning: In this stage, the project is thoroughly planned, including
the project.
A detailed project plan is developed, which includes a work breakdown
structure (WBS), a project schedule, a budget, and a risk management plan.
The project team is assembled, roles and responsibilities are assigned, and
communication channels are established.
Execution: Once the planning is complete, the project moves into the
execution stage. This is where the project plan is put into action, and the project
team starts working on the project tasks according to the schedule and budget.
The project manager monitors the progress of the project, manages risks,
and communicates with stakeholders. Regular progress reports are generated to
track the project’s status and ensure that it is on track.
Monitoring and Control: In this stage, the project progress is continuously
monitored and compared against the project plan to identify any deviations. If
there are any issues or risks that arise during the project, they are addressed and
mitigated. The project manager ensures that the project stays on track and takes
corrective action if necessary.
This stage involves ongoing monitoring, controlling, and reporting on the
project’s performance to ensure that it meets its objectives.
Closure: Once the project is completed, it moves into the closure stage.
deliverables have been met, and the project has achieved its goals and objectives.
A project closure report is generated, which documents the lessons learned, the
successes, and challenges faced during the project. The project is closed, and a
post-project evaluation is conducted to analyse the project’s performance and
identify areas for improvement in future projects.
It’s important to note that the length and complexity of each stage may
vary depending on the size, scope, and nature of the project.
The project life cycle provides a framework for managing projects
30
intended goals and objectives. It also helps in identifying and addressing issues
and risks that may arise during the project, and provides a structured approach
to project management.
Overall, understanding and following the project life cycle is critical for
successful project management. So, it’s important to plan, execute, monitor, and
close projects in a systematic manner to increase the chances of project success.
Each stage in the project life cycle requires careful planning, execution,
and monitoring to ensure that the project is completed successfully and meets
its intended goals and objectives.
The project life cycle serves as a guide for project managers and teams to
31
Activity 1
2.2 INITIATION
This phase of project management marks the beginning of the project and
All the activities necessary to begin planning the project. The initiation
phase typically begins with the assignment of the project manager and ends
identifying the project team, developing the resources needed to develop the
project plan, and identifying and acquiring the project management infrastructure
(space, computers).
the project team will invest time and resources in developing a clearer scope
of work. On projects where the major project stakeholders are not aligned,
the project team will expend resources and time creating stakeholder
alignment.
Unlike project milestones, some activities associated with project
initiation may be delayed without delaying the end of the project. For example,
it is advantageous for the project to have the major project stakeholders
it, and get it approved. During this time, the project manager may do any of the
following:
Perform a feasibility study
Create a project charter
Identify key stakeholders
Select project management tools
By the end of this phase, the project manager should have a high-level
understanding of the project’s purpose, goals, requirements, and risks.
32
Models that look at costs and revenues
Payback period
33
Output of Initiation process will be approved project Management plan
for Entire Project.
High Level Requiremen
Stakeholder Register
High level Project Budget
Project Estimated Time line
2.3 PLANNING
This is where the project plan is developed. That means costs are estimated,
resources are determined, and requirements (scope and work breakdown
34
where the project manager outlines the project objectives to all stakeholders
involved. Before that meeting happens, it is crucial for the project manager to
do the following:
Establish goals and deliverables
Identify your team members and assign tasks
Develop a draft project plan
35
Fig. 5: Example of PMIS
2.4 EXECUTION
This project phase is where the project is carried out, all while procuring
resources and managing stakeholder expectations.
The execution phase, labelled by PMI as “carrying out the work,”
includes the major activities needed to accomplish the work of the project. On a
construction project, this would include the design and construction activities.
On an information technology (IT) project, this would include the
development of the software code. On a training project, this would include the
development and delivery of the training.
This stage is where the bulk of the project happens. Deliverables are built
to make sure the project is meeting requirements. This is where most of the
time, money, and people are pulled into the project.
like this:
Introductions: Who’s who?
Project background: Why are you doing this project? What are the goals?
36
Project scope: What kind of work is involved?
Project plan: What does the roadmap look like?
Roles: Who will be responsible for which elements of the project?
Communication: What kind of communication channels will be used?
What kind of meetings or status reports should your team expect?
Tools: Which tools will be used to complete the project, and how will
they be used?
Next steps: What are the immediate action items that need to be
completed?
Performance Domain (Executing)
Acquire and manage project resources by following the human resource
and procurement management plans in order to meet project requirements.
Manage task execution based on the project management plan by leading
and developing the project team in order to achieve project deliverables.
Implement the quality management plan using the appropriate tools and
techniques in order to ensure that work is performed in accordance with
required quality standards.
Implement approved changes and corrective actions by following the
change management plan in order to meet project requirements.
Implement approved actions by following the risk management plan
in order to minimize the impact of the risks and take advantage of
opportunities on the project.
37
The project management plan documents the goals of the project and the
actual work you and the team will execute in order to meet those goals. Once
the project management plan is complete, you will know all of the work and
actions needed to meet the deliverables of the project and will have a plan for
executing those actions.
Most components of the project management come into play in this process.
The project documents listed as inputs to this process will assist in determining
when resources are needed, milestone due dates, what changes may impact the
work already completed or soon to be performed, and the project communications
Tools and Techniques of Direct and Manage Project Work
The tools and techniques of the Direct and Manage Project Work process
are expert judgment, project management information system, and meetings.
Experts should have experience or knowledge of cost and budget management,
procurement processes, regulations that impact your industry, and legal processes.
Project Management Information System
The project management information system (PMIS) is an automated
system used to document the project management plan and subsidiary plans, to
facilitate the feedback process, and to revise the documents. It incorporates the
38
result, or service set out to produce), work performance data, issue log, and
change requests.
39
Monitor and assess risk by determining whether exposure has changed
2.6 CLOSING
is given to the customer, stakeholders are told of the completion of the project,
and all resources are released back to their resource managers.
40
The closeout phase-or using PMI’s nomenclature, “closing of the project”-
The project client takes control of the product of the project, and the
The amount of resources and the skills needed to implement each phase
The closing phase is a critical step in the project management life cycle. It
41
Obtain feedback from relevant stakeholders using appropriate tools and
techniques and based on the stakeholder management plan in order to
evaluate their satisfaction.
the preferences of the project manager, the knowledge and skills of the team,
42
On a larger, more complex project, the art director may establish area
team leaders and have the art leads for each area report to an area art lead. If the
cities working on the project, then structuring the art function by area provides
better coordination and control.
Most projects have similar functions that are important to successfully
manage the project. Included among these are the following:
Sponsor
Project manager
Controls
Procurement
Technical management
Quality
Administration
On smaller projects, more than one function can be managed by one
person. On larger projects, large teams may be needed to accomplish the work
within the function.
Organizational Project Management
Organizational project management (OPM) ensures that projects,
programs, and portfolios are aligned and managed according to the organization’s
strategic business objectives.
It optimizes the organization’s capabilities by correlating projects,
goals.
The focus of OPM is to ensure that the organization performs the right
projects, that critical resources are available and assigned appropriately, and
43
Providing an established project management methodology, including
templates, forms, and standards
Mentoring, coaching, and training project managers
Facilitating communication within and across projects
Managing resources
Not all PMOs are the same. Some PMOs may have a great deal of authority
and control, whereas others may only serve a supporting role.
According to the PMBOK ® Guide , there are three types of PMOs:
supportive, controlling, and directive.
Functional Organizations
One common type of organization is the functional organization. Chances
are you have worked in this type of organization. This is probably the oldest
style of organization and is, therefore, known as the traditional approach to
organizing businesses.
Functional organizations are centred on specialties and grouped by
function, which is why they’re called functional organizations.
As an example, the organization might have a human resources department,
is specialized and requires people who have the skill sets and experience in these
personnel report to managers who report to vice presidents who report to the
44
CEO. In other words, each employee reports to only one manager; ultimately,
one person at the top is in charge.
Many companies today, as well as governmental agencies, are structured
in a hierarchical fashion. In organizations like this, be aware of the chain of
command.
Each department or group in a functional organization is managed
independently and has a limited span of control. Marketing doesn’t run the
needed information and then pass it back down to the project team.
Human Resources in a Functional Organization
Commonalities exist among the personnel assigned to the various
departments in a functional organization. In theory, people with similar skills
and experiences are easier to manage as a group. Instead of scattering them
together.
Work assignments are easily distributed to those who are best suited for
the task when everyone with the same skill works together.
Workers in functional organizations specialize in an area of expertise
their specialty.
People in a functional organization can see a clear upward career path.
An assistant budget analyst might be promoted to a budget analyst and then
eventually to a department manager over many budget analysts.
The Downside of Functional Organizations
Functional organizations have their disadvantages.
One of the greatest disadvantages for the project manager is that they
have little to no formal authority. This does not mean project managers in
functional organizations are doomed to failure. Many projects are undertaken
and successfully completed within this type of organization.
of the project manager are required to bring about a successful project under
this structure.
In a functional organization, the vice president or senior department
manager is usually the one responsible for projects. The title of project manager
denotes authority, and in a functional structure, that authority rests with the
Senior Management.
45
Managing Projects in a Functional Organization
Projects are typically undertaken in a divided approach in a functional
organization.
For example, the marketing department will work on its portion of the
to work together at the same time on various aspects of the project. Project team
members in this structure will more than likely remain loyal to their functional
managers.
The functional manager is responsible for their performance reviews, and
their career opportunities lie within the functional department—not within the
project team.
Exhibiting leadership skills by forming a common vision regarding the
project and the ability to motivate people to work toward that vision are great
skills to exercise in this situation.
It takes great skill and diplomatic abilities to keep projects on track and
functioning smoothly.
Project managers have little authority in functional organizations, but
with the right skills, they can successfully accomplish many projects.
Highlights the advantages and disadvantages of Functional organizations
Table 1 Advantage & Disadvantages of Functional Organization
Advantages Disadvantages
There is an enduring organizational structure Project managers have little to no formal
authority
Here is a clear career path with separation of
function
Multiple projects compete for limited Employees have one supervisor with a clear
resources and priority chain of command.
Project team members are loyal to the
functional manager.
Project-Oriented Organizations
Project-oriented organizations are nearly the opposite of functional
organizations. The focus of this type of organization is the project itself. The
idea behind a project-oriented organization is to develop loyalty to the project,
not to a functional manager.
46
Fig. 8: Project Oriented Organization
Organizational resources are dedicated to projects and project work in
purely project oriented organizations.
Project managers almost always have ultimate authority over the project
in this structure and report directly to the CEO.
In a purely project-oriented organization, supporting functions such as
human resources and accounting might report directly to the project manager
as well. Project managers are responsible for making decisions regarding the
project and acquiring and assigning resources.
They have the authority to choose and assign resources from other areas
in the organization or to hire them from outside if needed.
For example, if there isn’t enough money in the budget to hire additional
resources, the project manager will have to come up with alternatives to solve
this problem.
This is known as a constraint. Project managers in all organizational
structures are limited by constraints such as scope, schedule, and cost (or
budget).
47
resource utilization.
If you have a situation where you need a highly specialized skill at certain
times throughout the project, the resource you’re using to perform this function
might be idle during other times in the project.
In summary, can identify project-oriented organizations in several ways:
Project managers have high to ultimate authority over the project.
The focus of the organization is the project.
The organization’s resources are focused on projects and project work.
Team members are collocated.
Loyalties are formed to the project, not to a functional manager.
Project teams are dissolved at the conclusion of the project.
Matrix Organizations
and take advantage of, the strengths and weaknesses of functional and project-
oriented organizations.
The idea at play here is that the best of both organizational structures can
be realized by combining them into one.
48
up resources to work on projects. If the project manager is counting on a certain
employee to work on the project at a certain time, the project manager should
determine their availability up front with the functional manager.
49
Check your Progress 7
Summary
Project Phases: Project phases are a series of steps or stages that a project
goes through from initiation to closure. Here are the typical project phases:
Initiation Phase: This phase involves identifying the project goals,
stakeholders, and determining whether the project is feasible.
Planning Phase:
creating a detailed project plan, and identifying the resources required to
execute the project.
Execution Phase: This phase involves carrying out the project plan,
monitoring progress, and making adjustments as necessary.
Monitoring and Controlling Phase: This phase involves tracking
the project progress, measuring performance, and making changes as
necessary.
Closure Phase: This phase involves completing the project, delivering
of the organization.
50
Keywords
Project Management: The practice of planning, executing, and
Project Initiation:
project is assessed.
Project Planning: The phase where the project team develops a roadmap
the project.
Organizational Structure: The way an organization is arranged to carry
out its activities, including how tasks are divided, how departments are
Self-Assessment Questions
1. What is the main goal of the Execution phase of a project?
2. What is the purpose of the Monitoring and Controlling phase of a project?
51
Answers to Check your Progress
Check your Progress 1
Fill in the blanks.
2. high-level understanding
52
Suggested Reading
1. Project Management Institute, Inc., A Guide to the Project Management
Body of Knowledge (PMBOK Guide), 4th Ed. (Newtown Square, PA:
Project Management Institute, Inc., 2008), 6.
2. Jack R. Meredith and Samuel J. Mantel, Jr., Project Management: A
Managerial Approach (Hoboken, Nj: Wiley, 2006), 8.
3. Russell W. Darnall, The World’s Greatest Project (Newtown Square, PA:
Project Management Institute, Inc., 1996), 48–54
4. An Introduction to the History of Project Management: from the Earliest
Time to ad 1900 by Y. C. Chiu, Netherlands, Eburon Academic Publishers.
5. Introduction To Project Management by Kathy Schwalbe, Thomson
Course Technology, 2006.
6. Project Management by K. Nagarajan, New Age International (P) Limited.
7. Project Management Absolute Beginner’s Guide (4th Edition)” by Greg
Horine
8. The Art of Project Management” by Scott Berkun.
53
54
Understanding and Meeting Client Expectations
UNIT
3
Structure:
project.
The ability of a project manager to understand the expectations of the
various stakeholders and motivate them to contribute to project success is a
major aspect of the project manager’s leadership role.
In this unit, we will explore the concepts and skills needed by the project
manager to understand and meet the expectations of one of the most important
stakeholders-the client-and the various means and methods for motivating the
client to contribute to project success.
and it also includes understanding and meeting the expectations of the client.
Depending on the complexity level of the project, the plan to meet the
client’s expectations can range from having a general discussion with the project
leadership team to developing a formal plan that is tracked during the life of the
project.
56
Educate the Client from the Beginning
Often the client does not have project management experience and,
therefore, does not understand project phases and the requirements of the
explaining what to expect and planning with the client a process to minimize
the impact of these changes, the project manager prepares the client for these
events and reduces the frustration.
Customer expectations
Generally, customer expectations are a set of ideas about a product,
service or a brand that a customer holds in their mind.
For example, customers that buy an Apple iPhone over another phone
brand have a set of expectations about that product. For example, they expect to
see that the Apple phone has a sliding lock function, a ‘slate-style’ that has few
to no physical buttons, with ‘Face ID’ facial recognition as standard.
with the customer service and with their purchase. They’ll also have expectations
that aren’t so easy to see. Can deliver against these tangible and intangible
expectations.
Customers’ expectations are dynamic to business
Knowing your customer’s expectations is important to all businesses -
whether you’re a small business or a large enterprise organization.
into improving their customer experience compared with the previous year.
One survey found 65% of SMB respondents said that customer-centric
agility has increased in importance as a result of COVID-19.
Customer expectations matter, because - if you can meet them - customers
are likely to spend 140% more after a positive experience. To do well now and
57
in the future, companies need to close the gap between customer expectations,
and the actual customer experience.
Customer expectations have been changing over time for a number of
reasons
The power of the consumer is greater
With more competitors in each industry, the emphasis for companies
must be on how to keep your customers happy - because there are plenty of
alternatives out there.
Because of this increased power of the consumer and an expanding
market, it’s reported that 48% of consumers expect specialized treatment for
being a good customer, according to research by Accenture.
project. The ability of the project manager to understand the expectations of the
various stakeholders and motivate them to contribute to the project success is a
major aspect of the project manager’s leadership role.
Include the Client on Selected Project Teams
The client translates the needs of the organization through chartering the
58
The client also has a supervision role. This supervision is often
accomplished through regular project reviews and reports from the project
team. Depending on the complexity level of the project, the reviews can vary
59
A team was established to explore ways to reduce the approval process
for the drawings of the instructional design.
It was taking two weeks for the design review, and even though this was
within the normal time frame for design reviews, the project management team
believed there were opportunities to reduce this time and shorten the length of
the project.
The client’s engineering manager participated in the brainstorming
sessions that explored ways to reduce the design review time. Several good
ideas were developed and put into place.
The client’s engineering manager took these ideas back to the client’s
team and instituted many of the same ideas. There were two positive results:
(1) A shortened schedule that saved two weeks by the end of the design,
(2) A client that was emotionally engaged in the positive outcomes and
contributed to the project success.
Requirement Gathering or commonly known as the Discovery Phase is
basically a process in which we understand and identify a business’s project
full phase of requirements gathering is simply not needed. One can actually not
stress enough on the importance of discovery phase.
If the requirement gathering is not done properly, it can result into project
deliverables not meeting the business requirements which in turn would result
in waste of time and money.
This phase is critical as the information gathered will be utilized as a base
The SRS will include a vision or mission statement of the client company
requirement gathering. In this method, the business analyst talks to the user and
60
clients who are unable to give out detailed information as they are not aware of
the system development and related functionalities.
It is the responsibility of the business analyst to extract relevant information
from them which can be achieved by interview.
issues.
They are further responsible for requirement prioritization post they
collect all the requirements which are related to the software.
Under the observation method, the responsible person observes the team
in working environment and gets ideas about the software and subsequently
document the observation.
Observation can be invisible, the person simply observes the working
and does not interact or makes himself visible, and hence, the concerned person
observes and asks relevant questions.
61
This is a technique of building a model of software which helps in
uncovering and capturing software requirements from client. The output can be
broad mock-ups or sketch formats of software.
Use case diagram is a technique that shows how people interact with
software. It shows what a system does.
________________.
3. Under focus group, the idea is to collect information from
________________ .
Activity 2
62
client due to a clash of values or a failure to meet expectations.
Clarify Expectations
Client expectations are expressed in chartering documents such as the
scope of work, the project purpose statement, and the list of project deliverables.
Project manager, responsibility, and authority level. Name and authority of the
sponsor or another person (s) authorizing the project charter.
Project plan Approval documents
(for Reference purpose may change as per requirements exists
Project Title:
Author:
Version No.:
Date:
Purpose of project
This should be a brief but precise paragraph or two which states exactly what
the project is meant to do and why.
Project Outline
project. It aims to relate the impact of the project to the cost of doing the project
work and the risks involved, with mitigation as appropriate.
Smaller projects probably aren’t worth spending too much time on
detailed planning of a business case as it is important to just get on and do the
work.
However, if this isn’t done like this, then the case must be made somewhere
else in some form.
63
Stakeholders
Everyone who has a vested interest in the project activities/outcomes.
Objectives
What are the broad project activities and what they aim to achieve?
The cost of project activities at whatever level is most appropriate, set out
64
The completion of the most essential tasks are your milestones. How the
milestones are linked together (ie what they are dependent on) is your
Critical Path.
appreciation for the value of this diversity for project team members can prevent
During the life of the project, the project manager will often have the
opportunity to take advantage of the client, either because a clause in the
contract is not written accurately or because the project manager has access to
more detailed information.
to the project team. The project team analyses the new information to access the
potential impact on the project cost and schedule.
65
A skilled project manager can demonstrate a negative impact and increase
If the client believes the behaviour of the project manager is unfair, then
Acceptance Criteria
Acceptance criteria include the process and criteria that will be used to
stakeholder.
Acceptance criteria might include any number of elements, such as quality
This component should also describe the process stakeholders will use to
indicate their acceptance of the deliverables.
Project Deliverables
deliverables might include widgets with a 3-inch diameter that will in turn be
This could be a career-limiting move for the project manager because it’s
the project manager’s responsibility to document deliverables and monitor the
progress of those deliverables throughout the project.
Most projects have multiple deliverables. As in this example, if you are
assembling a new product with many parts, each of the parts might be considered
independent deliverables.
66
or a service that’s performed.
The product or service must be produced or performed in order to consider
the project complete. The deliverables might also include supplementary
outcomes, such as documentation or project management reports.
The bottom line is this: No matter how well you apply your project skills,
if the wrong deliverables are produced or the project is managed to the wrong
objectives, you will have an unsuccessful project on your hands.
Control Quality and Validate Scope work together to measure, inspect,
and accept the project deliverables.
Validating and accepting the work of the project shouldn’t be a
mindboggling task at this point if you’ve been following the project management
processes all along. For example, should monitor and inspect deliverables as
they’re completed.
Control Scope is absolutely essential for all projects.
Time and again changes to scope end up pitting stakeholders against the
place and because neither party clearly understood what was being requested.
67
3.5 CLINENT SATISFACTIONS
Projects always experience unexpected problems that produce stress.
Dealing with problems with competence is vital to maintaining a good
relationship with clients.
Establish Standards and Procedures for Decisions
There are competing interests on projects, and the larger and more
complex the project, the greater the number of issues and concerns that need to
be addressed.
Competing Interests
When project manager being asked for detailed questions and requested
performance data, the project manager patted said, “Don’t worry, I’ve got
everything under control.” Here is little worried because some of the key project
Often it is the next question that enables a project manager to discover the
less obvious expectations.
The next question is the one the project manager asks after the initial
response to inquiries about expectations. In our example, the client may express
that he or she wants project billings to be accurate and timely.
This is an easily understandable expectation, but when the project manager
asked the next question— “Can you tell me more about what you mean?”—
the client revealed the problems on her previous project, and the project team
developed a better understanding of the client’s concern.
68
The project team developed measures for tracking project billings that
measured both timeliness and accuracy. This process enabled the project team
to understand the client’s concern, develop work processes that demonstrated
a response, and provide data to the client on the timeliness and the accuracy of
the billing processes.
For the client that expected to hear about problems early and participate
in the problem-solving discussions, the project team shared the project action
item register and highlighted issues the team felt may be important to the client.
The project manager also discussed potential concerns with the client
After the project team captures the client expectations, the team then
develops a method for tracking performance against expectations. In our
69
project completion date or an increase in the project costs, typically involve the
client.
alternatives.
Others prefer to be involved in discussions to better understand the barriers,
developing alternative solutions and making decisions in a team environment.
Understanding the client’s decision-making preference and developing
procedures and processes that support that preference is important in meeting
client expectations.
Develop processes and methods that encourage both the client and team
members to identify issues and concerns early and develop processes for dealing
On projects with a low complexity level, the project manager and team
leaders can make decisions informally, with short meetings or phone calls.
meetings, responsibility matrices, and other tools foster the decision making on
a timely basis.
For project teams operating in diverse locations, Internet-based tools for
Now the problems have elevated to the point the client needs to be
informed. The greater the distance between the time of the event and the time the
client knows about the events, the greater the client’s frustration and mistrust.
70
Including the client in the processes for handling project issues or
clear communication
Example of a Volunteer Training Program
A museum planned to use volunteers as gallery interpreters to facilitate
a more engaging guest experience. The museum hired instructional designers
to manage a project to plan, develop, and implement training for prospective
volunteers.
hours. Throughout the project, it became clear to the project manager that the
complexity of the learning objectives required more than four hours of training.
Summary
How to manage client expectations
produce good results. When you know their requirements, then you will
71
Without any roadmap about what to do and where to start, you won’t progress.
And in the end, it will be impossible to manage the Client expectation.
Build trust and connections early
For any business, clients and customers are their biggest assets. It is
impossible to expect success without them. So, it is essential to build trust
and connections to manage their expectations.
this will help you manage their web design expectations better.
The advantage of building trust and connection with clients will let you
know what they are thinking, what their expectations are, and how they
approach things. This will help you know what is best for them and
manage their expectations.
Document everything
To manage client expectations, you always need detailed information
resources, etc.
Documentation makes sure that everything is under control and going
communication channels. You can use Slack, Zoom, Skype, anything that
72
Once their queries are responded to successfully, the trust they have in
increases.
Explain the current trends and changes and give them the best suggestions.
Make them understand why it is essential for them.
Keep reporting
The clients always want to know what is going on with their designs. Will
it be delivered on time? What is the status of the project? Such questions
remain on their mind constantly.
So, it is crucial to keep the clients up-to-date. You need to document
everything and keep reporting to them. Even if there is no documentation,
communicate with them through Slack or Zoom, or any channel.
Moreover, need to show that can complete the design on time.
It keeps the momentum going and builds trust with the clients. They will
understand that they have picked the right company to work with.
Deliver more
It is always important to know what can do and what can’t. Know
strengths and weaknesses, then set deadlines and expectations with the
clients. Otherwise, if fail to keep words, then the clients won’t be happy.
So, it is okay to under-promise and deliver more.
There is nothing more important than meeting the client’s expectations on
time. Either you can pitch your designs daily or weekly or communicate,
make sure that keep reporting to them and delivering quality work on
time.
In Conclusion
In a business, nothing is more important than building trust with the
clients. The closer you are to the clients, the more you will be successful. For
this, you need to know their expectations and manage them properly and build
requirements, and get the client’s agreement on the project scope, timeline, and budget.
Keep clients informed: Keep clients informed throughout the project,
providing regular updates on progress, risks, and issues.
Be proactive: Be proactive in addressing issues and concerns before they
become problems.
73
scope or requirements.
Manage expectations: Be realistic about what is achievable within the
project’s constraints and manage expectations accordingly.
Deliver high-quality work: Deliver high-quality work that meets or
exceeds the client’s expectations.
Overall, understanding and meeting client expectations requires strong
communication, attention to detail, and a commitment to delivering high-
quality work that meets the client’s needs and goals.
Keywords
Client Expectations: The perceived or stated requirements, needs,
and wants of a client regarding a product or service that they are
seeking from a company.
Client Communication: The exchange of information between a
company and its clients, including requests, feedback, and updates on
projects or services.
Needs Assessment: A process of identifying and evaluating the client’s
requirements, including their business objectives, goals, and challenges.
Service Level Agreement (SLA): A contractual agreement between a
will deliver and the performance standards that the client can expect.
Scope of Work:
agreed upon between a client and a company for a particular project.
Customer Relationship Management (CRM): A strategy and technology
used to manage interactions with clients, including customer data, sales,
and service.
Quality Assurance: The process of ensuring that a product or service
meets or exceeds the client’s expectations, including testing, inspection,
and documentation.
Feedback Loop: A continuous process of gathering, evaluating, and
responding to client feedback to improve the quality of products or services.
Self-Assessment Questions
1. How can you keep clients informed throughout the project?
2. Why is it important to be proactive in addressing issues and concerns?
3. What is the best way to manage changes to the project scope or
requirements?
4. How can you ensure that you deliver high-quality work that meets client
expectations?
74
5. Why is it important to maintain a positive working relationship with
clients?
2. requirement gathering
3. representatives to understand the software idea clearly
75
Suggested Reading
1. Project Management Institute, Inc., A Guide to the Project Management
Body of Knowledge (Pmbok Guide), 4th Ed. (Newtown Square, PA:
Project Management Institute, Inc., 2008), 6.
2. Jack R. Meredith and Samuel J. Mantel, Jr., Project Management: A
Managerial Approach (Hoboken, Nj: Wiley, 2006), 8.
3. Russell W. Darnall, The World’s Greatest Project (Newtown Square, PA:
Project Management Institute, Inc., 1996), 48–54
4. An Introduction To The History of Project Management: from the Earliest
Time to ad 1900 by Y. C. Chiu, Netherlands, Eburon Academic Publishers.
5. Introduction To Project Management by Kathy Schwalbe, Thomson
Course Technology, 2006.
6. Project Management by K. Nagarajan, New Age International (P) Limited.
7. Project Management Absolute Beginner’s Guide (4th Edition)” by Greg
Horine
8. The Art of Project Management” by Scott Berkun
76
Project Planning
UNIT
4
Structure:
Project Planning 77
Objectives
After going through this unit, you will be able to:
Importance of project planning in project environments
Understand importance of feasibility study
Process of requirement gathering
Preparation of project plan & other subsidiary documents
Change request & client approved project plan
One view of project planning divides the activity into these steps: setting
measurable objectives. identifying deliverables. scheduling.
you are ready to enter the second phase in the project management life cycle:
the detailed project planning phase.
Project planning is at the heart of the project life cycle, and tells everyone
involved where you’re going and how you’re going to get there.
The planning phase is when the project plans are documented, the
78
created. It involves creating a set of plans to help guide your team through the
implementation and closure phases of the project.
The plans created during this phase will help you manage time, cost,
and external suppliers to ensure that you deliver the project on time, within
budget, and within schedule.
The project planning phase is often the most challenging phase for a project
79
Identifying constraints: Project planning helps to identify the constraints
that may impact the project, including time, budget, and resources.
Developing a timeline: Project planning helps to establish a timeline for
the project, including the start and end dates for each phase of the project.
Allocating resources: Project planning helps to allocate resources to the
project, including personnel, materials, and equipment.
Identifying risks: Project planning helps to identify potential risks to the
project and develop strategies for mitigating those risks.
Communicating with stakeholders: Project planning helps to
communicate the project’s objectives, timeline, and resource requirements to
stakeholders, including clients, team members, and project sponsors.
Overall, project planning provides a roadmap for the successful completion
of a project, ensuring that everyone involved in the project is on the same page
and working towards the same goals.
Process Name Project Management Knowledge area
Develop Project Management Plan Project Integration
Project Scope
Collect Requirements Project Scope
Create WBS Project Scope
Project Schedule
Sequence Activities Project Schedule
Estimate Activity Resources Project Schedule
Estimate Activity Duration Project Schedule
Develop Schedule Project Schedule
Estimate Costs Project Cost
Determine Budget Project Cost
Plan Stakeholder Engagement Project Stakeholder
Plan Communication Project Communication
Plan Risk Management Project Risk
Identify Risk Project Risk
Perform Qualitative Risk Analysis Project Risk
Perform Quantitative Risk Analysis Project Risk
Plan Risk Response Project Risk
Plan Procurement Management Project Procurement
Plan Resource Management Project Resource
Plan Quality Management Project Quality
during the initiation phase. It includes planning the steps necessary to meet
80
Now that these objectives have been recognized, they must be clearly
articulated, detailing an in-depth scrutiny of each recognized objective. With
such scrutiny, our understanding of the objective may change. Often the very
act of trying to describe something precisely gives us a better understanding of
what we are looking at.
This articulation serves as the basis for the development of requirements.
What this means is that after an objective has been clearly articulated, we can
describe it in concrete (measurable) terms and identify what we have to do
to achieve it. Obviously, if we do a poor job of articulating the objective, our
requirements will be misdirected and the resulting project will not represent the
true need.
Users will often begin describing their objectives in qualitative language.
81
Activity 1
82
potential investors and lending institutions It must therefore be conducted with
an objective, unbiased approach to provide information upon which decisions
can be based.
A project feasibility study is a comprehensive report that examines in detail
four Ps, its risks and POVs, and its constraints (calendar, costs, and norms of
quality).
The goal is to determine whether the project should go ahead, be
technical and operating characteristics are engineered into the design. Therefore,
operational feasibility is a critical aspect of systems engineering that needs to
be an integral part of the early design phases
A company may conduct a feasibility study when it’s considering
launching a new business, adding a new product line, or acquiring a rival.
A feasibility study assesses the potential for success of the proposed plan
It’s a good idea to have a contingency plan on hand in case the original
project is found to be infeasible.
Understanding a Feasibility Study
A feasibility study is an assessment of the practicality of a proposed plan
or project.
83
A feasibility study analyses the viability of a project to determine whether
the project or venture is likely to succeed.
The study is also designed to identify potential issues and problems that
could arise while pursuing the project.
managers discern the pros and cons of undertaking a project before investing a
Feasibility studies can also provide a company’s management team with crucial
information that could prevent them from entering into a risky business venture.
Such studies help companies determine how they will grow. They will
know more about how they will operate, what the potential obstacles are, who
the competition is, and what the market is.
Feasibility studies also help convince investors and bankers that investing
in a particular project or business is a wise choice.
How to Conduct a Feasibility Study
The exact format of a feasibility study will depend on the type of
organization that requires it. However, the same factors will be involved even if
their weighting varies.
Preliminary Analysis
Although each project can have unique goals and needs, there are some best
practices for conducting any feasibility study:
Conduct a preliminary analysis, which involves getting feedback about
the new concept from the appropriate stakeholders.
Analyses and ask questions about the data obtained in the early phase of
the study to make sure that it’s solid.
Conduct a market survey or market research to identify the market demand
and opportunity for pursuing the project or business.
Write an organizational, operational, or business plan, including
identifying the amount of labour needed, at what cost, and for how long
Prepare a projected income statement, which includes revenue, operating
84
Technological considerations: Ask what will it take. Do you have it? If
not, can you get it? What will it cost?
Existing marketplace: Examine the local and broader markets for the
product, service, plan, or business.
Marketing strategy: Describe it in detail.
What are the human capital needs for this project?
Draw up an organizational chart.
Schedule and timeline:
project’s completion date.
phase, but you’ll continue to manage your project requirements throughout the
project timeline.
Requirements gathering is the process of determining what your projects
need to achieve and what needs to be created to make that happen.
Data Gathering
Data gathering techniques include brainstorming, focus groups, and
interviews. Brainstorming is used with groups of people to gather information,
whether pertinent to the topic or not, in a short amount of time.
Focus groups are sessions conducted with stakeholders to help identify
success criteria, risks, and other information. Interviews are typically one-
on-one and used to gather information regarding project requirements, the
identifying constraints.
The techniques associated with this process include questionnaires and
surveys, and brainstorming.
85
Both of these techniques can be used to help identify stakeholders and
their needs on the project. Brainstorming can involve the usual process of
getting folks in a room and having them name things (or stakeholders in this
case) that come to mind while a facilitator jots down all the ideas.
It may also involve brain writing, a type of brainstorming, where
participants are given the question or brainstorming topic ahead of time so they
have time to think about their answers.
After a period of time, you hold the meeting and host the brainstorming
session. A brain writing meeting can be face-to-face, or you could use technology
such as a video- or web-conferencing tool to hold the meeting.
Probably familiar with the fact that everybody has their own common
project assumptions about what a project should include. Through requirements
gathering, you collect insights from a project’s stakeholders to get an adequate
understanding on how a project should work — before you start the work.
Project requirements are generally split into two categories:
Business requirements: What the project should do. You’ll also hear
these referred to as “functional requirements.”
Technical requirements:
requirements. You’ll also hear these referred to as “non-functional
requirements.”
Let’s add some clarity with a work-related example. Imagine your team
is responsible for building a new job application portal for your company.
surpasses them.
Why are requirements gathering important?
Requirement gathering and analysis might sound like an unnecessary
formality, especially when you and your team are eager to sink your teeth into
the project.
However, getting a handle on a project’s requirements is a crucial step
for several reasons. Here’s what can happen when you don’t take the time to
understand them.
Requirement Gathering or commonly known as the Discovery Phase is
basically a process in which we understand and identify a business’s project
86
Although the discovery phase is an essential phase in any critical project
full phase of requirements gathering is simply not needed. One can actually not
stress enough on the importance of discovery phase.
If the requirement gathering is not done properly, it can result into project
deliverables not meeting the business requirements which in turn would result
in waste of time and money.
This phase is critical as the information gathered will be utilized as a base
The SRS will include a vision or mission statement of the client company
requirement gathering. In this method, the business analyst talks to the user and
clients who are unable to give out detailed information.
issues.
Joint Application Method
Observation
Focus Group
Interface Analysis
Prototyping
Use case diagram
87
Reduce Risk in Requirements Gathering
The project manager needs to duly assess and understand the novelty
value of the requirement gathering process of individual project.
Requirement risks are one of the most insidious risks that threaten IT
several kinds of pitfalls. Herein we shall discuss about the various challenges
that can grip the requirements gathering process and discuss the potential
approaches to deal with them.
Stakeholders and usually clients have a clear idea about the problems they
are facing or exploring a particular opportunity; however, more often than not
they are pretty clueless about exactly what they are looking to achieve.
In order to address this concern, it is advisable to break the project into
small bits and start from the section where the client has most clarity.
There are collaborative modelling tools which allow the clients to have
a high-level vision of the end result which makes getting feedback early in the
process simple enough.
It is also advisable to ask questions from the client and identify current
business practices and identify the pain points which can be improvised.
88
testable so as to have a solid foundation against which the results can be later
measured.
Clients Change their Minds Often
89
requirements and some suggested additional revenue streams and also the basic
USP (unique selling point)
The SRS will include some further details as follows:
Project Overview
Objectives & Constraints
Functional and data Description
System architecture
Architecture context diagram (ACD)
System module narrative
Resource requirements
Team members by skill type
Systems requirements
Estimates will further include the following:
Development timeline based on above
Costs associated with each element above
Hosting Requirements, Cost Estimation, TimeLine
In the industry having multiple companies for the top slot, there are a few
best practices in the requirements gathering phase that must be followed for
most desirable results.
Requirements Gathering Best Practices
The primary important step in requirement gathering phase is identifying
90
To be successful in requirements gathering or discovery phase, it is vital
that the business analyst draws out a plan which is helpful for capturing the
basic requirements of the client. When this plan is carefully researched,
and drafted, there is little room for rework which further helps in saving
time.
It is also necessary that all the stakeholders give their view with regard
to the software being developed and kept in loop of the progress being
made.
Working as per the requirement gathering process ensures that the quality
of the end product is superlative and makes it simpler at all stages of the
SDLC.
This phase gives a solid foundation to the rest of the processes and
steps for design and development and hence ensures that the problem
is resolved.
The stronger the foundation and clearer the understanding for the project,
smoother will be the course of things when development begins and we
move onto the support and testing phases of the project.
however, better the understanding, more solid the end product would turn
out to be.
This document is your trigger point for designing, documenting and
developing and will be of immense help in all aspects of the project some
time or the other.
Power.
The constraints are the standard constraints of calendar, costs and norms
of quality that can each be objectively determined and measured along the entire
project lifecycle.
feasibility study; smaller projects, for example, may not require an exhaustive
environmental assessment
91
o How do we write a project plan that aligns with company goals?
o What do stakeholders expect? What will be expected from them?
o How will you measure success?
o What are your resources?
o What assets or deliverables are expected out of this project?
According to executive leaders, a lack of clear goals accounts for 37% of
deadlines you set for your project work plan have nothing anchoring them.
Now that you have a list of key stakeholder needs and their buy-in, begin
to assign them to goals and OKRs. OKRs are a planning and goal-setting
technique made famous by Intel and Google. Your project should align with
your team and company’s OKRs.
Try writing down the project goals on a project plan board and connect
them to the stakeholder requirements they address. From there, build out the
structure, milestones, and tasks it takes to reach those goals.
For example, the project or product launch itself can be a big milestone,
so it’s important to know how you will go about it - perhaps you’ll use a product
in points throughout the project so that everyone is clear about what progress
looks like, what the expectations are, and when they’ll be measured.
Requirements Documentation
There are many reasons why it is a good practice, but at the very least,
it is the most important tool to ensure that you have accurately understood the
requirements of the project.
The customer must review what have understood, and what you think you
are being asked to build. It must be written in language that they can understand,
and in a structure, that makes sense. I will mention two methods:
1. Hierarchical - The classic format for a textual representation of requirements.
There is nothing wrong with this approach, if it is done properly.
2. Use Cases - Use Cases are borrowed from the world of Object Oriented
Analysis and Design. They are simply scenarios of functionality. Each
Use Case represents a kind of task that a user will perform with the system
being built.
I will not go into the details of Use Cases, but I want to point out that you
can use this powerful form of describing what a system will do without using
other aspects of the Object-Oriented approach.
You don’t need to use the modelling languages or tools that are typically
used by organizations that have adopted the Object-Oriented approach in order
to make full use of this technique for documenting requirements. I highly
recommend it.
92
Before actually handing the requirements documentation to the customer,
more than one name by one or more departments. I’ve never written a
and acronyms.
2. Discrete, atomic - Sometimes a requirement needs to be broken down
into sub requirements, in order to be accurately executed. Ask yourself,
“Can this requirement be broken down?” Break it down until it cannot be
broken down any further, just like an atom.
3. Scope - The question of scope should be asked in both directions: Is the
requirement within the scope of the project (a test for relevance)? Is the
project fully within the scope of the requirement (a test of importance)?
4. - In order to know if we have met the requirements at
the end of the project, we need to be able to test the results of the system,
and compare those results to what was requested. If the requirement was,
“The system shall complete one cycle in a reasonable amount of time,”
your success may depend on whether the project sponsor had a good
night’s sleep.
Quantifying requirements can sometimes be a painstaking process, but
persist, and be creative. A “user-friendly system” is one which 7 out of 10
new users rate it as “easy” or “very easy” after a one-day training class. If
the customer doesn’t want to test it, then perhaps it shouldn’t be included
as a requirement.
5. Traceable - Requirements Tracing is an important technique, since we can
use it to control scope creep. We should be able to trace each activity in the
project to a requirement. Every design decision should be answering a need
expressed in one or more requirements. Every module or program written
should justify its existence because it is needed to meet a requirement.
We also trace requirements “backward”: every requirement should be
traceable back to an objective in the project charter or initial project plan. If it
can’t, it is probably out of scope. An excellent technique for ensuring traceability
is a simple matrix, which can also be used to manage requirements throughout
the project.
Ensuring Quality Requirements
Having excellent requirements does not happen by accident. It is widely
accepted in the industry that requirements defects are the most common, and
93
requirements. Good Quality Control practices include testing requirements
thoroughly during the gathering and documentation process.
Table 1 Requirement Documentation
Requirements Management
Requirements Management is necessary partly because we may not do a
perfect job of ensuring that every requirement is of high quality.
However, even if we did a perfect job, the customer can announce midway
through the project that they have changed their mind (as often happens in real
life). That is when a Requirements Traceability Matrix can be indispensable. A
sample matrix is provided in Exhibit 1.
Create a project scope document
Now that you have the project outlined, your tasks aligned with goals, and
buy-in from the team, it’s time to create a project scope document detailing the
project elements you’ve listed in step two.
completed to accomplish each one. For each task, determine the amount
of time it’ll take, the resources necessary, and who will be responsible for
execution.
Finalize and record the project details so that everyone has a single source
of truth. Make the document easily shareable, like in your project management
tool, to reduce the chance of costly miscommunication.
While preparing project scope documentation and calculating earned
value should be standard practice,
Craft a detailed project schedule
With your goals, tasks, and milestones already outlined for you, it’s time
to start plugging your project into a schedule. A Gantt chart is a handy tool
that helps you visualize your project timeline easily. It’s an interactive timeline
that gives you a complete view of the project’s progress, work scope, and
dependencies.
94
Dependencies are tasks that need to be completed before other tasks can
begin. As you plot out tasks, use subtasks to help you break up larger ones into
smaller ones. This can make reporting (you can check out our guide on how to write
Tasks: The individual tasks that people need to carry out to achieve your goals
Subtasks: No longer than a few days each, these help you break a larger
task into the smaller steps
Milestones: Major phases or events in your project that help break up the
project and act as check-ins throughout the project life cycle
Even folks who already know how to write a project work plan and have
done so a hundred times can underestimate their labour needs.
A RACI chart helps you determine who will do what for your project. It’s a
matrix of all a project’s tasks, paired with who’s responsible (assigned to complete
the work), accountable (has yes/no/veto power), consulted (needs to approve or
contribute), and informed (needs to know about the action or decision).
As you begin to assign tasks, make sure you take bandwidth into
consideration. Clarify the responsibilities and expectations of each person.
impact the project’s timeline or budget. Knowing how to calculate earned value to
monitor the level of work completed on a project against the plan is imperative.
For project managers, tools for resource management can help you
95
According to research, employees spend nearly 20% of the workweek
CHANGE REQUEST
A change request form is a form used to request, approve, and track
project-related changes. Stakeholders request changes for many reasons, including
the following: One of the items you need to complete the project goes out of stock.
takes place over a predetermined amount of time (the faster the better as long
as accuracy is maintained) and sets up a step by step process for dealing with
major structural changes.
Overall, the project change control process makes sure that no matter what
happens, the project will continue to move forward without leaving anyone out
of the loop.
How to achieve integrated change control in project management
Create a change control system:
request. For example, adding an extra step to a project phase that won’t take
97
submitted, approved, and updated.
Develop change control procedures: Designate a leader in this process to
communicate with stakeholders, oversee progress, and keep everyone informed.
They’ll also come up with predetermined responses to change requests
to help keep the process moving forward. Also, be sure to include an analysis
strategy, and reputation are up to par with the quality standards and requirements
established by the organization.
The approval process is the last stage in project management and
consists of the following processes:
creative collaterals
98
Deliverables are either approved or reintroduced into the production
loop
You can think of the project approval process as hosting a dinner party.
everyone.
Luckily, there’s an easy seven-step method you can follow to establish the
smoothest project approval process possible.
99
Summary
100
Keywords
Project Scope:
deliverables, tasks, and responsibilities.
Work Breakdown Structure (WBS): A hierarchical decomposition
of the project into manageable, smaller tasks, making it easier to plan,
schedule, and execute the project.
Milestones:
to track progress and provide visibility to stakeholders.
Critical Path: The sequence of tasks that must be completed on time for
the project to be completed on scheduleResource Allocation: The process
of assigning and managing resources, including personnel, equipment,
and materials, to meet project requirements.
Risk Management: The process of identifying, assessing, and mitigating
risks that could impact the project’s success.
Project Schedule: A timeline that outlines the start and end dates of
project tasks, milestones, and deadlines.
Dependencies: The relationships between tasks, where the completion of
one task depends on the completion of another task.
Budgeting: The process of estimating and managing the costs associated
with the project, including labour, materials, and overhead expenses.
Project Management Software: Tools that facilitate project planning,
scheduling, tracking, and communication, including Gantt charts, project
dashboards, and collaboration platforms.
101
Self-Assessment Questions
1. What is project planning?
2. Why is project planning important?
3. What are the key elements of project planning?
4. What is a project scope statement?
5. How do you develop a project schedule and budget?
102
Suggested Reading
1. Project Management Institute, Inc., A Guide to the Project Management
Body of Knowledge (PMBOK Guide), 4th Ed. (Newtown Square, PA:
Project Management Institute, Inc., 2008), 6.
2. Jack R. Meredith and Samuel J. Mantel, Jr., Project Management:
A Managerial Approach (Hoboken, Nj: Wiley, 2006), 8.
3. Russell W. Darnall, The World’s Greatest Project (Newtown Square, PA:
Project Management Institute, Inc., 1996), 48–54
4. An Introduction to the History of Project Management: from the Earliest
time to Ad 1900 by Y. C. Chiu, Netherlands, Eburon Academic Publishers.
5. Introduction to Project Management by Kathy Schwalbe, Thomson
Course Technology, 2006.
6. Project Management by K. Nagarajan, New Age International (P) Limited.
7. Project Management Absolute Beginner’s Guide (4th Edition)” by Greg
Horine
8. The Art of Project Management” by Scott Berkun.
103
104
Working with People on Projects
UNIT
5
Structure:
reveal if you need more or less of a certain kind of resource, like specialized
106