Software Engineering :Project Management

SOFTWARE PROJECT
MANAGEMENT
Simmi S
Department of Computer Science(UG)
Kristu Jayanti College , Bangalore
Simmi S,Dept of CS UG

Software project management
Software project management is an essential part of software engineering.
Projects need to be managed because professional software engineering is
always subject to organizational budget and schedule constraints.
The project manager’s job is to ensure that the software project meets and
overcomes these constraints as well as delivering high-quality software.

The success criteria for project management
The success criteria for project management obviously vary from
project to project but, for most projects, important goals are:
1. Deliver the software to the customer at the agreed time.
2. Keep overall costs within budget.
3. Deliver software that meets the customer’s expectations.
4. Maintain a happy and well-functioning development team

Project Management
Most managers take responsibility at some stage for some or all of the
following activities:
Project planning Project managers are responsible for planning,
estimating and scheduling project development, and assigning people
to tasks.

Project Management
Reporting Project managers are usually responsible for reporting on
the progress of a project to customers and to the managers of the
company developing software.
Risk management Project managers have to assess the risks that may
affect a project, monitor these risks, and take action when problems
arise.

Project Management
People management Project managers are responsible for managing a
team of people. They have to choose people for their team and establish
ways of working that lead to effective team performance.
Proposal writing The first stage in a software project may involve writing
a proposal to win a contract to carry out an item of work.The proposal
describes the objectives of the project and how it will be carried out

Risk management
Risk management is one of the most important jobs for a project
manager.
Risk management involves anticipating risks that might affect the
project schedule or the quality of the software being developed, and
then taking action to avoid these risks

Related categories of risk:
Project risks: Risks that affect the project schedule or resources.
An example of a project risk is the loss of an experienced designer.
Finding a replacement designer with appropriate skills and experience
may take a long time and, consequently, the software design will take
longer to complete.

Product risks Risks that affect the quality or performance of the
software being developed.
An example of a product risk is the failure of a purchased component
to perform as expected.
 This may affect the overall performance of the system so that it is
slower than expected.

Business risks Risks that affect the organization developing or procuring
the software.
For example, a competitor introducing a new product is a business risk.
The introduction of a competitive product may mean that the assumptions
made about sales of existing software products may be unduly optimistic.

Process of risk management
Process of risk management is involved several stages:
1.Risk identification You should identify possible project, product, and business risks.
 2. Risk analysis You should assess the likelihood and consequences of these risks.
3. Risk planning You should make plans to address the risk, either by avoiding it or
minimizing its effects on the project.
4. Risk monitoring You should regularly assess the risk and your plans for risk
mitigation and revise these when you learn more about the risk.

The risk management process

Risk identification
Risk identification is the first stage of the risk management process
 It is concerned with identifying the risks that could pose a major threat to the
software engineering process, the software being developed, or the development
organization.
 Risk identification may be a team process where a team get together to
brainstorm possible risks.
 Alternatively, the project manager may simply use his or her experience to
identify the most probable or critical risks

Risk identification
There are at least six types of risk that may be included in a risk checklist:
1.Technology risks Risks that derive from the software or hardware technologies
that are used to develop the system.
2. People risks Risks that are associated with the people in the development team.
3. Organizational risks Risks that derive from the organizational environment where
the software is being developed.

Risk identification
4. Tools risks Risks that derive from the software tools and other
support software used to develop the system.
5. Requirements risks Risks that derive from changes to the customer
requirements and the process of managing the requirements change.
6. Estimation risks Risks that derive from the management estimates of
theresources required to build the system

Risk analysis
During the risk analysis process, you have to consider each identified
risk and make a judgment about the probability and seriousness of that
risk.
There is no easy way to do this. You have to rely on your own
judgment and experience of previous projects

Risk analysis

Risk analysis
The probability of the risk might be assessed as very low (10%), low
(10–25%), moderate (25–50%), high (50–75%), or very high (75%).
 The effects of the risk might be assessed as catastrophic (threaten
the survival of the project), serious (would cause major delays),
tolerable (delays are within allowed contingency), or insignificant.

Risk planning
The risk planning process considers each of the key risks that have
been identified, and develops strategies to manage these risks.
 For each of the risks, you have to think of actions that you might take
to minimize the disruption to the project if the problem identified in
the risk occurs.

Risk monitoring
It is the process of checking that your assumptions about the product,
process, and business risks have not changed.
You should regularly assess each of the identified risks to decide
whether or not that risk is becoming more or less probable

Managing people
The people working in a software organization are its greatest assets. It costs a lot
to recruit and retain good people and it is up to software managers to ensure that
the organization gets the best possible return on its investment.
In successful companies and economies, this is achieved when people are
respected by the organization and are assigned responsibilities that reflect their
skills and experience.
It is important that software project managers understand the technical issues that
influence the work of software development

Critical factors in people management:
 Consistency People in a project team should all be treated in a comparable way.
 Respect Different people have different skills and managers should respect these
differences
Inclusion People contribute effectively when they feel that others listen to them
and take account of their proposals. It is important to develop a working
environment where all views, even those of the most junior staff, are considered.
 Honesty As a manager, you should always be honest about what is going well
and what is going badly in the team

Motivating people
As a project manager, you need to motivate the people that work with
you so that they contribute to the best of their abilities
Motivation means organizing the work and the working environment
to encourage people to work as effectively as possible..

Team Work
Most professional software is developed by project teams that range in size from two to several
hundred people.
large teams are usually split into a number of groups.
Each group is responsible for developing part of the overall system.
When small groups are used, communication problems are reduced. Everyone knows everyone else
and the whole group can get around a table for a meeting to discuss the project and the software
that they are developing.
 Putting together a group that has the right balance of technical skills, experience, and personalities
is a critical management task. A good group is cohesive and has a team spirit.

Software Pricing
In principle, the price of a software product to a customer is simply the cost
of development plus profit for the developer.
In practice, however, the relationship between the project cost and the price
quoted to the customer is not usually so simple.
When calculating a price, you should take broader organizational,
economic, political, and business considerations into account, such as those
shown in following table

Software Pricing

THANK YOU

Software Engineering :Project Management

More Related Content

Similar to Software Engineering :Project Management (20)

More from simmis5 (11)

Recently uploaded (20)

Software Engineering :Project Management