Scribd
Upload
17 views15 pages

Software Project Management1

The document provides an overview of software project management, defining software and its characteristics compared to programs. It outlines the role of software, the definition of a project, and the complexities involved in software projects, emphasizing the importance of management activities such as planning, organizing, and monitoring. Additionally, it introduces the W5HH principle, which serves as a framework for project managers to address key questions related to project development and resource allocation.

Uploaded by

md nehal saim
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
17 views15 pages

Software Project Management1

The document provides an overview of software project management, defining software and its characteristics compared to programs. It outlines the role of software, the definition of a project, and the complexities involved in software projects, emphasizing the importance of management activities such as planning, organizing, and monitoring. Additionally, it introduces the W5HH principle, which serves as a framework for project managers to address key questions related to project development and resource allocation.

Uploaded by

md nehal saim
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 15

Software Project

Management
Software - Definition
• Computer Programs along with associated
documentation
And is developed for
• Either a single customer as per his
requirements OR
• For General market i.e. it is generic in nature
and is sold to different customers thru
different channels
Program Vs Software
Characteristics Program Software
Size Small Large
Users (Numbers) Self (Few) Others (Large)
Users (Background) Similar Varied
Functionality Limited Large
Interfaces OK Well Designed
Environment Single Several
System Used by itself Used with others
Documentation Minimal Exhaustive
Presence of bugs Not a major Concern Major Concern
Testing Minimal Exhaustive
Cost / user High Low
Developers (Number) One / Few Many
Use of Standards Limited Essential
Software - Role
• Software Plays a Dual role
– It is a product by itself due to its computing
potential
– It acts as a vehicle to deliver other products
• Control other programs e.g. OS
• Helps in Communication e.g. Networking software
• Helps building other software : OS, 4GL, RDBMS
• Supports or directly provides system functionality
Project - Definition
• A specific plan or design

• A planned undertaking
Project - Definition
• Non routine tasks
• Planning is required
• Specific objectives are to be met
• Specific product is to be created
• Specific time line is to be achieved
• Always large and / or complex
• Work involves several specialties
• Work is done in several phases
• Available resources are always constrained
• Work is carried out for someone else than yourself
Software Project
• Invisibility
With software, progress is visible late
• Complexity
Software products contain more complexity
than other engineered artifacts
• Flexibility
The ease with which software can be changed
is one of its strengths
Management
Management involves the following:
 Planning : What is to be done
 Organizing : Making arrangements
 Staffing : Selecting right people
 Directing : Instructions
 Monitoring : Checking on progress
 Controlling : Action to remedy hold-ups
 Innovating : New solutions
 Representing : Liaising with users
Management
• Activities Covered By S P Management
– Feasibility Study
• Requirements of proposed system gathered
• Development, operational costs and benefits
estimated
• Decide whether a prospective project is worth starting
– Planning
• Outline plan is formulated and then the detailed one
• More detailing can be done at later stages
– Project Execution
• Project is executed as per life cycle
W HH Principle
5

(As suggested by Barry Boehm


in one of his papers)
The principle

IS
• Excellent planning outline for project
managers and software team

• Applicable to all sizes of software


projects
• Why is the system being develop?

• What will be done?

• When will it be done?

• Who is responsible for a function ?

• Where are they organizationally located ?

• How will be job done technically and managerially ?

• How much of each resource is needed ?


W5HH principle
• Why is the system being develop?
– Answer to this questions help assess
validity of business reason for the
software work.
– It answers if the business purpose
justifies the expenditure of people,
time and money
• What will be done?
– Answer to this question establishes the
task set required for project
W5HH principle (Contd.)
• When will it be done?
– Answer to this question helps the team
establish a project schedule by identifying
when tasks have to be conducted and
when milestones are to be reached
• Who is responsible for a function ?
– Answer to this question establishes roles
and responsibility of each team member
W5HH principle (Contd.)
• Where are they organizationally located ?
– Answer to this question indicates that
all roles and responsibilities are not
limited to the software team itself, the
customers, users and stakeholders also
have responsibilities.
• How will be job done technically and managerially ?
– Once product scope is establishes, a
technical and management strategy
must be defined for it.
• How much of each resource is needed ?
– Answer to this question is derived by
developing estimates based on answers
to earlier questions.

You might also like