Enviar búsqueda
Cargar
Ch5
•
Descargar como PPT, PDF
•
1 recomendación
•
427 vistas
Cristian Mureșan
Seguir
Denunciar
Compartir
Denunciar
Compartir
1 de 39
Descargar ahora
Recomendados
Ch5
Ch5
Ankita Rana
Project Management (Soft)
Project Management (Soft)
Ahmad Basim Hamza
Software Engineering (Project Scheduling)
Software Engineering (Project Scheduling)
ShudipPal
Credible Plans, Integrated Reporting, and Control Systems
Credible Plans, Integrated Reporting, and Control Systems
Glen Alleman
Software Project Management
Software Project Management
Ramesh Babu
Software project management 3
Software project management 3
Indu Sharma Bhardwaj
Software project management
Software project management
R A Akerkar
Spm ksp
Spm ksp
ktosri
Recomendados
Ch5
Ch5
Ankita Rana
Project Management (Soft)
Project Management (Soft)
Ahmad Basim Hamza
Software Engineering (Project Scheduling)
Software Engineering (Project Scheduling)
ShudipPal
Credible Plans, Integrated Reporting, and Control Systems
Credible Plans, Integrated Reporting, and Control Systems
Glen Alleman
Software Project Management
Software Project Management
Ramesh Babu
Software project management 3
Software project management 3
Indu Sharma Bhardwaj
Software project management
Software project management
R A Akerkar
Spm ksp
Spm ksp
ktosri
Software project management- Software Engineering
Software project management- Software Engineering
Muhammad Yousuf Abdul Qadir
Software project managment
Software project managment
Jawid Ahmad Baktash
Bechtel project planning example
Bechtel project planning example
asfandiyar
software project management
software project management
Varendra University Rajshahi-bangladesh
Chapter1 conventional softwaremanagement (1)
Chapter1 conventional softwaremanagement (1)
Jkumararaja
WBS is Paramount
WBS is Paramount
Glen Alleman
Building a Credible Performance Measurement Baseling
Building a Credible Performance Measurement Baseling
Glen Alleman
Structure of project plan and schedule
Structure of project plan and schedule
Mr SMAK
Software Project Management by Dr. B. J. Mohite
Software Project Management by Dr. B. J. Mohite
Zeal Education Society, Pune
The integrated master plan and integrated master schedule
The integrated master plan and integrated master schedule
Glen Alleman
Process Flow and Narrative for Agile
Process Flow and Narrative for Agile
Glen Alleman
Ch3 proj.mgt
Ch3 proj.mgt
videoaakash15
CMMI and Agile
CMMI and Agile
Glen Alleman
Estimating and Reporting Agile Projects
Estimating and Reporting Agile Projects
Glen Alleman
Probabilistic Risk Management (With Notes)
Probabilistic Risk Management (With Notes)
Glen Alleman
Software project-scheduling
Software project-scheduling
saurabhshertukde
Planning Phase - P&MSP2010 (3/11)
Planning Phase - P&MSP2010 (3/11)
Emanuele Della Valle
Project management_process
Project management_process
hepta-sat
Performance Based Management Handbook
Performance Based Management Handbook
Glen Alleman
A Gentle Introduction to the IMP/IMS
A Gentle Introduction to the IMP/IMS
Glen Alleman
Media Pembelajaran TIK Kelas IX Semester I
Media Pembelajaran TIK Kelas IX Semester I
Rizky Adhi Pradipta II
Sommer 2012
Sommer 2012
mba1704
Más contenido relacionado
La actualidad más candente
Software project management- Software Engineering
Software project management- Software Engineering
Muhammad Yousuf Abdul Qadir
Software project managment
Software project managment
Jawid Ahmad Baktash
Bechtel project planning example
Bechtel project planning example
asfandiyar
software project management
software project management
Varendra University Rajshahi-bangladesh
Chapter1 conventional softwaremanagement (1)
Chapter1 conventional softwaremanagement (1)
Jkumararaja
WBS is Paramount
WBS is Paramount
Glen Alleman
Building a Credible Performance Measurement Baseling
Building a Credible Performance Measurement Baseling
Glen Alleman
Structure of project plan and schedule
Structure of project plan and schedule
Mr SMAK
Software Project Management by Dr. B. J. Mohite
Software Project Management by Dr. B. J. Mohite
Zeal Education Society, Pune
The integrated master plan and integrated master schedule
The integrated master plan and integrated master schedule
Glen Alleman
Process Flow and Narrative for Agile
Process Flow and Narrative for Agile
Glen Alleman
Ch3 proj.mgt
Ch3 proj.mgt
videoaakash15
CMMI and Agile
CMMI and Agile
Glen Alleman
Estimating and Reporting Agile Projects
Estimating and Reporting Agile Projects
Glen Alleman
Probabilistic Risk Management (With Notes)
Probabilistic Risk Management (With Notes)
Glen Alleman
Software project-scheduling
Software project-scheduling
saurabhshertukde
Planning Phase - P&MSP2010 (3/11)
Planning Phase - P&MSP2010 (3/11)
Emanuele Della Valle
Project management_process
Project management_process
hepta-sat
Performance Based Management Handbook
Performance Based Management Handbook
Glen Alleman
A Gentle Introduction to the IMP/IMS
A Gentle Introduction to the IMP/IMS
Glen Alleman
La actualidad más candente
(20)
Software project management- Software Engineering
Software project management- Software Engineering
Software project managment
Software project managment
Bechtel project planning example
Bechtel project planning example
software project management
software project management
Chapter1 conventional softwaremanagement (1)
Chapter1 conventional softwaremanagement (1)
WBS is Paramount
WBS is Paramount
Building a Credible Performance Measurement Baseling
Building a Credible Performance Measurement Baseling
Structure of project plan and schedule
Structure of project plan and schedule
Software Project Management by Dr. B. J. Mohite
Software Project Management by Dr. B. J. Mohite
The integrated master plan and integrated master schedule
The integrated master plan and integrated master schedule
Process Flow and Narrative for Agile
Process Flow and Narrative for Agile
Ch3 proj.mgt
Ch3 proj.mgt
CMMI and Agile
CMMI and Agile
Estimating and Reporting Agile Projects
Estimating and Reporting Agile Projects
Probabilistic Risk Management (With Notes)
Probabilistic Risk Management (With Notes)
Software project-scheduling
Software project-scheduling
Planning Phase - P&MSP2010 (3/11)
Planning Phase - P&MSP2010 (3/11)
Project management_process
Project management_process
Performance Based Management Handbook
Performance Based Management Handbook
A Gentle Introduction to the IMP/IMS
A Gentle Introduction to the IMP/IMS
Destacado
Media Pembelajaran TIK Kelas IX Semester I
Media Pembelajaran TIK Kelas IX Semester I
Rizky Adhi Pradipta II
Sommer 2012
Sommer 2012
mba1704
Online meeting and learning DRAFT work in progress
Online meeting and learning DRAFT work in progress
Jo Flick
Zekic musser rad_ispravljen
Zekic musser rad_ispravljen
Edo Musser
The future of online learning
The future of online learning
Jo Flick
Soal dan-solusi-uas-kalkulus-i-ittelkom
Soal dan-solusi-uas-kalkulus-i-ittelkom
Muhammad Huda
Destacado
(6)
Media Pembelajaran TIK Kelas IX Semester I
Media Pembelajaran TIK Kelas IX Semester I
Sommer 2012
Sommer 2012
Online meeting and learning DRAFT work in progress
Online meeting and learning DRAFT work in progress
Zekic musser rad_ispravljen
Zekic musser rad_ispravljen
The future of online learning
The future of online learning
Soal dan-solusi-uas-kalkulus-i-ittelkom
Soal dan-solusi-uas-kalkulus-i-ittelkom
Similar a Ch5
Unit-3-Risk-mgmt.ppt
Unit-3-Risk-mgmt.ppt
joshimeet479
project managnement.ppt
project managnement.ppt
ssuser8c0d24
Project-management.ppt
Project-management.ppt
MUsama58
Project Management.pdf
Project Management.pdf
HughMungus22
ch5.pdf
ch5.pdf
Rayver4
Software Engineering - Ch5
Software Engineering - Ch5
Siddharth Ayer
ch04.ppt
ch04.ppt
charu110662
Project Scheduling, Planning and Risk Management
Project Scheduling, Planning and Risk Management
university of education,Lahore
Ch26
Ch26
J.Durga Chaitanya Kumar
Ch1
Ch1
Mayuran Ramanathan
Ch1
Ch1
guestfea9c55
Introduction to Software Enigneering
Introduction to Software Enigneering
university of education,Lahore
01 unidad i introduccion
01 unidad i introduccion
victdiazm
ch1.ppt
ch1.ppt
OmarMohammadHamad
Ch28
Ch28
al-wahidi
0273710133 pp01v2
0273710133 pp01v2
Ravi Chandra
Software Processes
Software Processes
Mayuran Ramanathan
Software Engineering - Ch4
Software Engineering - Ch4
Siddharth Ayer
sftware cst est
sftware cst est
testinggggaaaa
Ch1
Ch1
srvnsmile
Similar a Ch5
(20)
Unit-3-Risk-mgmt.ppt
Unit-3-Risk-mgmt.ppt
project managnement.ppt
project managnement.ppt
Project-management.ppt
Project-management.ppt
Project Management.pdf
Project Management.pdf
ch5.pdf
ch5.pdf
Software Engineering - Ch5
Software Engineering - Ch5
ch04.ppt
ch04.ppt
Project Scheduling, Planning and Risk Management
Project Scheduling, Planning and Risk Management
Ch26
Ch26
Ch1
Ch1
Ch1
Ch1
Introduction to Software Enigneering
Introduction to Software Enigneering
01 unidad i introduccion
01 unidad i introduccion
ch1.ppt
ch1.ppt
Ch28
Ch28
0273710133 pp01v2
0273710133 pp01v2
Software Processes
Software Processes
Software Engineering - Ch4
Software Engineering - Ch4
sftware cst est
sftware cst est
Ch1
Ch1
Ch5
1.
Project management ©Ian Sommerville
2004 Software Engineering, 7th edition. Chapter 5 Slide 1
2.
Objectives
To explain the main tasks undertaken by project managers 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 2004 Software Engineering, 7th edition. Chapter 5 Slide 2
3.
Topics covered
Management activities Project planning Project scheduling Risk management ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 3
4.
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. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 4
5.
Software management distinctions
The product is intangible. The product is uniquely flexible. Software engineering is not recognized as an engineering discipline with the sane status as mechanical, electrical engineering, etc. The software development process is not standardised. Many software projects are 'one-off' projects. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 5
6.
Management activities
Proposal writing. Project planning and scheduling. Project costing. Project monitoring and reviews. Personnel selection and evaluation. Report writing and presentations. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 6
7.
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. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 7
8.
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. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 8
9.
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. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 9
10.
Types of project
plan Plan Description Quality plan Describes the quality procedures and standards that will be used in a project. See Chapter 27. Validation plan Describes the approach, resources and schedule used for system validation. See Chapter 22. Configuration Describes the configuration management procedures and management plan structures to be used. See Chapter 29. Maintenance plan Predicts the maintenance requirements of the system, maintenance costs and effort required. See Chapter 21. Staff development Describes how the skills and experience of the project team plan. members will be developed. See Chapter 25. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 10
11.
Project planning process Establish
the project constraints Make initial assessments of the project parameters Define project milestones and deliverables while project has not been completed or cancelled loop Draw up project schedule Initiate activities according to schedule Wait ( for a while ) Review project progress Revise estimates of project parameters Update the project schedule Re-negotiate project constraints and deliverables if ( problems arise ) then Initiate technical review and possible revision end if end loop ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 11
12.
The project plan
The project plan sets out: • The resources available to the project; • The work breakdown; • A schedule for the work. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 12
13.
Project plan structure
Introduction. Project organisation. Risk analysis. Hardware and software resource requirements. Work breakdown. Project schedule. Monitoring and reporting mechanisms. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 13
14.
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. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 14
15.
ATIV
Clopm EDes Sstud Milestones in the RE process Fasibility easibility RquirRq e dechit ements Prdess ototy analyre ysisal v Ar e sp F require e User S Ev y alua rt M N rt E e e em studtionti ypor por IO LS T E S ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 15
16.
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 2004 Software Engineering, 7th edition. Chapter 5 Slide 16
17.
The project scheduling
process Identifyts Identify Estim Allo Cr activities depends for an toA Software requiremac ch ts a t ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 17
18.
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 2004 Software Engineering, 7th edition. Chapter 5 Slide 18
19.
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 2004 Software Engineering, 7th edition. Chapter 5 Slide 19
20.
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) ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 20
21.
414/8/
5M4 ys5d /7da 1days /0329 1 ys 5 d M1M6 T37/8 822 T ys0 da T1 da 5 ys 5T7T1 /03 1 /7 5/ T6 4/701da /03ys/8/ M3 Activity network starM7 t151 1M 5M2 d ysys da T2 5ys 11/030T1 2T52 /7 1 08daT1d ys/7 ys T42 da 0 /031 /9 M59 5 Fi ys T8 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 21
22.
4/78/81 /9
12/72/89/9 1/752/8 81/85/9 5/792 Star t T4 T1 T2 1 /8 1 Activity timeline M1 T7 T3 M5 T8 4 M3 M2 T6 T5 M6 M T9M8 M7 T1 Fin 0T1 1 T1 2 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 22
23.
4/7/7/8/
1T8T1 1/725/9 81/8/8 2/722 58/8/8 191 512 Fne T1 rT4 ed 19 Staff allocation JT1T1 a T3 9 AnneT T2 0 T6 Jim T7 Mary T5 ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 23
24.
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 2004 Software Engineering, 7th edition. Chapter 5 Slide 24
25.
Software risks
Risk Affects Description Staff turnover Project Experienced staff will leave the project before it is finished. Management change Project There will be a change of organisational management with different priorities. Hardware unavailability Project Hardware that is essential for the project will not be delivered on schedule. Requirements change Project and There will be a larger number of changes to the product requirements than anticipated. Specification delays Project and Specifications of essential interfaces are not available on product schedule Size underestimate Project and The size of the system has been underestimated. product CASE tool under- Product CASE tools which support the project do not perform as performance anticipated Technology change Business The underlying technology on which the system is built is superseded by new technology. Product competition Business A competitive product is marketed before the system is completed. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 25
26.
The risk management
process Risk identification • Identify project, product and business risks; Risk analysis • Assess the likelihood and consequences of these risks; Risk planning • Draw up plans to avoid or minimise the effects of the risk; Risk monitoring • Monitor the risks throughout the project; ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 26
27.
The risk management
process Riskof a ListandRi Risk p Risk identific mo Risk Priorit Ri risks as list plan ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 27
28.
Risk identification
Technology risks. People risks. Organisational risks. Requirements risks. Estimation risks. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 28
29.
Risks and risk
types Risk type Possible risks Technology The database used in the system cannot process as many transactions per second as expected. Software components that should be reused contain defects that 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 management are responsible for the project. Organisational financial problems force reductions in the project budget. Tools The code generated by CASE tools is inefficient. CASE tools cannot be integrated. Requirements Changes to requirements that require major design rework are proposed. Customers fail to understand the impact of requirements changes. 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 2004 Software Engineering, 7th edition. Chapter 5 Slide 29
30.
Risk analysis
Assess probability and seriousness of each risk. Probability may be very low, low, moderate, high or very high. Risk effects might be catastrophic, serious, tolerable or insignificant. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 30
31.
Risk analysis (i)
Risk Probability Effects Organisational financial problems force reductions in Low Catastrophic the project budget. It is impossible to recruit staff with the skills required High Catastrophic for the project. Key staff are ill at critical times in the project. Moderate Serious Software components that should be reused contain Moderate Serious defects which limit their functionality. Changes to requirements that require major design Moderate Serious rework are proposed. The organisation is restructured so that different High Serious management are responsible for the project. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 31
32.
Risk analysis (ii)
Risk Probability Effects The database used in the system cannot process as Moderate Serious many transactions per second as expected. The time required to develop the software is High Serious underestimated. CASE tools cannot be integrated. High Tolerable Customers fail to understand the impact of Moderate Tolerable requirements changes. Required training for staff is not available. Moderate Tolerable The rate of defect repair is underestimated. Moderate Tolerable The size of the software is underestimated. High Tolerable The code generated by CASE tools is inefficient. Moderate Insignificant ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 32
33.
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 2004 Software Engineering, 7th edition. Chapter 5 Slide 33
34.
Risk management strategies
(i) Risk Strategy Organisational Prepare a briefing document for senior management financial problems showing how the project is making a very important contribution to the goals of the business. Recruitment Alert customer of potential difficulties and the problems possibility of delays, investigate buying-in components. Staff illness Reorganise team so that there is more overlap of work and people therefore understand each other’s jobs. Defective Replace potentially defective components with bought- components in components of known reliability. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 34
35.
Risk management strategies
(ii) Risk Strategy Requirements Derive traceability information to assess requirements changes change impact, maximise information hiding in the design. Organisational Prepare a briefing document for senior management restructuring showing how the project is making a very important contribution to the goals of the business. Database Investigate the possibility of buying a higher- performance performance database. Underestimated Investigate buying in components, investigate use of a development time program generator ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 35
36.
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 2004 Software Engineering, 7th edition. Chapter 5 Slide 36
37.
Risk indicators Risk type
Potential indicators Technology Late delivery of hardware or support software, many reported technology problems People Poor staff morale, poor relationships amongst team member, job availability Organisational Organisational gossip, lack of action by senior management Tools Reluctance by team members to use tools, complaints about CASE tools, demands for higher-powered workstations Requirements Many requirements change requests, customer complaints Estimation Failure to meet agreed schedule, failure to clear reported defects ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 37
38.
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 which continue throughout the course of a project. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 38
39.
Key points
A project milestone is a predictable state where a formal report of progress is presented to management. Project scheduling involves preparing various graphical representations showing project activities, their durations and staffing. Risk management is concerned with identifying risks which may affect the project and planning to ensure that these risks do not develop into major threats. ©Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 39
Descargar ahora