0% found this document useful (0 votes)
114 views10 pages

Software Project Management: Telone Centre For Learning

This document discusses the four P's of software project management: People, Product, Process, and Project. It outlines key considerations for each: [1] People includes staffing, communication, work environment and development. [2] Product involves defining objectives, scope, and technical constraints. [3] Process provides a framework and requires selecting an appropriate model. [4] Successful projects require understanding the problem, maintaining momentum, tracking progress, making decisions, and conducting postmortems. The document emphasizes quality software project management and outlines factors for a successful project.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
114 views10 pages

Software Project Management: Telone Centre For Learning

This document discusses the four P's of software project management: People, Product, Process, and Project. It outlines key considerations for each: [1] People includes staffing, communication, work environment and development. [2] Product involves defining objectives, scope, and technical constraints. [3] Process provides a framework and requires selecting an appropriate model. [4] Successful projects require understanding the problem, maintaining momentum, tracking progress, making decisions, and conducting postmortems. The document emphasizes quality software project management and outlines factors for a successful project.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

Telone Centre for Learning

SOFTWARE PROJECT
MANAGEMENT

DIPLOMA IN SOFTWARE ENGINEERING 2.1

LECTURER: MS. J. CHIBHABHA


[email protected]
The Four P’s in Software
Project Management
The People

Every organization needs to continually improve its ability to attract,


develop , motivate, organize, and retain the workforce needed to
complete a business objective.
Consider:
Staffing
Communication and coordination
Work environment
Performance management
Training
Compensation
Competency analysis and development
Career development
Team culture development etc.
The product

Before a project can be planned, product objectives and scope


should be established,
Alternative solutions should be considered,
And technical and management constraints should be identified
Teams must define product objectives and scope.
Objectives identify the overall goals for the product without
considering how these goals will be achieved.
Scope identifies the primary data, functions and behaviors that
characterize the product and bounds these characteristics in a
quantitative manner.
The product – Software Scope
The first software project management activity is
determination of software scope by answering the
following questions:
1. Context – how does the software to be built fit into a larger
system, product, or business context and what constraints are
imposed as a result of the context?
2. Information objectives – what customer-visible data objects are
produces as output from the software? What data objects are
required for input?
3. Function and performance – what function does the software
perform to transform input data into output? Are any special
performance characteristics to be addressed?
The Process
A software process provides the framework from which a
comprehensive plan for development can be established.
The framework activities that characterize the software process are
applicable to all software projects.
A team needs to select the process model that is appropriate for the
software to be engineered.
Consider:
1. The customer who has requested the product
2. The people who will do the work
3. The characteristics of the product itself
4. The project environment in which the software team works
Melding the Product and the Process

Project planning begins with melding of the product and the process.
Each function to be engineered must pass through the set of
framework activities that have been defined by the software
organization.
Process decomposition:
At the initial stage the team might choose a particular software
process model
But actual work tasks vary, a particular framework activity might
require a different process model.
The Project

We conduct planned and controlled software projects to


manage their complexity.
Over the years success rate of software projects has
improved, however the failure rate remains higher than it
should be.
That’s why we need quality software project management.
The Project Cont..

To successfully manage a software project:


1. Start on the right foot – understand the problem that is to be solved.
1. Set realistic objectives and expectations.
2. Maintain momentum
3. Track progress
4. Make smart decisions
5. Conduct a postmortem analysis – a mechanism for extracting
lessons from each project
THE END

You might also like