WELCOME TO CLASS ODD SEMESTER 2024-25

NAME OF THE PROGRAM: BBA

P.R.C. APPROVAL REF.: PU-SOC/2022-2023/BOS-1

SEMESTER/YEAR: 4th Semester

COURSE TITLE & CODE: Project Management

BBA 3072

COURSE CREDIT STRUCTURE: 4-0-4

CONTACT HOURS: 60 Sessions
COURSE INSTRUCTORS: Dr. Annette Christinal

Dr. Annette Christinal Course-Project

12-Feb-25
Management BBA 3072 1
 COURSE OUTCOMES: On successful completion of the course, the students shall be able to

• CO 1: Define each phase of the lifecycle of a project. (Knowledge)

• CO 2: Discuss the risks involved and resources needed for each project
stages (Comprehension)
• CO 3: Explain the requirements needed to successfully complete
projects (Comprehension)
• CO 4: Illustrate the project scopes and estimate the project costs by
considering factors Of cost, variances, and profits (Applications)
• CO 5: Sketch a project using a Gantt chart (Applications)..

Dr Annette Christinal Course-Project

12-Feb-25
Management BBA 3072
2
• MODULE 1: Introduction to Project Management (10 Sessions)
(CO1 Knowledge)
• Projects & Project Management-Objectives-Definition-Importance; Tools
and Techniques, Project Team, Roles and Responsibilities of Project
Manager, Determinants of Project Success.
• Project life cycle and its phases-Classification/Types of projects; Project
selection, non-quantitative and scoring models; Consideration factors,
factors affecting selection, technology selection; Alternatives options,
Techniques of long term forecasting;

Dr Shivakami Rajan Course-Project

12-Feb-25
Management MGI260
3
 • DELIVERY PROCEDURE (ANDRAGOGY):
• Self-learning: Project Team, Roles and
Responsibilities of Project Manager
• Participative learning: Debates and
Discussion on Construction Projects
• Flipped learning: Reasons for Project
Failures.

12-Feb-25 4
Text Books
• • R1 Prasanna Chandra, Dr: Projects Planning, Analysis,
Financing, Implementation & Review, Tata McGraw Hill.
• R2 Narendra Singh: Project Management.
• R3 Jach R. & Meredith Samuel J: Project Management.
• R4 Vasanth Desai: Project Management, Himalaya
Publishing House
Reference Articles:
1. Pinto, (2009), Project Management, 1st Edition, Pearson Education
2. Choudhury, S, (2007). Project Management, 1st Edition, Tata Mc Graw Hill
Publishing Company
3. Bhavesh, M. Patel (2009). Project Management: Strategic Financial Planning
Evaluation and Control, Vikas Publishing House Pvt. Ltd.
4. Panneerselvam, R., and Senthilkumar, P., (2007), Project Management,
Prentice Hall of India.

12-Feb-25 5
 What is an Project Exactly?
• A project is a work performed by an organisation one time to produce
a unique outcome.
• One-Time- the work has a DEFINTE beginning and a DEFINITE ending
• Unique- the work results are different in one or more ways from
ANYTHING THE FIRM HAS DONE BEFORE
• Examples of projects are
• ??

Dr Annette Christinal Course-Project

12-Feb-25
Management BBA 3072
6
 Examples!
• Building a new house
• Developing a new software application
• Performing an assessment of CURRENT manufacturing process
in YOUR FIRM
• Improving business process- for dept or Entire firm
• Writing a book
• Mergers and Acquisitions
• Shifting or relocating your firm.

12-Feb-25 7
 Dr Annette Christinal Course-Project
12-Feb-25
Management BBA3072
8
 Definition
The Project Management Project characteristics
Institution(PMI) defines A project is an activity that :
Project is a temporary endeavour • is temporary having a start
to produce a unique product or and end date
service. • is unique
Requires application of
• are completed when project
knowledge, skills, tools and goals are met
techniques to project activities to
• brings about change
meet project requirement.
• has unknown elements, which
therefore create risk

Dr Annette Christinal Course-Project

12-Feb-25
Management BBA 3072
9
 Why Projects are done?

• projects are formed to solve a problem or

take advantage of an opportunity.
• the uniqueness of the activity that is the
deciding factor – do we do this every year?
• If yes, then it is not truly a project –
• although you can use project methods to
get it done.

