software project management

21
Software Engineering Presentation Course Code: CSE 221 Date: July 30, 2015

Transcript of software project management

Software Engineering Presentation

Course Code: CSE 221

Date: July 30, 2015

Introduction

Presentated by –

Mohammad Kasedullah

ID: 141311042

5th Semester (5th Batch)

Department of CSE,

Varendra University, Rajshahi

Presentated to –

Meraj Ali

Lecturer,

Department of CSE,

Varendra University, Rajshahi

Topic to Discuss

Software Project Management

Index

Definition of software project management

Need of software project management

Steps of software project management

Software project manager

Software project management activities

Project Planning

Scope Management

Project Estimation

Project Estimation Techniques

Issue Management

Definition

Software project management is the art and science of planning and leading software projects. It is a sub-discipline of project management in which software projects are planned, implemented, monitored and controlled.

Need of Software Project Management

The underlying technology in software development changes and advances so frequently and rapidly that experience of one product may not be applied to the other one. All such business and environmental constraints bring risk in software development hence it is essential to manage software projects efficiently.

Need of Software Project Management

Software project management is essential to incorporate user requirements along with budget and time constraints.

Steps of Software Management

Traditionally there were five stages in software management.

1. Initiation

2. Planning and design

3. Execution and construction

4. Monitoring and controlling systems

5. Completion and finish point

Steps of Software Management

In recent times, the management of software has become a broader term and the steps or processes in the management of software have been redefined. The newer model includes the steps –

Interpersonal communication and conflict management and resolution: The software manager needs to ensure proper communication between the developers and between the developers and the clients. He also needs to resolve any conflicts that may arise.

Risk management: It is the process of measuring or assessing risk and then developing strategies to manage the risk. In general, the strategies employed include transferring the risk to another party, avoiding the risk, reducing the negative effect of the risk, and accepting some or all of the consequences of a particular risk.

Steps of Software Management

Requirements management: It is the process of identifying, eliciting, documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. Having identified these requirements they are then in a position to design a solution.

Change management: It is the process of identifying, documenting, analyzing, prioritizing and agreeing on changes to scope (project management) and then controlling changes and communicating to relevant stakeholders.

Steps of Software Management

Software configuration management: It is the process of identifying, and documenting the scope itself, which is the software product underway, including all sub-products and changes and enabling communication of these to relevant stakeholders.

Release management: It is the process of identifying, documenting, prioritizing and agreeing on releases of software and then controlling the release schedule and communicating to relevant stakeholders.

Software Project Manager

A software project manager is a person who undertakes the responsibility of executing the software project. Software project manager is thoroughly aware of all the phases of SDLC that the software would go through.

Software Project Manager

His responsibilities include –

Act as project leader

Lesion with stakeholders

Managing human resources

Setting up reporting hierarchy etc.

Defining and setting up project scope

Managing project management activities

Monitoring progress and performance

Risk analysis at every phase

Take necessary step to avoid or come out of problems

Act as project spokesperson

Activities of Software Project Management

Project Planning

Scope Management

Project Estimation

Project Planning

Software project planning is task, which is performed before the production of software actually starts. It is a set of multiple processes, which facilitates software production.

Scope Management

Define the scope

Decide its verification and control

Divide the project into various smaller parts for ease of management.

Verify the scope

Control the scope by incorporating changes to the scope

Project Estimation

Software size estimation

Effort estimation

Time estimation

Cost estimation

Project Estimation Techniques

There are two main models -

Line of Code Estimation is done on behalf of number of line of codes in the software product.

Function Points Estimation is done on behalf of number of function points in the software product.

Issue Management

Issues or problems occur from time to time and fixing them in a timely fashion is essential to achieve correctness of a system and avoid delayed deliveries of products.

Issues are often categorized in terms of severity levels. Different companies have different definitions of severities, but some of the most common ones are:

High

Medium

Low

Cosmetic

Issue Management

High: The bug or issue affects a crucial part of a system, and must be fixed in order for it to resume normal operation.

Medium: The bug or issue affects a minor part of a system, but has some impact on its operation. This severity level is assigned when a non-central requirement of a system is affected.

Low: The bug or issue affects a minor part of a system, and has very little impact on its operation. This severity level is assigned when a non-central requirement of a system (and with lower importance) is affected.

Cosmetic: The system works correctly, but the appearance does not match the expected one. For example: wrong colors, too much or too little spacing between contents, incorrect font sizes, typos, etc. This is the lowest severity issue.

End of presentation.Thank You!