Scribd
Upload
37 views21 pages

SE Slides8

The document discusses software project management. It covers topics like management activities, project planning, scheduling, and risk management. It describes the importance of project management to deliver software on time and on budget. It also discusses planning activities like creating quality, validation, and configuration management plans. The key aspects of project planning like work breakdown, scheduling using charts and networks, and allocating staff are explained.

Uploaded by

tayyabson06
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
37 views21 pages

SE Slides8

The document discusses software project management. It covers topics like management activities, project planning, scheduling, and risk management. It describes the importance of project management to deliver software on time and on budget. It also discusses planning activities like creating quality, validation, and configuration management plans. The key aspects of project planning like work breakdown, scheduling using charts and networks, and allocating staff are explained.

Uploaded by

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

Software Engineering

Project management
Topics covered

• Management activities
• Project planning
• Project scheduling
• Risk management
Software project management
• Concerned with activities involved in ensuring
that software is delivered on time and on
schedule and in accordance with the
requirements of the organisations developing
and procuring the software.
• Project management is needed because
software development is always subject to
budget and schedule constraints that are set by
the organisation developing the software.
Management activities

• Proposal writing.
• Project planning and scheduling.
• Project costing.
• Project monitoring and reviews.
• Personnel selection and evaluation.
• Report writing and presentations.
Management commonalities
Management commonalities
• These activities are not peculiar to software
management.
• Many techniques of engineering project
management are equally applicable to software
project management.
• Technically complex engineering systems tend
to suffer from the same problems as software
systems.
Project staffing
• May not be possible to appoint the ideal people to
work on a project
– Project budget may not allow for the use of highly-
paid staff;
– Staff with the appropriate experience may not be
available;
– An organisation may wish to develop employee skills
on a software project.
• Managers have to work within these constraints
especially when there are shortages of trained
staff.
Project planning
• Probably the most time-consuming project
management activity.
• Continuous activity from initial concept through
to system delivery. Plans must be regularly
revised as new information becomes available.
• Various different types of plan may be developed
to support the main software project plan that is
concerned with schedule and budget.
Types of project plan

Plan Description
Quality plan Describes the quality procedures and standards that will be
used in a project.
Validation plan Describes the approach, resources and schedule used for
system validation.
Configuration Describes the configuration management procedures and
management plan structures to be used.
Maintenance plan Predicts the maintenance requirements of the system,
maintenance costs and effort required.
Staff development Describes how the skills and experience of the project team
plan. members will be developed.
The project plan

• The project plan sets out:


– The resources available to the project;
– The work breakdown;
– A schedule for the work.
Project plan structure

• Introduction.
• Project organisation.
• Risk analysis.
• Hardware and software resource requirements.
• Work breakdown.
• Project schedule.
• Monitoring and reporting mechanisms.
Activity organization

• Activities in a project should be organised to


produce tangible outputs for management to
judge progress.
• Milestones are the end-point of a process
activity.
• Deliverables are project results delivered to
customers.
• The waterfall process allows for the
straightforward definition of progress milestones.
Milestones in the RE process

ACTIVITIES

Feasibility Requir ements Prototype Design Requir ements


stud y analysis de velopment stud y specification

Feasibility User Evalua tion Architectur al System


repor t requirements repor t design requirements

MILESTONES
Project scheduling

• Split project into tasks and estimate time and


resources required to complete each task.
• Organize tasks concurrently to make optimal
use of workforce.
• Minimize task dependencies to avoid delays
caused by one task waiting for another to
complete.
• Dependent on project managers intuition and
experience.
Project scheduling process

Identify Identify activity Estimate resources Allocate people Create project


activities dependencies for activities to activities char ts

Software Activity charts


requirements and bar char ts
Scheduling problems
• Estimating the difficulty of problems and hence
the cost of developing a solution is hard.
• Productivity is not proportional to the number of
people working on a task.
• Adding people to a late project makes it later
because of communication overheads.
• The unexpected always happens. Always allow
contingency in planning.
Bar charts and activity networks

• Graphical notations used to illustrate the project


schedule.
• Show project breakdown into tasks. Tasks
should not be too small. They should take about
a week or two.
• Activity charts show task dependencies and the
critical path.
• Bar charts show schedule against calendar time.
Task durations and dependencies

Activity Duration (days) Dependencies


T1 8
T2 15
T3 15 T1 (M1)
T4 10
T5 10 T2, T4 (M2)
T6 5 T1, T2 (M3)
T7 20 T1 (M1)
T8 25 T4 (M5)
T9 15 T3, T6 (M4)
T10 15 T5, T7 (M7)
T11 7 T9 (M6)
T12 10 T11 (M8)
Activity network
1 4/7 /03 15 da ys
15 da ys
M1 T3
8 da ys T9
T1 5 da ys 4/8/03 2 5/8/03
2 5/7 /03
4/7 /03 T6 M4 M6
M3
star t 2 0 da ys 7 da ys
15 da ys
T7 T11
T2
25/7 /03 11/8/03 5/9/03
10 da ys 10 da ys
M2 M7 M8
T4 T5 15 da ys
T10 10 days
1 8/7 /03
T12
M5
2 5 da ys
T8 Finish
19/9/03
Activity timeline
4/7 11/7 18/7 2 5/7 1/8 8/8 1 5/8 22/8 2 9/8 5/9 12/9 1 9/9

Star t
T4
T1
T2
M1
T7
T3
M5
T8
M3
M2
T6
T5
M4
T9
M7
T10
M6
T11
M8
T12
Finish
Staff allocation
4/7 1 1/7 18/7 2 5/7 1/8 8/8 15/8 2 2/8 2 9/8 5/9 1 2/9 19/9

Fred T4
T8 T11
T12
Jane T1
T3
T9
Anne T2
T6 T10

Jim T7

Mary T5

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy