Software Project

Management
Software Project Management
 Course Code : INT411

 TextBook:Software Project Management By Bob

Hughes and Mike Cotterell, 5thEdition, Tata
McGraw Hill.

 Credits: 3
Chapter 1
Introduction to

SOFTWARE
PROJECT
MANAGEMENT
What is Software?
 Collection of computer programs and related data
(associated documentation)
 Projects to produce software are worthwhile only
if they satisfy real needs of stakeholders.

 Identifying these objectives and checking that they

are met is the basis of successful project.
What is Project?
 Non-routine Tasks
 Planning is required
 Aiming at a specific target
 Work carried out for a customer
 Involving several specialism
 Made up of several different phases
 Constrained by time and resources
 Large and/or complex
 Project size is important.
What are constraints on a project?
 Projectsare constrained by three factors: time,
budget and quality.
What is management?
• Planning – deciding what is to be done
• Organizing – making arrangements
• Staffing – selecting the right people for the job
• Directing – giving instructions
• Monitoring – checking on progress
• Controlling – taking action to remedy hold-ups
• Innovating – coming up with solutions when
problems emerge
Cont…
• Representing – presenting to clients, users,
developers and other stakeholders
Manager Must Know Project
Management Skills
 Building a work break down structure
 Documenting Plans
 Estimating Cost
 Managing Risks
 Scheduling
 Tracking Project Progress
Manager Must Know People
Management Skills
 Appraising Performance: Evaluating Team
 Holding Effective meetings
 Selecting a team
 Presenting Effectively: Good communication
skills
 Leadership
Project Management v/s Software
Project Management(How Software
Projects are different from other
projects?)
 Invisibility.

 Complexity.

 Flexibility.
Activities Covered Under
SPM(SDLC Phases)
 Feasibility Study
 Planning
 ProjectExecution
 Requirements Analysis
 SRS
 Design
 Coding
Cont…
 Verification and Validation

 Implementation/Installation

 Maintenance and support

Categorizations of Software Projects
 Informationvs Embedded
 Open vs Closed systems
 Socio-Technical Systems
What is Management?
 Planning
 Organising
 Staffing
 Directing
 Monitoring
 Controlling
 Innovating
 Representing
 Plan, Methods and Methodologies
• Plan: A way of doing something, especially a systematic way;
implies an orderly logical arrangement
A Plan consists of:
– Its start and end dates
– Who will carry it out
– What tools and materials will be used

• Method: takes the plan and convert it to real activities.

• A groups of methods or technique are known as

methodologies
Stakeholder
 People having stake or interest in the project.

 Three types of stakeholder:

 Internal to the Project team

 External to the Project team

 Internalto the organization
 External to the organization
Objectives and Goals (SMART)
 Specific: Effective objectives must be concrete
and well defined.
 Measureable: Measures of Effectiveness.
 Achievable: with in the power of individual.
 Relevant: should be relevant to the true purpose.
 Time Constrained: Defined point of time.
Problems with Software Projects.
 Poor estimates and plans
 Lack of quality standards and measures
 Lack of guidance about making organizational
decisions
 Lack of techniques to make progress visible
 Poor role definition- who does what?
 Incorrect success criteria
 Inadequate specification of work
 Management ignorance of IT
 Lack of standards
 Lack of up-to date documentation
 Late delivery
 Deadline pressure
 Remote management
 Lack of training
 Lack of quality control
 Lack of communication…………..etc