Chapter: 4

Project Management

Course Instructor
Er. ANUJ GHIMIRE
Project Management
Project management is the application of processes,
methods, skills, knowledge and experience to achieve
specific project objectives according to the project
acceptance criteria within agreed parameters.
Project management has final deliverables that are
constrained to a finite timescale and budget
A key factor that distinguishes project management
from just 'management' is that it has this final
deliverable and a finite time span, unlike
management which is an ongoing process. 
Component of Project Management
Defining the reason why a project is necessary
Capturing project requirements, specifying quality of the
deliverables, estimating resources and timescales
Developing and implementing a management plan for the project
Leading and motivating the project delivery team.
Managing the risks, issues and changes on the project.
Monitoring progress against plan.
Managing the project budget.
Maintaining communications with stakeholders and the project
organisation.
Closing the project in a controlled fashion when appropriate.
Advantages of Project Management
Having expertise of project process and different
knowledge area will be much helpful during project
management
Knowing how to use the techniques to finish your
projects in time and estimated budget comes with
innumerable benefits.
However, there are five immediate benefits of good
project management.
Advantages of Project Management
Improves Productivity and Reduces Costs and
Workload
Improves Collaboration
Improves Customer Satisfaction
Helps You to Improve Your Performance
Helps with Problem Resolution
Advantages of Project Management
Improves Productivity and Reduces Costs and Workload:
 The ultimate goal of project management and planning is
efficiency.
 We want to do as much as possible in as little time as possible.

 Good management provides better path to perform project

activities.
 It helps in timely completion of projects and yields greater
productivity.
 Once you create processes, templates, and procedures, you’ll be
able to reuse them with every project and know exactly what you
can count on.
 This will automatically mitigate risks and improve your
efficiency.
Advantages of Project Management
Improves Collaboration:
 If everything related to your project is structured and team
members know exactly what they need to be doing at any
given time, it’ll be much easier to manage them.
 Also, positive result from the project inspire the team
members to perform better in future.
 Collaboration can be improved by:
 Using PM tools to keep everyone on the same page.

 Defining your own and everyone else’s roles clearly and

accurately.
 Understanding your stakeholders and creating communication

plans
Advantages of Project Management
Improves Customer Satisfaction:
Completing project on time and within budget make
customer satisfied.
It acts as a base to build a strong customer network and
increase organizational trust towards the customer.
This is how we achieve customer satisfaction:
 Understand customers’ expectations and communicate clearly.
 Prepare the necessary documentation.
 Monitor risks and prepare a plan for mitigating them.
Advantages of Project Management
Helps You to Improve Your Performance:
When you have an organized way of tracking your
performance and results from project to project, you’ll
be able to understand it.
And if you can measure it, you can improve it.
It can be done with:
 Use a central tool for project and task management, tracking,
and reporting.
 Create post-completion processes
 Create a document with all the lessons you’ve learned 
 Implement Changes
Advantages of Project Management
Helps with Problem Resolution:
 Finally, there are always problems in projects. After all, there’s a
lot of moving parts involved.
 However, when you’re using a PM methodology, you know exactly
how to approach a problem.
 As all the members and their skills are properly analyzed, the
possible risks can be detected and mitigated in time.
 For this:
 Establish risk management processes.

 Note every change and problem in your change/issue log.

 Create communication plans

 Update your project and task plans with every new accepted change

to understand how they’ll reflect on the entirety of the project.

Project Management as Per PMI
Project management is the application of knowledge,
skills, tools, and techniques to project activities to meet
the project requirements.
It has always been practiced informally, but began to
emerge as a distinct profession in the mid-20th
century. 
PMI’s A Guide to the Project Management Body of
Knowledge (PMBOK® Guide) is the standard guidelines
for the project management planning and execution.
It is a strategic competency for organizations, enabling
them to tie project results to business goals.
Project Management as Per PMI
PMI defines 5 processes and 10 knowledge areas for
the project management.
5 Processes are:
 Initiation
 Planning
 Execution
 Monitoring & Controlling
 Closure
Process Groups as Per PMI
PMBOK as Per PMI
Characteristics of Project Life Cycle
The project life cycle serves to define the beginning
and the end of a project.
For example, when an organization identifies an
opportunity that it would like to respond to, it will
often authorize a feasibility study to decide if it should
undertake a project.
The project life cycle definition will determine
whether the feasibility study is treated as the first
project phase or as a separate, stand-alone project.
Characteristics of Project Life Cycle
The project life cycle definition will also determine
which transitional actions at the end of the project are
included and which are not.
In this manner, the project life cycle definition can be
used to link the project to the ongoing operations of
the performing organization.
Characteristics of Project Life Cycle
Most project life cycle descriptions share a number of
common characteristics:
Cost and staffing levels are low at the start, higher
towards the end, and drop rapidly as the project draws to
a conclusion. This pattern is illustrated as:
Characteristics of Project Life Cycle
The probability of successfully completing the project is lowest,
and hence risk and uncertainty are highest, at the start of the
project.
 The probability of successful completion generally gets
