Software project management (SPM)

lecture#6
 Activity Planning
• What is an activity in SPM
• 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 next project stage. Taken together as a series, the
activities will result in the final deliverable. Each activity has a defined
start and end, as well as a deadline or time period within which it
must be completed. Or
• Software project management consists of many activities, that
includes planning of the project, deciding the scope of product,
estimation of cost in different terms, scheduling of task, etc.
 Activity Planning cont..
The list of activities are as follows:
• Project planning
• Project resource management
• Scope management
• Estimation management
• Project risk management
• Scheduling management
• Project communication management
 Activity Planning cont..
• Configuration management
1. Project planning
it is a set of multiple processes, or we can say that it a task that
performed before the construction of the product starts
2. Scope management
it describe the scope of the project. Scope management is important
because it clearly defines what would do and what would not. Scope
management create the project to contain restricted and quantitative
tasks, which may merely be documented and successively avoids price
and time overrun.
 Activity Planning cont..
3. Estimation management: This is not only about cost estimation
because whenever we start to develop software, but we also figure out
their size(line of code), efforts, time as well as cost.
• If we talk about the size, then Line of code depends upon user or
software requirement.
• If we talk about effort, we should know about the size of the software,
because based on the size we can quickly estimate how big team
required to produce the software.
• If we talk about time, when size and efforts are estimated, the time
required to develop the software can easily determine.
 Activity Planning cont..
And if we talk about cost, it includes all the elements such as:
• Size of software
• Quality
• Hardware
• Communication
• Training
• Additional Software and tools
• Skilled manpower
 Activity Planning cont..
4. Scheduling Management: Scheduling Management in software refers to all
the activities to complete in the specified order and within time slotted to each
activity. Project managers define multiple tasks and arrange them keeping
various factors in mind.
• For scheduling, it is compulsory -
• Find out multiple tasks.
• Divide time into units.
• Assign the respective number of work-units for every job.
• Calculate the total time from start to finish.
• Break down the project into modules.
 Activity Planning cont..
5. Project Resource Management: In software Development, all the
elements are referred to as resources for the project. It can be a human
resource, productive tools, and libraries.
• Resource management includes:
• Create a project team and assign responsibilities to every team
member
• Developing a resource plan is derived from the project plan.
• Adjustment of resources.
 Activity Planning cont..
6. Project Risk Management: Risk management consists of all the
activities like identification, analyzing and preparing the plan for
predictable and unpredictable risk in the project.
• Several points show the risks in the project:
• The Experienced team leaves the project, and the new team joins it.
• Changes in requirement.
• Change in technologies and the environment.
• Market competition.
 Activity Planning cont..
7. Project Communication Management: Communication is an
essential factor in the success of the project. It is a bridge between
client, organization, team members and as well as other stakeholders of
the project such as hardware suppliers.

• From the planning to closure, communication plays a vital role. In all

the phases, communication must be clear and understood.
Miscommunication can create a big blunder in the project.
 Activity Planning cont..
8. Project Configuration Management: Configuration management is
about to control the changes in software like requirements, design, and
development of the product.
The Primary goal is to increase productivity with fewer errors.
• Some reasons show the need for configuration management:
• Several people work on software that is continually update.
• Help to build coordination among suppliers.
• Changes in requirement, budget, schedule need to accommodate.
• Software should run on multiple systems.
 Risk Management
What is Risk?
• In software engineering risk means the probability of occurrence of
some uncertain events which may cause some kind of lose to the
organization in which software is working.

• We always have risks in our real life, some time we take risks to
achieve something good and some time we make some strategies to
overcome the risk.
 Risk Management cont..
Risk Management
• When we plan a project in the software field we also think about the
possible risk in the project.
• After identifying the risks in the project we check its probability
(chance of occurrence of risk in the project).
• After that on third step we check level of impact of a particular risk on
the project.
• Now we will see all the above mention steps one by one in detal.
 Risk Management cont..
1. Risk Identification
• This step mainly based on the brainstorming technique.
In this technique all the stakeholders set together and think about all
the possible risks of the project.

It this step we list down all the possible risks as well.

This is the first step in the risk management process but all the
creative thinking work happens here.
 Risk Management cont..
2. Analysis and prioritization of Risks
• At this step first of all we identify the reason causing the risk in the
project.
• After identifying the reason of risk we identify the impact of the risk
on the project.
• Because all of the necessary of action you may take on the risk
depends on how much a risk have impact on the over all project.
• For doing something good and extra ordinary some time you take
small risks, not all risks are to avoid.
 Risk Management cont..
• We also identify the probability of the risk here.
3. Risk Avoidance
• Purpose of this stage is to some how avoid risk.

• But some time we cannot avoid the risk completely, if this is the case
so we try to reduce the impact of the risk to some extent.
 Risk Management cont..
4. Monitoring
• If you are on the stage 4 of risk management that means the risk has
been identified, its impact has been checked, probability has been
checked and all the necessary actions has been taken to avoid or
mitigate it.

• Now it is the time to keep an eye on the avoided or mitigated risk, this
just to avoid its reoccurrence in the project.
THANKS