Escolar Documentos
Profissional Documentos
Cultura Documentos
Probably the most time-consuming project management activity. Continuous activity . Plans must be regularly revised as new information becomes available. Different types of plan may be developed to support the main project plan that is concerned with schedule and budget.
Slide 1
Informal planning projects involving few activities ,resources, constraints and inter-relationships can be visualized and planned informally.
Formal planning when a project crosses a certain threshold level of size and complexity, informal planning has to be substituted by formal planning.
Slide 2
Functions of planning
Provide a basis for organizing the work on the project Allocate responsibilities to individuals Provide a means of communication and coordination of all those involved in the project. Induce people to look ahead. Develop a sense of urgency and time consciousness Establish the basis for monitoring and control.
Software Engineering, 7th edition. Chapter 5 Slide 3
Areas of Planning
A comprehensive project planning covers the following: Planning the project work- The activities must be identified. They should be properly scheduled and sequenced. Planning the manpower and organizationestimate the manpower requirementsmanagers, technologists, operators, and others
Slide 4
(------- contd)
Planning the money- The expenditure must be budgeted in a time-phased manner Planning the information system The information required for monitoring the project must be defined
Slide 5
Project development and preliminary engineering Bidding and contract negotiation Engineering design Purchase and procurement Construction Commissioning
Slide 6
2.
Rolling wave concept when detailed planning is done for one stage, summary planning would be done for the remaining stages. Integration concept - planning for all the stages must be integrated. It stems from the inter-relationship among various stages of the project.
Slide 7
Tools of planning
Bar chart , also referred to as Gantt chart or the multiple activity chart. Net work techniques
Slide 8
Bar chart
-
is a pictorial device in which the activities are represented by horizontal bars on the time axis
Advantages of bar chart: Simple to understand Can be used to show progress Can be used for manpower planning
Slide 9
Can not show inter-relationship among activities on large and complex projects Physical limit to the size of the bar chart may limit its application Can not easily incorporate frequent changes in the project
Slide 10
Network techniques
In these techniques the activities, the events and their inter-relationships are represented by a net work diagram, also called arrow diagram. These are more sophisticated than the traditional bar chart. Advantages: (i) They can effectively handle inter-relationships among project activities (ii) Timely identification of the activities which are critical
Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 11
(contd..)
(ii)Timely identification of the activities which are critical to the completion of the project (iii) They can handle very large and complex projects (iv) They can be easily computerized and updated Drawbacks: (i) Being more complicated the project personnel may not be able to understand easily. (ii) The do not define an operational schedule which tells who does what and when.
Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 12
Slide 13
Introduction. Project organisation. Risk analysis. Hardware and software resource requirements. Work breakdown. Project schedule. Monitoring and reporting mechanisms.
Slide 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.
Slide 15
Slide 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.
Slide 17
Slide 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.
Slide 19
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.
Slide 20
Duration (days) 8 15 15 10 10 5 20 25 15 15 7 10
Dependencies
T1 (M1) T2, T4 (M2) T1, T2 (M3) T1 (M1) T4 (M5) T3, T6 (M4) T5, T7 (M7) T9 (M6) T11 (M8)
Slide 21
M1
M3
T6 2 0 d ays T7
25/7 /03 M2
10 d ays T5
Fin is h
Slide 23
Slide 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.
Slide 25
Risk identification
Identify project, product and business risks;
Assess the likelihood and consequences of these risks; Draw up plans to avoid or minimise the effects of the risk; Monitor the risks throughout the project;
Risk analysis
Risk planning
Risk monitoring
Slide 26
Slide 27
Risk identification
Technology risks. People risks. Organisational risks. Requirements risks. Estimation risks.
Slide 28
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.
Slide 29
Risk planning
Consider each risk and develop a strategy to manage that risk. Avoidance strategies
The probability that the risk will arise is reduced; The impact of the risk on the project or product will be reduced;
Minimisation strategies
Contingency plans
If the risk arises, contingency plans are plans to deal with that risk;
Slide 30
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.
Slide 31
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.
Slide 32
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.
Slide 33