©ian sommerville 2000 slide 1 project management l organising, planning and scheduling software...
Post on 03-Jan-2016
214 Views
Preview:
TRANSCRIPT
©Ian Sommerville 2000 Slide 1
Project management
Organising, planning and scheduling software projects
Objectives• To introduce software project management and to
describe its distinctive characteristics• To discuss project planning and the planning process• To show how graphical schedule representations are
used by project management• To discuss the notion of risks and the risk management
process
©Ian Sommerville 2000 Slide 2
Concerned with activities involved in ensuring that software is delivered• on time
• within the budget
• in accordance with the requirements
Project management is needed because software development is always subject to budget and schedule constraints • Set by the development organisation or the customer
Software project management
©Ian Sommerville 2000 Slide 3
Project control Time, both the number of man-months and the schedule
Information, mostly the documentation
Technical, Knowledge, techniques and tools.
Organization, people and team aspects
Quality, not an add-on feature; it has to be built in
Budget for the project,
©Ian Sommerville 2000 Slide 4
The product is intangible The product is uniquely flexible The product is uniquely complex Software engineering is not recognized as an
engineering discipline with the same status as mechanical, electrical engineering, etc.
The software development process is not standardised
Many software projects are “one-off” projects
Software management distinctions
©Ian Sommerville 2000 Slide 5
Proposal writing Project planning and scheduling Project costing Project monitoring and reviews Personnel selection and evaluation Report writing and presentations
Management activities
©Ian Sommerville 2000 Slide 6
Management Activities
Process model Organization of project Standards, guidelines,
procedures Management activities Risks
Methods and techniques Quality assurance Work packages Resources Changes Delivery
Other important details.
©Ian Sommerville 2000 Slide 7
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» Here’s Bob. He’s new. He’ll be a member of your team. He doesn’t
know much yet, but he can brew a mean cup of coffee and has a great personality.
Managers have to work within these constraints• especially when (as is currently the case) there is an international
shortage of skilled IT staff
©Ian Sommerville 2000 Slide 8
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• Beware of grumbling developers
Various different types of plan may be developed to support the main software project plan that is concerned with schedule and budget
©Ian Sommerville 2000 Slide 9
Types of project plan
Plan DescriptionQuality 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. Configurationmanagement plan
Describes the configuration managementprocedures and structures to be used.
Maintenance plan Predicts the maintenance requirements ofthe system, maintenance costs and effortrequired.
Staff development plan. Describes how the skills and experience ofthe project team members will bedeveloped.
©Ian Sommerville 2000 Slide 10
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
Evaluationreport
Prototypedevelopment
Requirementsdefinition
Requirementsanalysis
Feasibilityreport
Feasibilitystudy
Architecturaldesign
Designstudy
Requirementsspecification
Requirementsspecification
ACTIVITIES
MILESTONES
©Ian Sommerville 2000 Slide 11
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
©Ian Sommerville 2000 Slide 12
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
©Ian Sommerville 2000 Slide 13
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 the critical path
Bar charts show schedule against calendar time
©Ian Sommerville 2000 Slide 14
Task durations and dependenciesTask Duration (days) DependenciesT1 8T2 15T3 15 T1 (M1)T4 10T5 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)
©Ian Sommerville 2000 Slide 15
Activity network
start
T2
M3T6
Finish
T10
M7T5
T7
M2T4
M5
T8
4/7/99
8 days
14/7/99 15 days
4/8/99
15 days
25/8/99
7 days
5/9/99
10 days
19/9/99
15 days
11/8/99
25 days
10 days
20 days
5 days25/7/99
15 days
25/7/99
18/7/99
10 days
T1
M1 T3T9
M6
T11
M8
T12
M4
©Ian Sommerville 2000 Slide 16
Staff allocation4/7 11/7 18/7 25/ 1/8 8/8 15/8 22/8 29/8 5/9 12/9 19/9
T4
T8 T11
T12
T1
T3
T9
T2
T6 T10
T7
T5
Fred
Jane
Anne
Mary
Jim
©Ian Sommerville 2000 Slide 17
Risk management Risk management is concerned with identifying
risks and drawing up plans to minimise their effect on a project.
A risk is a probability that some adverse circumstance will occur. • Project risks affect schedule or resources
• Product risks affect the quality or performance of the software being developed
• Business risks affect the organisation developing or procuring the software
©Ian Sommerville 2000 Slide 18
The risk management process Risk identification
• Identify project, product and business risks
Risk analysis • Assess the likelihood and consequences of risks
Risk planning • Draw up plans to avoid/minimise risk effects
Risk monitoring • Monitor the risks throughout the project
©Ian Sommerville 2000 Slide 19
Risk identification Technology risks People risks Organisational risks Requirements risks Estimation risks
©Ian Sommerville 2000 Slide 20
Risks and risk typesRisk type Possible risksTechnology The database used in the system cannot process as many
transactions per second as expected.Software components which should be reused contain defectswhich limit their functionality.
People It is impossible to recruit staff with the skills required.Key staff are ill and unavailable at critical times.Required training for staff is not available.
Organisational The organisation is restructured so that different managementare responsible for the project.Organisational financial problems force reductions in the projectbudget.
Tools The code generated by CASE tools is inefficient.CASE tools cannot be integrated.
Requirements Changes to requirements which require major design rework areproposed.Customers fail to understand the impact of requirementschanges.
Estimation The time required to develop the software is underestimated.The rate of defect repair is underestimated.The size of the software is underestimated.
©Ian Sommerville 2000 Slide 21
Risk analysis Assess probability and seriousness of each risk Probability may be
• very low• low• moderate• high• very high
Risk effects might be• catastrophic• serious• tolerable• insignificant
©Ian Sommerville 2000 Slide 22
Risk analysisRisk Probability EffectsOrganisational financial problems force reductionsin the project budget.
Low Catastrophic
It is impossible to recruit staff with the skillsrequired for the project.
High Catastrophic
Key staff are ill at critical times in the project. Moderate SeriousSoftware components which should be reusedcontain defects which limit their functionality.
Moderate Serious
Changes to requirements which require majordesign rework are proposed.
Moderate Serious
The organisation is restructured so that differentmanagement are responsible for the project.
High Serious
The database used in the system cannot process asmany transactions per second as expected.
Moderate Serious
The time required to develop the software isunderestimated.
High Serious
CASE tools cannot be integrated. High TolerableCustomers fail to understand the impact ofrequirements changes.
Moderate Tolerable
Required training for staff is not available. Moderate TolerableThe rate of defect repair is underestimated. Moderate TolerableThe size of the software is underestimated. High TolerableThe code generated by CASE tools is inefficient. Moderate Insignificant
©Ian Sommerville 2000 Slide 23
Risk planning Consider each risk and develop a strategy to
manage that risk Avoidance strategies
• The probability that the risk will arise is reduced
Minimisation strategies• The impact of the risk on the project or product will be reduced
Contingency plans• If the risk arises, contingency plans are plans to deal with that
risk
©Ian Sommerville 2000 Slide 24
Risk monitoring Assess each identified risks regularly to decide
whether or not it is becoming less or more probable
Also assess whether the effects of the risk have changed
Each key risk should be discussed at management progress meetings
©Ian Sommerville 2000 Slide 25
Key points Good project management is essential for project success The intangible nature of software causes problems for management Managers have diverse roles but their most significant activities are
planning, estimating and scheduling Planning and estimating are iterative processes that continue throughout
the course of a project A project milestone is a predictable state where
some formal report of progress is presented to management. Risks may be project risks, product risks or business risks Risk management is concerned with identifying risks that may affect the
project and planning to ensure that these risks do not develop into major threats
top related