progressively higher as the project continues.
The ability of the stakeholders to influence the final
characteristics of the project product and the final cost of the
project is highest at the start and gets progressively lower as the
project continues.
A major contributor to this phenomenon is that the cost of
changes and error correction generally increases as the project
continues.
Representative Project Life Cycle
For this we look to different types of project and focus
on the different activities done in different phases of
the project life cycle.
Example of Software Development:
Proof-of-concept cycle: Capture business
requirements, define goals for proof-of-concept, produce
conceptual system design, design and construct the
proof-of-concept, produce acceptance test plans,
conduct risk analysis and make recommendations.
Example of Software Development
First build cycle: Derive system requirements, define
goals for first build, produce logical system design,
design and construct the first build, produce system
test plans, evaluate the first build and make
recommendations.
Second build cycle: Derive subsystem requirements,
define goals for second build, produce physical design,
construct the second build, produce system test plans,
evaluate the second build and make
recommendations.
Example of Software Development
Final cycle: Complete unit approach for software
requirements, final development.
design, construct final
build, perform unit,
subsystem, system, and
acceptance tests.
Spiral model for software
development with four
cycles and four quadrants
can be one representative
Construction Project
Feasibility: Project formulation, feasibility studies, and
strategy design and approval. A go/no-go decision is made
at the end of this phase.
Planning and Design: Base design, cost and schedule,
contract terms and conditions, and detailed planning.
Major contracts are let at the end of this phase.
Production: Manufacturing, delivery, civil works,
installation, and testing. The facility is substantially
complete at the end of this phase.
Turnover and Start-up: Final testing and maintenance.
The facility is in full operation at the end of this phase.
Construction Project
Construction project life cycle can be illustrated as:
Pharmaceuticals Project
Discovery and Screening: Includes basic and applied
research to identify candidates for preclinical testing.
Preclinical Development: Includes laboratory and
animal testing to determine safety and efficacy as well as
preparation and filing of an Investigational New Drug
(IND) application.
 Registration(s) Workup: Includes Clinical Phase I, II,
and III tests as well as preparation and filing of a New
Drug Application (NDA).
Post-submission Activity: Includes additional work as
required to support Food and Drug Administration review
of the NDA.
Pharmaceuticals Project
Project life cycle for pharmaceutical new product
development can be:
IT Product Development Life cycle
Software Development Life Cycle (SDLC) is a process used by
the software industry to design, develop and test high quality
software's.
The SDLC aims to produce a high-quality software that meets
or exceeds customer expectations, reaches completion within
times and cost estimates.
SDLC is the acronym of Software Development Life Cycle. It is
also called as Software Development Process.
SDLC is a framework defining tasks performed at each step in
the software development process.
ISO/IEC 12207 is an international standard for software lifecycle
processes.
It aims to be the standard that defines all the tasks required for
developing and maintaining software
IT Product Development Life cycle
SDLC is a process followed for a software project,
within a software organization.
It consists of a detailed plan describing how to
develop, maintain, replace and alter or enhance
specific software.
The life cycle defines a methodology for improving the
quality of software and the overall development
process.
IT Product Development Life cycle
SDLC is a process followed for a software project,
within a software organization.
It consists of a detailed plan describing how to
develop, maintain, replace and alter or enhance
specific software.
The life cycle defines a methodology for improving the
quality of software and the overall development
process.
System Development Life Cycle (SDLC) is a
conceptual model which includes policies and
procedures for developing or altering systems
throughout their life cycles.
IT Product Development Life cycle
SDLC is used by analysts to develop an information
system.
SDLC includes the following activities :
Requirements
Design
Implementation
Testing
Deployment
Operations
Maintenance
IT Product Development Life cycle
Phases of SDLC
Systems Development Life Cycle is a systematic
approach which explicitly breaks down the work into
phases that are required to implement either new or
modified Information System.
 Planning
 Analysis
 Design
 Implementation
 Testing

 Deployment
 Maintenance
IT Product Development Life cycle
Planning :
In the Planning phase, project leaders evaluate the terms
of the project. This includes calculating labor and
material costs, creating a timetable with target goals, and
creating the project’s teams and leadership structure.
Planning can also include feedback from stakeholders.
Also need to get feedback from potential customers,
developers, subject matter experts, and sales reps.
Planning should clearly define the scope and purpose of
the application.
It also sets boundaries to help keep the project from
expanding or shifting from its original purpose.
IT Product Development Life cycle
Analysis :
In feasibility analysis, your team ensures that the project
requirements help the end-user of the system.
Gathering requirements means talking to stakeholders and
looking at as much relevant data as possible. At all times, you’ll
want to consider the users and how workable the feature is.
The outputs from the requirements analysis stage will vary
depending on the methodology you are using.
 Regardless of whether your team is working with a formal
requirements document or a list of tickets, everyone has to
understand each need.
At this stage, architects, developers, and product managers
work together with relevant stakeholders.
IT Product Development Life cycle
Design:
The Design phase models the way a software application will
work. Some aspects of the design include:
 Architecture – Specifies programming language, industry practices,
