---
Video Title: Software Project Management Activities
Description: Software Project Management Activities
Watch more Videos at https://www.tutorialspoint.com/videotutorials/index.htm
Lecture By: Mr. Arnab Chakraborty, Tutorials Point India Private Limited
---

Software project management activities.

So, we have defined project in the earlier
videos.

So, project is nothing but one temporary
endeavor.

At the end of the project, we are going to
get unique service, product or result.

That means a project will have a certain
start time and a certain end time or

certain start date or a certain end date.

So, a project cannot go forever.

Whenever a project executes, we divide the
project into multiple phases.

Each and every phase will be consisting of
multiple different tasks and activities.

It is a wise decision not to break a task
into sub-tasks into a very minute level.

If we go on dividing a task into sub-tasks
into a very minute level, then the project

will get very much difficult to get
monitored and to get controlled.

So, now let us concentrate on the software
project management activities.

So, software project management comprises
of number of activities and which contains

planning of project, deciding the scope of
the software product and estimation of

cost in various terms and scheduling of
tasks and events and resource management.

So, these are the prime operations which
will be conducted in our project management.

We know that a project
will be consisting of

multiple different phases
as we discussed earlier.

And each and every phase will be
consisting of certain activities and

activities will be comprising of certain
tasks.

So, now all these tasks should be
scheduled in a proper way.

In between two tasks, there are four
different task relationships.

That is one is start to finish.

That means, one task will start after
finishing of the second task.

Then finish to start, one task will
finish.

Then another task will start.

Start to start, two tasks will start on
the same date and time.

But they may be having different
durations.

So, they may have different end dates.

And another one is the finish Finish to
finish, that is both the two tasks will be

finished on the same date and time,
but as they might be having different

durations, so they can have different
start dates.

So, start to finish, finish to start,
start to start and finish to finish.

So, there are four task relationships
between these tasks and activities.

So, this task scheduling is a very important
job in our software project management.

And also, we shall do the estimation of
the cost of the project.

We know that tasks will not have any cost.

A task will not have any cost.

The resources will have the cost.

So, when
the resources will get assigned on to a

certain task, then the
task will have some cost.

Let us suppose, there is a particular
developer who is charging X dollar per hour.

That is one task which is having a
duration of 10 hours.

So, when this particular developer will be
assigned to that very task, then the task

will have a cost of 10 into X dollars.

So, in this way, the task will have the
cost.

So, in case of
estimation, there is an estimation of the

cost of the
project will be done in this similar way.

And also, we are supposed to do the
scheduling of task and events.

And then, resource management.

In case of resource management,
we are having mainly two issues.

One is the over-allocation and another one
is the under-allocation.

So, what is the difference between
over-allocation and under-allocation?

A same manpower cannot be assigned on two
tasks on the same date and time.

So, that is known as the over-allocation.

And under-allocation means, a resource is
sitting But he or she is getting paid.

But the resource is not getting utilized.

And that is known as the under allocation.

So, all this over allocation, under
allocations, all these things are to be

resolved in our software project
management activities.

So, after considering all these things.

So, let us go for what are the main issues
are there.

So, project management activities may
include project

planning, scope Scope
management and project estimation.

So, we are going to have a separate video
on project estimation.

In this video, we are going to discuss on
this project planning and scope management.

At first, we are going to discuss project
planning.

So, software
project planning is task which is performed

before the production of the software
actually starts.

So, that is our project planning.

We do the planning before starting the
project.

We usually estimate So, we are going to
get the task durations.

We try to get what is the nature of the
task.

And we try to do the scheduling of all
these tasks.

And then the project would get initiated.

It is there for the software production,
but involves no concrete activity that has

any direct connection with the software
production.

Rather, it is a set of multiple processes
that facilitates the software production.

So, in this way, we are going to do the
project planning.

Whenever we do the project planning,
while estimating the task durations,

we should remain very much cautious.

Because we should not overestimate the
task durations.

Also, we should not do the underestimate.

What will happen if we do some wrong
during the project planning?

When the project will be in execution,
the project will be missing the deadlines.

It will be going to fall over budget,
under budget.

It may also put some anomalies and some
other tasks are getting delayed due to the

elongation of certain task which was
estimated with a shorter duration.

Next one is the scope management.

So, it defines the scope of the project
that includes all the activities process

need to be done in order to make a
derivable software product.

So, scope means different type of
features, specifications which were

decided during the recommend analysis
phase, during the analysis phase,

software analysis phase and those recommends,
those features are to be implemented.

So, they will be treated as a scope for
the respective software.

Scope management is essential.

It creates boundaries of the project by
clearly defining

what would be done in the project
and what would not be done.

So, which feature, which scope has to be
implemented and which scope should not get

implemented, would not get implemented.

So, that boundary will be decided in this
scope management.

This takes project to certain limited and
quantifiable tasks which can easily be

documented and in turn avoids cost and
time overrun.

So, always use, we are having a constraint
that is the cost constraint.

We are having the constraint called the
quality constraint and another one is the

known as the time constraint.

So, time, cost and quality.

So, in our
earlier video, we have discussed this one

that is the triple
constraint in our project management.

So, during project
scope management, it is

necessary to,
so these are the points I have listed.

So, define the scope, decide its
verification and control and divide.

Provide the project into various smaller
parts so that it will be easier for us to

do the management and verify the scope
each and every scope is to be verified and

it has to be matched with the requirement
which we gathered at the early stage of

the software development and control the
scope by incorporating changes to the scope.

So, in this way
we are going to have this is this is the

least of necessary
things to be done in our scope management.

So, let us go for the next video where we
will be going for cost estimations.

Thanks for watching this.

TutorialsPoint.com.

Simply easy learning.