16523 spm chapter 1
TRANSCRIPT
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 1/35
© The McGraw-Hill Companies, 20051
An Introduction
Chapter 1Software Project
Management4 th Edition
Robert Hughes andMike Cotterell
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 2/35
© The McGraw-Hill Companies, 20052
Outline of talk
In this introduction the main questions to beaddressed will be:
– What is software project management? Is itreally different from „ordinary‟ projectmanagement?
– How do you know when a project has beensuccessful? For example, do the expectationsof the customer/client match those of thedevelopers?
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 3/35
© The McGraw-Hill Companies, 20053
What is a project?
Some dictionary definitions:“A specific plan or design”
“A planned undertaking” “A large undertaking e.g. a public works
scheme” Longmans dictionary
Key points above are planning and size of task
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 4/35
© The McGraw-Hill Companies, 20054
Jobs versus projects
‘Jobs’ – repetition of very well-defined and wellunderstood tasks with very little uncertainty
‘Exploration’ – e.g. finding a cure for cancer: theoutcome is very uncertain
‘Projects’ – in the middle!
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 5/35
© The McGraw-Hill Companies, 20055
Characteristics of projects
A task is more „project -like‟ if it is: • Planned• Aiming at a specific target
• Work carried out for a customer• Made up of several different phases• Constrained by time and resources
• Large and/or complex
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 6/35
© The McGraw-Hill Companies, 20056
Are software projects reallydifferent from other projects?
Not really! …but…
• Invisibility• Complexity• Conformity• Flexibility
make software more problematic tobuild than other engineered artefacts.
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 7/35
© The McGraw-Hill Companies, 20057
Activities covered by projectmanagement
Feasibility study
Is project technically feasible and worthwhile from abusiness point of view?Planning
Only done if project is feasibleExecution
Implement plan, but plan may be changed as we go along
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 8/35
© The McGraw-Hill Companies, 20058
The software development life-cycle (ISO 12207)
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 9/35
© The McGraw-Hill Companies, 20059
ISO 12207 life-cycle
Requirements analysis – Requirements elicitation: what does the
client need? – Analysis: converting „customer -facing‟
requirements into equivalents thatdevelopers can understand
– Requirements will cover• Functions• Quality• Resource constraints i.e. costs
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 10/35
© The McGraw-Hill Companies, 200510
ISO 12207 life-cycle
• Architecture design – Based on system requirements – Defines components of system: hardware,
software, organizational – Software requirements will come out ofthis
• Code and test – Of individual components
• Integration – Putting the components together
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 11/35
© The McGraw-Hill Companies, 200511
ISO12207 continued
• Qualification testing – Testing the system (not just the software )
• Installation
– The process of making the systemoperational – Includes setting up standing data, setting
system parameters, installing on
operational hardware platforms, usertraining etc• Acceptance support
– Including maintenance and enhancement
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 12/35
© The McGraw-Hill Companies, 200512
Some ways of categorizingprojects
Distinguishing different types of project isimportant as different types of task
need different project approaches e.g.• Information systems versus embedded
systems
• Objective-based versus product-based
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 13/35
© The McGraw-Hill Companies, 200513
What is management?
This involves the following activities:
• Planning – deciding what is to be done• Organizing – making arrangements• Staffing – selecting the right people for
the job• Directing – giving instructions
continued…
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 14/35
© The McGraw-Hill Companies, 200514
What is management?(continued)
• Monitoring – checking on progress
• Controlling – taking action to remedy hold-
ups• Innovating – coming up with solutions when
problems emerge
• Representing – liaising with clients, users,developers and other stakeholders
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 15/35
© The McGraw-Hill Companies, 2005
Problems with Software
Projects
15
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 16/35
© The McGraw-Hill Companies, 200516
Setting objectives
• Answering the question „ What do wehave to do to have a success?‟
• Need for a project authority – Sets the project scope – Allocates/approves costs
• Could be one person - or a group – Project Board – Project Management Board – Steering committee
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 17/35
© The McGraw-Hill Companies, 200517
ObjectivesInformally , the objective of a project can be
defined by completing the statement:
The project will be regarded as asuccess if………………………………..
Rather like post-conditions for the project
Focus on what will be put in place, rather thanhow activities will be carried out
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 18/35
© The McGraw-Hill Companies, 200518
Objectives should be SMART
S – specific, that is, concrete and well-defined
M – measurable, that is, satisfaction of theobjective can be objectively judged
A – achievable, that is, it is within the power of theindividual or group concerned to meet the target
R – relevant, the objective must relevant to the truepurpose of the project
T – time constrained: there is defined point intime by which the objective should be achieved
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 19/35
© The McGraw-Hill Companies, 200519
Goals/sub-objectives
These are steps along the way to achievingthe objective. Informally, these can bedefined by completing the sentence…
Objective X will be achievedIF the following goals are all achieved
A……………
B…………… C…………… etc
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 20/35
© The McGraw-Hill Companies, 200520
Goals/sub-objectives continued
Often a goal can be allocated to an individual.Individual may have the capability of achievinggoal, but not the objective on their own e.g.
Objective – user satisfaction with software product
Analyst goal – accurate requirements
Developer goal – software that is reliable
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 21/35
© The McGraw-Hill Companies, 200521
Measures of effectiveness
How do we know that the goal or objective hasbeen achieved?By a practical test, that can be objectively
assessed.
e.g. for user satisfaction with software product:
• Repeat business – they buy further products fromus
• Number of complaints – if low etc etc
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 22/35
© The McGraw-Hill Companies, 200522
StakeholdersThese are people who have a stake orinterest in the projectIn general, they could be users/clients ordevelopers/implementers
They could be:• Within the project team
• Outside the project team, but within thesame organization• Outside both the project team and the
organization
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 23/35
© The McGraw-Hill Companies, 200523
Management control
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 24/35
© The McGraw-Hill Companies, 200524
Management control
Data – the raw detailse.g. „6,000 documents processed at location X‟
Information – the data is processed to producesomething that is meaningful and usefule.g. „productivity is 100 documents a day‟
Comparison with objectives/goalse.g. we will not meet target of processing all
documents by 31 st March
continued…..
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 25/35
© The McGraw-Hill Companies, 200525
Management control -continued
Modelling – working out the probableoutcomes of various decisionse.g. if we employ two more staff at location X
how quickly can we get the documentsprocessed?
Implementation – carrying out the remedialactions that have been decided upon
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 26/35
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 27/35
© The McGraw-Hill Companies, 2005
Problems in Software Projects
• People-related problems• Process-related problems• Product-related problems• Technology-related problems
27
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 28/35
© The McGraw-Hill Companies, 2005
People Related Problems
• Low motivation• Problem employees• Unproductive work environment• Inefficient project management
style• Lack of stakeholder interest• Ineffective project sponsorship by
management: 28
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 29/35
© The McGraw-Hill Companies, 2005
Process Related problems
• Unrealistic schedule• Insufficient identification• Unsuitable life cycle model selection• Abandoning quality under pressure
of deadlines
29
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 30/35
© The McGraw-Hill Companies, 2005
Product related Problems
• Product scope changed toward theend of the project life cycle
• Research-oriented softwaredevelopment
• defined scope• Fuzzy users
30
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 31/35
© The McGraw-Hill Companies, 2005
Technology related Problems
• Overestimated savings from reusablecomponents and new tools and methods
• Integrating different software productsin cross-platform implementation
• Switching tools in mid way
31
I f S f P j
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 32/35
© The McGraw-Hill Companies, 2005
Importance of Software ProjectManagement
• Scheduling-Allocation of work against Time considering resources
• Resource assignments (man-machine-material) • Cost control and budget management • Quality management-meeting the requirement of project
• Tracking progress- monitoring ‘Scope -Time- Cost’ baseline
• Report generation-Timely generation of reports for the project
stakeholders
32
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 33/35
© The McGraw-Hill Companies, 2005
Importance of SPM
• Excellent Product Quality• Adequate Communication• Reducing Risks• Strategic objectives and goals• Crisis Management
33
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 34/35
© The McGraw-Hill Companies, 2005
Risk and Types
• “Risk are future uncertain events with aprobability of occurrence and a
potential for loss”
34
8/12/2019 16523 SPM Chapter 1
http://slidepdf.com/reader/full/16523-spm-chapter-1 35/35
© h G ill C i 200
Risk Reduction
• Senior Management Commitment• High Level of Communication -
Keep Talking!• Highly Skilled Development Team• Use Case Driven Approach• Change Control• Visual Modelling - 'A picture is
worth a thousand words'35