CSC2012 Professional Software Development 2

Lecture 01
Project Management

Peter CY YAU
 PMI, ITIL

Software Project Management

• Project management is needed as:

• Software development is subject to budget
budget and
• Schedule
Schedule constraints - constraints.
should emphasize to client

• Ensure delivering high-quality

high-quality
software.
• Software may be delivered
delivered late late,
• cost more than originally estimated,
Cost more

• or fail to meet
fail to meetexpectations
expectations of customers.

Prepared by Peter YAU 2

 IEEE Software Life Cycle
(Technical)

• SQA – Software quality assurance • IEEE 730

quality assurance 70

• SCM – Software configuration

configuration managementmanagement • IEEE 828
828

• STD – Software test test

documentation
documentation • IEEE 29119
29119

• SRS – Software requirements specification • IEEE 29148

• V&V – Software verification and validation • IEEE 1012
verification and validation
1012

Prepared by Peter YAU 3

 IEEE Software Life Cycle (Cont)
(More business - softskills)

• SDD – Software design description • IEEE 1016

• SPM – Software project management • IEEE 16326
project management 16326

• SUD – Software user documentation • IEEE 24748

user documentation 24748

• SRA – Software reviews and audit • IEEE 1028

reviews and audit
1028

Prepared by Peter YAU 4

 Typical Pain Points

• Software product is intangible

intangible

• Cannot see progress

progress by simply looking at artefact
artefact being constructed.
• Many software projects are “one-off”
"one-off" (Important) project

• Lessons learned from previous projects may not be readily transferable to new
readily transferable

projects.
• Software processes are variable & organization specific
variable & organizaton specific

• Can’t reliably predict development

predict development problems problems.

Prepared by Peter YAU 5

 Universal Management Activities

• Proposal writing - Write a proposal to win a contract to carry out a work.

Proposal writing

• Project Project
planningplanning - Planning and scheduling project development.
• Risk management
Risk management - Assess risks, monitor these risks and take actions.

• People management
People management - Choose people and led to effective team performance.
• Reporting
Reporting - Report & communicate project progress, progress reviews.

Prepared by Peter YAU 6

 Triple Constraint

• The project management triangle

Project management triangle

(called also the triple constraint, iron

triple constriants

triangle
iron triangle and project project triangle triangle) is a

model of the constraints of project

management.

Prepared by Peter YAU 7

 Triple Constraint Key Points

• The quality of work is constrained by the project's budget (resources),

budget (resources), deadlines
deadlines (time) and scope (features)

(time) and scope (features).

• The project manager can trade
trade between constraints.
• Changes in one constraint necessitate changes in others to compensate
compensate or quality
will
quality suffer.
will suffer

Prepared by Peter YAU 8

 Common Software Management
Activities

• Software project management comprises of a number of activities, which contains

planning of project, deciding scope of software product, estimation of cost in
various terms, scheduling of tasks and events, and resource management.
• Project management activities may include:
• Project
Project Planning
Planning, Scope Management, Project Estimation

• Scope Management
• Project Estimation

Prepared by Peter YAU 9

 Pitfalls

• Planning Assumptions
Assumptions

• Make realistic
realistic
rather than optimistic
optimistic assumptions when defining a project plan.
• Initial
Initial assumptions and scheduling should take unexpected problems into
unexpected problems into account

account.
• Include in the plan, not seriously disrupted delivery schedule.

Prepared by Peter YAU 10

 Scope Management

• It defines the scope of project; this includes all the activities; process need to be
done in order to make a deliverable software product.
• Scope management is essential because it creates boundaries boundaries
of the project by
what would not be done
clearly defining
clearly defining what would be what
done would be done in the project and what would not be done.
• This makes project to contain limited and quantifiable tasks, which can easily be
limited and quantifiable task

documented and in turn avoidsavoidcost and

cost and time overruntime overrun.

Prepared by Peter YAU Source: https://www.tutorialspoint.com/software_engineering/software_project_management.htm 11

 Scope Management (Cont)

• During Project Scope management, it is necessary to

• Define the scope
scope

• Decide its verification

verification and control and control

• Divide the project into various smaller

smaller parts parts for ease of management.

• Verify
Verify the scope
• Control the scope by incorporating changes to the scope

Prepared by Peter YAU Source: https://www.tutorialspoint.com/software_engineering/software_project_management.htm 12

 Project Estimation

• For an effective management accurate estimation of various measures is a must.

With correct estimation managers can manage and control the project more
efficiently and effectively.
• Project estimation may involve the following:
• Software
Software
Size Estimation
Effort Estimation
size estimation
Time Estimation

• Effort estimation
Cost Estimation

• Time estimation
• Cost estimation

Prepared by Peter YAU Source: https://www.tutorialspoint.com/software_engineering/software_project_management.htm 13

 Software Size Estimation

• Software size may be estimated either in terms of KLOC (Kilo

KLOC (Kilo Line of Code) Line of Code) or by

calculating number of function points in the software.

• Lines of code depend upon coding practices and Function points vary according to
Lines of code

the user or software requirement.

Prepared by Peter YAU Source: https://www.tutorialspoint.com/software_engineering/software_project_management.htm 14

 Effort Estimation

• The managers estimate efforts in terms of personnel

personnel requirement requirement
and man-hour and man-hour
required to produce the software.
• For effort estimation software size should be known. This can either be derived by
managers’ experience, organization’s historical
historical data
data or software size can be
converted into efforts by using some standard
standard formulae formulae.

Prepared by Peter YAU Source: https://www.tutorialspoint.com/software_engineering/software_project_management.htm 15

 Time Estimation

• Once size and efforts are estimated, the time required to produce the software can
be estimated.
• Efforts required is segregated intoas persub
segregated into sub categories categories
the requirement as per the requirement
specifications and interdependency

specifications and interdependency of various components of software.

• Software tasks are divided into smaller tasks, activities or events by Work
Breakthrough Structure (WBS). The tasks are scheduled on day-to-day basis or in
calendar months.
• The sum of time required to complete all tasks in hours or days is the total time
invested to complete the project.

Prepared by Peter YAU Source: https://www.tutorialspoint.com/software_engineering/software_project_management.htm 16

 Cost Estimation

• This might be considered as the most etc.

difficult of all because it depends on
• Skilled personnel with task-specific
more elements than any of the previous skills
ones. For estimating project cost, it is
required to consider • Travel involved
• Size of software • Communication
Communication

• Software
Software quality
quality • Training and support
• Hardware
• Additional software or tools, licenses
software or tools, licenses

Prepared by Peter YAU Source: https://www.tutorialspoint.com/software_engineering/software_project_management.htm 17

 Acknowledgements

Teaching materials in this slide is derived, referenced and/or extracted from the following sources. We
try to make the acknowledgements and references as accurate as possible. Thank you very much.
• Internet Resources, such as Wikipedia, Javapoint, Tutorialspoint, etc.
• IEEE Library, IEEE Xplore
• COMPSCI4015 Professional Software Development (H), University of Glasgow (UoG), Dr. Tim Storer
• COMPSCI3005 - Software Engineering M3, UoG, Dr. Richard McCreadie
• Software Engineering (Publisher: Pearson), Ian Sommerville
• Engineering Software Products: An Introduction to Modern Software Engineering (Publisher:
Pearson), Ian Sommerville.
• Contents, and comments from Dr Cao Qi

Prepared by Peter YAU 18