12-Feb-25 10
 Answer these?

• Are these Projects

– Building a deck
– Implementing a new system
– Mowing your lawn
– Planning a birthday bash for the entire family
– A Student graduation

12-Feb-25 11
 Project Management
Project Management is the application of knowledge, skills, tools and techniques
applied to project activities in order to meet the project requirements,
It is a process that includes planning, putting the project plan into action, and
measuring progress and performance.
On any project, THERE will have a number of project constraints that are competing
for FIRMS attention. They are cost, scope, quality, risk, resources, and time.
• Cost is the budget approved for the project including all necessary expenses
needed to deliver the project.
• Scope is what the project is trying to achieve. It is the reason and the purpose of
the project.
• Time is defined as the time to complete the project. Time is often the most
frequent project oversight in developing projects- missed deadlines and
incomplete deliverables.

12-Feb-25 12
 Project Management
Project has an objective, or a set of objectives, Basic tenets of project management
to achieve-operated within The triple constraint
a given set of rules, regulations, constraints
and restrictions
needs resources or inputs-converts the given
inputs into outputs through a process of
implementation.
Every project has two phases basically;
1. the first is preparation and construction,
and
2. the second, its operation.---where
conversions take place
Project Management by Jennifer Russell ( http://www.tharpo.com/, https://c
reativecommons.org/licenses/by/3.0/ ) . Creative Commons 4.0 International
License (http://creativecommons.org/licenses/by/4.0/)

12-Feb-25 13
 Case Study
• AN EXAMPLE of project that cut quality because the project
costs were fixed.
• The P-36 oil platform was the largest footing production
platform in the world capable of processing 180,000 barrels
of oil per day and 5.2 million cubic meters of gas per day.
Located in the Roncador Field, Campos Basin, Brazil, the P-36
was operated by Petrobras. In March 2001, the P-36 was
producing around 84,000 barrels of oil and 1.3 million cubic
meters of gas per day when it became destabilized by two
explosions and subsequently sank in 3,900 feet of water with
1,650 short tons of crude oil remaining on board, killing 11
people. The sinking is attributed to a complete failure in
quality assurance, and pressure for increased production led
to corners being cut on safety procedures. It is listed as one
of the most expensive accidents with a price tag of
$515,000,000.

12-Feb-25 14
 • For example, Ford Motor Company is in the business of designing and
assembling cars. Each model that Ford designs and produces can be
considered a project- unique-model differ, features, customers
segment-different purpose(SUV, Sports etc)design ,marketing
• However, the actual assembly of the cars is considered an operation
(i.e., a repetitive process that is followed for most makes and models)

12-Feb-25 15
 Common Project Terms
• Deliverables: Tangible ‘things’ that the project produces
• Milestones: Dates by which major activities are performed.
• Tasks: Also called Actions. Activities undertaken during the project
• Risks: Potential problems that may arise
• Issues: Risks that have happened
• Gantt Chart: A specific type of chart showing time and tasks. Usually created by
a Project Management program like MS Project.
• Stakeholder: Any person or group of people who may be affected by your
project

12-Feb-25 16
 Using an Example-Building a deck
• Deliverables: A plan, A approved Plan from customer, the DECK.
• Milestones: Dates

•Tasks: Actions. Activities

12-Feb-25 17
 Risks: Potential problems ??? STUDENTS?
Issues: Risks that have happened
Gantt Chart: See Below
• Stakeholder: Customers, owner, Suppliers, Banks, Government.

12-Feb-25 18
 Tools and Techniques of PM
There are various tools and techniques used in project management to
accomplish successful project
1.Process Modeling and Management tools :
Process modeling simply means to model software processes. At first,
developers need to fully understand process and work of software, then only
they can be able to model process. This tool represents key elements of process
that are important. So, it makes it easier to perform work tasks in efficient and
proper manner.

12-Feb-25 19
 Tools and Techniques of PM
2.Project Planning tools :
Project planning simply means to plan and set up project for successful
development within timeframe.
• It includes defined stages or steps to define objectives of project with
designated resources, clarify scope of what should be done, and then develop
list of tasks that are needed to be done to complete it.
• Tools used for project planning can be CPM (Critical Path Method) and PERT
(Program Evaluation and Review Technique).
• Both of them are used for finding parallelism, eliminating bottlenecks in
projects, and scheduling activities of project.
• Some tools that make planning of project in efficient way are Trello, Nifty,
Asana, Team Gantt, etc.

12-Feb-25 20
 Gantt

12-Feb-25 21
 Example

12-Feb-25 22
 Contd.
A Gantt chart, commonly used
in project management, is one
of the most popular and useful
ways of showing activities (tasks
or events) displayed against
time. On the left of the chart is a
list of the activities and along
the top is a suitable time scale.
Each activity is represented by a
bar; the position and length of
the bar reflects the start date,
duration and end date of the
activity

12-Feb-25 23
 CPM
Critical Path Method,
is an algorithm of
resource-utilization
that schedules a set
of project activities.
CPM is used to
construct a project
model that includes:

12-Feb-25 24
 PERT
A PERT diagram, is a
project management tool
used to schedule,
organize and coordinate
tasks within a project. It
provides a graphical
representation of a
project's timeline

12-Feb-25 25
 Developing a WBS
1. Outline of the work to be
performed
2. Provides a framework for
defining the work on the
project.
3. Developing the WBS
should involve the people who
will be doing the work
4. WBS should be
deliverable-oriented

12-Feb-25 26
 Example

12-Feb-25 27
• Risk Analysis tools :
Risk analysis simply means to identify and analyze errors or defects or any
issue that can cause negative impact and result in the changed outcome
and objectives of project.
• The analysis is done so that Firm can fix issue or remove error to avoid
effect caused by them.
• These tools help in identifying risks and are useful for binding risk table.
These provide detailed guidance in the identification and analysis of risks.
• The risks identified can be categorized into catastrophic, critical, marginal,
or negligible.
• A cost is associated with each risk which can be calculated at each stage of
development. Some tools and techniques are Delphi technique,
Information gathering technique, Checklist analysis, etc.

12-Feb-25 28
 4.Project Management tools :
Project management simply means to track or control progress and tasks
of project. These tools are extension of project planning tools. These tools
are generally used to update pans if require and schedule project. These
tools make Project Management more effective and efficient. Some tools
are Gantt chart, mind map, WBS chart (Work Breakdown Structure), etc.
5.Metrics and Management tools :
Metric management tools are very good for software as they provide very
quick and easy way to track software development, set goals, and
measure performance. These tools help in capturing and finding out
specific metrics that are useful and provide overall measure of quality.
These tools focus more on process and product characteristics. For
example, “defects per function point”, “Line Of Code/person-month”

12-Feb-25 29
6. Quality Assurance tools :

Quality assurance in software engineering simply means to maintain level of quality of

software product by focusing on each step of process of development or production
and delivery. It prevents mistakes and any defects or errors in manufactured products.
These are actually metrics tools that audit source code to ensure compliance with
language standards. Some tools that are used for both Quality management plan and to
control quality process are Pareto Diagrams, control charts, histograms and scatter
diagrams, etc.
7. Database Management tools :
Database management simply means to organize, store, and retrieve data from
computer in efficient manner. It provides consistent interfaces for project for all data, in
particular, configuration objects are primary repository elements.Some best database
management tools are MySQL workbench, SolarWinds Database Performance Analyzer,
TablePlus, TeamDesk, etc.

12-Feb-25 30
 What is a project team?
• The project team is the group of people responsible for executing the
tasks and producing deliverables outlined in the project plan and
schedule, as directed by the project manager, at whatever level of
effort or participation defined for them.
• Project team members may or may not be involved during the entire
life cycle of the project and may or may not be full time to the project.
• Project teams are comprised of many different roles such as project
manager(PM), subject matter experts(SME), business analysts(BA),
Vendor representation(Vendors) and other stakeholders.

12-Feb-25 31
 Project Manager
• The project manager is primarily responsible for the
successful completion of a project.
• The project manager’s role is to ensure that the project
proceeds within the specified time frame and under the
established budget while achieving its objectives.
• Project managers make sure that projects are given
sufficient resources while managing relationships with
contributors and stakeholders.

12-Feb-25 32
 Roles and Responsibilities of Project Manager.
• Developing a project plan
• Managing deliverables according to the plan
• Recruiting project staff
• Leading and managing the project team
• Determining the methodology used on the project
• Establishing a project schedule and determining each phase
• Assigning tasks to project team members
• Communicating with upper management

12-Feb-25 33
 Roles and Responsibilities of Project Manager.
• PM will negotiate with functional managers for their resources’ time
on the project, targeting the resources who are most qualified (skills
and ability) for the specific project needs.
• The PM-to acquire commitment and time from resources who are
– knowledgeable about the work that needs to be done,
– are able to represent the stakeholders, and
– will work both independently on their tasks as well as in partnership with the
project team towards the final deliverable(s).

12-Feb-25 34
 Project Team Member
• Project team members are the individuals who actively work on one or
more phases of the project.
• They may be in-house staff or external consultants, working on the
project on a full-time or part-time basis.
• Project team member roles can vary according to each project.
• Contributing to overall project objectives
• Completing individual deliverables
• Providing expertise
• Working with users to establish and meet business needs
• Documenting the process

12-Feb-25 35
 Responsibilities of Responsibilities of Project
Project Team Sponsor
• As a group, the project team The project sponsor is
should represent the diversity of • the driver and in-house champion of the
skills and knowledge necessary, project.
• members of senior management and have
in the proportion required, to
a stake in the project’s outcome
successfully complete the project
• work closely with the project manager.
and represent stakeholders. • legitimize the project’s objectives and
• Provide information, estimates participate in high-level project planning
and feedback to the PM during • resolve conflicts and remove obstacles that
project planning occur throughout the project life cycle
• Report issues and status to PM
The project sponsor’s responsibilities usually
include:
•Making key business decisions for the project
•Approving the project budget
•Ensuring availability of resources
•Communicating the project’s goals throughout
the organization
12-Feb-25 36
 Roles
• Business analyst • Project manager
• Customer • Project owner
• Strategic Architect • Project team
• Functional manager • Sponsor
• IT governance
• Stakeholders
• Manager PMO
• • Subject
Program business change manager matter expert
• Program manager

12-Feb-25 37
 Project Success.

• Every stakeholder may have a different idea of what project success

looks like.The standard criterion of project success-develop a common
definition
• The project scope definition is a document that will be published and
used by the project owner and project participants for planning and
measuring project success-Scope describes what the organization
expects to deliver to the customer when the project is complete
• The definition of project success often includes
– completing the project on time
• Completion of the project on time is a primary responsibility of the project manager, and completing the
project on time requires the development of a realistic plan and the effective management of the plan.
– completing the project within budget
– meeting project specifications

12-Feb-25 38
 Determinants of Project Success
1. Experienced project managers & skilled project team
The more experienced a project manager, the more confidence and skill he
will have to overcome the challenges of the daily project business. Successful
project managers not only impress with technical expertise but also with
leadership.
A professional and skilled project team with a prolific leader can use as much
advanced methods
bring a positive attitude to the project.

12-Feb-25 39
2. Methodical approach
The choice of an appropriate project management methodology is crucial for success.
• Adopt the tools and techniques of the framework chosen to make sure process is
clear, reliable and efficient.
• Invest time in defining a clear project goal all stakeholders understand and agree
upon.
3. Planning

• Many project managers rush to the execution phase of the project and do not take
enough time for solid planning.
• A thorough planning will help -. As the quote by Benjamin Franklin says: "If you fail
to plan, you plan to fail."

12-Feb-25 40
 • 4. Follow best practices
• No need to reinvent the wheel:. Use wherever possible frameworks
and best practices. Draw from the experience of past successes and
adapt proven strategies .Focus on the truly unique aspects of the
project which will make all the difference.
• 5. Controlling
• Check progress and evaluate results on a regular basis.
• Define key performance indicators (KPI) and
• use reports to be able to quickly grasp if the project is on track.
• If things go sideways recognize early on and be able to take
countermeasures before bigger damage is done

12-Feb-25 41
 • 6. Software
• The role of project management software is commonly underestimated
• Software supports
– Secure and easy team collaboration
– Acts as the basis to give each team member access to their needed information.
• Professional and intuitive software minimizes
– the risk of mistakes and miscalculation and
– creates the best possible overview of all relevant KPI and
– displays important data reliably on all needed devices.
• Invest in a professional and specific tool to simplify the work and achieve
project success

12-Feb-25 42
 • Communication- The communication between team members plays
and important part.
• Lots of undesirable developments in projects could be prevented or at
least be discovered earlier with proper communication.
• Formal communication processes (meetings, documentation) as well
as informal processes.
• together outside the formal meetings,

12-Feb-25 43
 Project life cycle
The project life cycle is a structured process that takes a
project from start to finish. It's made up of phases that
help organize tasks, manage problems, and ensure the
project's success.
Phases of the project life cycle
• Initiation: Define the project and identify its scope
• Planning: Create a plan for the project
• Execution: Put the plan into action
• Monitoring and control: Track progress and identify
issues
• Closure: Bring the project to a close
 Classification/Types of projects
Projects can be classified based on various
factors including their size (small, medium,
large), type (new, maintenance, strategic),
application (software development,
construction), complexity, business value,
industry sector, and the level of risk involved,
allowing for categorization based on factors like
cost, duration, team size, and impact on the
organization.
 Classification
According to its objective:
• Production: Oriented at the production of a product or
service taking into consideration a certain determined
objective to be met by an organization.
• Social: Oriented at the improvement of the quality of
life of people. This can be in the form of rendering
corporate social responsibility (CSR) to the people.
• Educational: Oriented at the education of others. This
is always done to make them better.
• Community: Oriented at people too, however with
their involvement.
• Research: Oriented at innovation and the gaining of
knowledge to enhance the operational efficiency of an
organization.
 Classification
According to Project content:
• Construction: These are projects that have anything to do with the
construction of civil or architectural work. Predictive methods are
used along with agile techniques which will be explained later on.
Furthermore, construction is an engineering project and the
process of planning its execution must be painstakingly done to
achieve the desired outcome.
• IT: Any project that has to do with software development, IT
system, etc. The types of project management information systems
vary across the board, but in today’s world are very common.
• Business: These projects are involved with the development of a
business idea, management of a work team, cost management,
etc., and they usually follow a commercial strategy.
• Service or product production: These are projects that involve the
development of an innovative product or service, design of a new
product, etc. They are often used in the R & D department.
According to the source of capital:
• Public: Financing comes from Governmental
institutions.
• Private: Financing comes from businesses or
private incentives.
• Mixed: Financing comes from a mixed source
of both public and private funding.
According to complexity:
• Easy: A project is classified as easy when the relationships
between tasks are basic and detailed planning or
organisations are not required. A small work team and a
few external stakeholders and collaborators are common in
this case. The tasks of the projects can be undertaken by a
small team.
• Complicated: The project network is broad and
complicated. There are many task interdependencies. With
these projects, simplification where possible is everything.
The task of executing this type of project requires proper
planning. Cloud-based apps such as Sinnaps will immensely
help to simplify complicated projects by automatically
calculating the project’s best work path and updating any
changes introduced through its use of different types of
project management tools
 Project selection
Project selection is the process of evaluating and
choosing projects that best align with an organization's
goals. It's a key part of project portfolio management
(PPM), which connects project execution with business
strategy.
How is project selection done?
• Prioritize projects: Rank projects based on criteria like
feasibility, risk, and cost-benefit
• Use scoring models: Create a list of criteria, score each
criterion, and then rank projects based on the scores
• Use financial analysis: Calculate the payback period,
net present value, or internal rate of return
 Non-quantitative and scoring models
Non-quantitative project selection models, also
called "non-numeric" models, rely on qualitative
factors and subjective assessments rather than
numerical calculations, including methods like
the "sacred cow" model, "operating necessity,"
"competitive necessity," "product line
extension," and "comparative benefit," while
scoring models are a quantitative method that
uses a set of criteria with assigned weights to
evaluate and rank projects based on their
relative strengths across different factors.
 Examples of non-quantitative scoring
models:
Kano Model:
• This prioritizes product features based on customer satisfaction levels,
categorized as "basic needs" (must-haves), "performance" (expected
features), and "excitement" (delightful extras), with the focus on
understanding customer perception rather than numerical scores.
SWOT Analysis:
• Evaluates a project or strategy by analyzing its strengths, weaknesses,
opportunities, and threats, providing a qualitative assessment of its
potential without assigning numerical values to each factor.
Nominal Group Technique:
• Facilitates group decision-making by collecting individual ideas and then
prioritizing them through discussion and ranking, relying on consensus
rather than quantitative scoring.
Fuzzy Logic:
• Uses linguistic variables like "high" or "low" to represent criteria, allowing
for more flexible evaluations that don't rely on strict numerical
thresholds.
 Factors affecting selection of Project
When selecting a project, key factors to consider
include: cost, available resources, potential
benefits or ROI, project timeline, associated
risks, alignment with organizational goals,
feasibility, stakeholder management, regulatory
compliance, team capabilities, and project
scope; essentially balancing the potential gains
against the required investment and potential
challenges involved.
 Factors
• Breakdown of key factors:
• Financial factors:
– Project cost
– Return on investment (ROI)
– Budget constraints
• Strategic alignment:
– Alignment with organizational goals
– Strategic priorities
• Operational factors:
– Project timeline
– Required resources
– Team availability and expertise
• Risk assessment:
– Potential risks associated with the project
– Mitigation strategies
• Project scope:
– Project deliverables
– Complexity of the project
• Stakeholder considerations:
– Stakeholder needs and expectations
– Stakeholder buy-in
• Legal and regulatory aspects:
– Compliance with relevant regulations
– Legal considerations
• Other factors:
– Project feasibility
– Market potential
– Technological considerations
– Environmental impact
– Cultural factors
 Technology Selection
Technology selection is the process of choosing
the right technology for a project. It's an
important part of a company's technology
strategy.
Why is technology selection important?
• The technology you choose can affect the
project's profitability and viability.
• It's a chance to make conscious decisions and
trade-offs.
• It helps avoid finger-pointing when things go
wrong.
 How do you select technology for a
project?
• Define requirements: Start by defining the project's
requirements and objectives.
• Consider scalability: Make sure the technology can handle
growth in users, data, and traffic.
• Prioritize security: Choose technologies with strong
security features.
• Evaluate risk: Consider the potential risks associated with
each technology.
• Consider cost: Consider the potential expenses of each
technology.
• Consider practicality: Choose a technology that's practical
and suitable for the project.
• Consider appropriateness: Choose a technology that's
appropriate for the project's learners or objectives.
 Alternatives options
Tools like Asana, Trello, Smartsheet, Wrike, Jira,
Basecamp, ClickUp, Monday.com, Zoho Projects,
Airtable, depending on needs or features like
task management, collaboration, visual boards,
Gantt charts, and integrations with other
software; each platform offers different
strengths and functionalities to suit various
project types and team sizes.
Key points to consider when choosing
an alternative project management
tool:
• User interface: How easy is the platform to
navigate and learn?
• Collaboration features: Does it facilitate team
communication and task assignment effectively?
• Visual aids: Does it offer features like Kanban
boards, Gantt charts, or timelines for project
visualization?
• Integrations: Can it connect with other tools you
use, like email, calendars, and design software?
• Pricing structure: Does the pricing plan fit your
budget and team size?
 Techniques of long term forecasting
In project management, long-term forecasting
techniques typically include trend analysis, time
series analysis, econometric modeling, scenario
planning, the Delphi method, and technological
forecasting, which all rely on historical data and
expert judgment to predict future project trends
and outcomes over extended periods, like
several years or more.
 Key long-term forecasting techniques
Time Series Analysis:
• Trend analysis (straight-line method): Projects future
values based on a linear trend identified in historical
data, useful for simple cost or schedule projections.
• Moving average: Smooths out short-term fluctuations
by calculating the average of a set of recent data
points, revealing longer-term trends.
• Exponential smoothing: Assigns more weight to recent
data points when forecasting, giving greater emphasis
to recent trends.
• ARIMA (Autoregressive Integrated Moving
Average): A sophisticated time series model that
handles complex patterns in data by combining
autoregression, differencing, and moving averages
• Regression Analysis:
• Simple linear regression: Predicts a dependent variable
based on the relationship with one independent variable
• Multiple linear regression: Predicts a dependent variable
based on the relationship with multiple independent
variables
• Qualitative Techniques:
• Delphi method: Collects expert opinions through multiple
rounds of anonymous feedback to reach a consensus
forecast
• Scenario planning: Develops multiple potential future
scenarios by considering various factors and uncertainties
to assess potential risks and opportunities