overall design, and use of any templates.
 User Interface – Defines the ways customers interact with the

software, and how the software responds to input.

 Platforms – Defines the platforms on which the software will run, such

as Apple, Android, Windows version, Linux, or even gaming consoles.

 Communications – Defines the methods that the application can

communicate with other assets, such as a central server or other

instances of the application.
 Security – Defines the measures taken to secure the application, and

may include SSL traffic encryption, password protection, and secure

storage of user credentials.
IT Product Development Life cycle
Implementation:
 The implementation phase involves putting the
project plan into action.
 It’s here that the project manager will coordinate and
direct project resources to meet the objectives of the
project plan.
 As the project unfolds, it’s the project manager’s job
to direct and manage each activity, every step of the
way.
 That’s what happens in the implementation phase of
the project life cycle: you follow the plan you’ve put
together and handle any problems that come up.
IT Product Development Life cycle
Testing:
 It is the critical to test an application before making it available
to users. Much of the testing can be automated, like security
testing. 
 Other testing can only be done in a specific environment –
consider creating a simulated production environment for
complex deployments.
 Testing should ensure that each function works correctly.
Different parts of the application should also be tested to work
seamlessly together performance test, to reduce any hangs or
lags in processing.
 The testing phase helps reduce the number of bugs and
glitches that users encounter.
 This leads to a higher user satisfaction and a better usage rate.
IT Product Development Life cycle
Deployment:
 In the deployment phase, the application is made available to
users.
 Many companies prefer to automate the deployment phase.
This can be as simple as a payment portal and download link
on the company website.
 It could also be downloading an application on a
Smartphone.
 Deployment can also be complex. Upgrading a company-
wide database to a newly-developed application is one
example.
 Because there are several other systems used by the database,
integrating the upgrade can take more time and effort.
IT Product Development Life cycle
Maintenance:
 At this point, the development cycle is almost finished.
The application is done and being used in the field.
 The Operation and Maintenance phase is still important,
though. In this phase, users discover bugs that weren’t
found during testing.
 These errors need to be resolved, which can spawn new
development cycles.
 In addition to bug fixes, models like Iterative
development plan additional features in future releases.
 For each new release, a new Development Cycle can be
launched.
IT Product Development Life cycle
Different Software Development Models are in
practice, some of them are:
Waterfall Model
Prototype Model
Iterative Model
Spiral Model
Agile Model, and so on.
Product Life Cycle and Project Life Cycle
Product life cycle and project life cycle sound quite
similar, but in fact, are very different from one another.
A marketing project can impact a product's life cycle,
but otherwise these two concepts are essentially
unrelated.
 However, understanding what each one is and having
some strategies for their use will help you to integrate
both into your business plans with maximum
effectiveness
Product Life Cycle
The product life cycle represents the amount of
revenue a product generates over time, from its
inception to the point where it is discontinued.
The five stages of a product's life are:
 Development
 Introduction
Growth
Maturity, and
Decline.
Product Life Cycle
In the development stage, the product isn't yet being
sold, so there is no revenue.
During introduction, sales are small as people begin to
try the product.
Sales will increase during the growth phase, peak
during maturity, and eventually decline as the market
shifts or better alternatives become available.
There is no set time span for a given stage; the entire
cycle may last only months, or a product like the
refrigerator may remain in the maturity phase for
decades.
Project Life Cycle
A project life cycle measures the work that goes into a project from
beginning to end.
The phases in project life cycle are initiation, planning, execution,
and closure.
During initiation, a business case and goals are created, and
resources are assigned.
During planning, the team researches solutions to reach the project
goals and creates a plan and timeline to complete the project.
Execution involves following each step on the project plan and
adjusting as necessary along the way.
Finally, in the closure phase, the project's final details are wrapped
up and deliverable items like final reports are given to the
appropriate parties.
Role and Responsibilities of Project
members
Different level of manpower of human resources are
involved during the development of the project.
Any project can not move in required direction
without each of its key team members.
The key team members are project manager, project
team member, project sponsor, executive sponsor and
business analyst.
All of these key members have their own roles and
responsibility for the smooth running of project and
organization as well.
Role and Responsibilities of Project
members
Project Manager
Develop a project plan
Manage deliverables according to the plan
Recruit project staff
Lead and manage project team
Determine methodology used on the project
Establish a project schedule and determine each phase
Assign task to team members
Role and Responsibilities of Project
members
Project Team Member
Contribute to overall project objectives
 Complete individual deliverables
Provide expertise
 Work with users to establish business needs
 Document the process
Role and Responsibilities of Project
members
Project Sponsor
Approve project budget
Ensure resource availability
Executive Sponsor
Approve changes to project scope
Provide additional funds for scope changes
Approve project deliverables
Role and Responsibilities of Project
members
Business Analyst
Gather requirements
Document technical and business requirements
Verify that project deliverables meet the requirements