811720104049-Keerthana S

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 14

SOFTWARE PROJECT

MANAGEMENT TECHNIQUES

PRESENTED BY,
KEERTHANA S
INTRODUCTION TO SOFTWARE
PROJECT MANAGEMENT :
• Software Project Management (SPM) is a
proper way of planning and leading software
projects. It is a part of project management in
which software projects are planned,
implemented, monitored, and controlled.
Need for Software Project Management:
Software is a non-physical product. Software
development is a new stream in business and
there is very little experience in building
software products. Most of the software
products are made to fit clients’
requirements.
TYPES OF MANAGEMENT:
• Conflict Management: Conflict management
is the process to restrict the negative features
of conflict while increasing the positive
features of conflict. The goal of conflict
management is to improve learning and
group results including efficacy or
performance in an organizational setting.
Properly managed conflict can enhance group
results.
• Risk Management: Risk management is the
analysis and identification of risks that is
followed by synchronized and economical
implementation of resources to minimize,
operate and control the possibility or effect
of unfortunate events or to maximize the
realization of opportunities.
• Requirement Management: It is the
process of analyzing, prioritizing, tracking,
and documenting requirements and then
supervising change and communicating to
pertinent stakeholders. It is a continuous
process during a project.
• Change Management: Change management
is a systematic approach for dealing with the
transition or transformation of an
organization’s goals, processes, or
technologies. The purpose of change
management is to execute strategies for
effecting change, controlling change, and
helping people to adapt to change.
• Software Configuration Management:
Software configuration management is the
process of controlling and tracking changes in
the software, part of the larger cross-
disciplinary field of configuration
management. Software configuration
management includes revision control and
the inauguration of baselines.
ACTIVITY PLANNING AND
RISK MANAGEMENT
OBJECTIVE OF ACTIVITY
PLANNING:
• Feasibility assessment : Is the project
possible within required timescales and
resource constraints? It is not until we have
constructed a detailed plan that we can
forecast a completion date with any
reasonable knowledge of its achievability.
• Resource allocation : What are the most
effective ways of allocating resources to the
project? When should the resources be
available? The project plan allows us to
investigate the relationship between
timescales and resource availability
• Detailed costing : How much will the
project cost and when is that expenditure
likely to take place? After producing an
activity plan and allocating specific
resources, we can obtain more detailed
estimates of costs and their timing.
• Motivation : Providing targets and being
seen to monitor achievement against
targets is an effective way of motivating
staff, particularly where they have been
involved in setting those targets in the first
place.
• Coordination : When do the staff in different
departments need to be available to work on
a particular project and when do staff need
to be transferred between projects? The
project plan, particularly with large projects
involving more than a single project team,
provides an effective vehicle for
communication and coordination among
teams.
• General Idea : Activity planning and
scheduling techniques place an emphasis on
completing the project in a minimum time at
an acceptable cost
PROJECT MANAGEMENT
AND CONTROL
• Monitoring and Controlling are processes
needed to track, review, and regulate the
progress and performance of the project. It
also identifies any areas where changes to the
project management method are required
and initiates the required changes.
MONITORING AND CONTROL
PROCESSING GROUP :
• Monitor and control project work : The
generic step under which all other monitoring
and controlling activities fall under.
• Perform integrated change control : The
functions involved in making changes to the
project plan. When changes to the schedule,
cost, or any other area of the project
management plan are necessary, the program
is changed and re-approved by the project
sponsor.
• Validate scope : The activities involved with
gaining approval of the project's deliverables.
• Control scope : Ensuring that the scope of
the project does not change and that
unauthorized activities are not performed as
part of the plan (scope creep).
• Control schedule : The functions involved
with ensuring the project work is performed
according to the schedule, and that project
deadlines are met.
THANK YOU

You might also like