Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering.

Similar presentations


Presentation on theme: "1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering."— Presentation transcript:

1 1 Software Engineering Muhammad Fahad Khan fahad@uettaxila.edu.pk Software Engineering Muhammad Fahad Khan fahad@uettaxila.edu.pk University Of Engineering & Technology Taxila,Pakistan

2 2 Today’s Class Project management (Ch 05) Today’s Class Project management (Ch 05)

3 3 Objectives To explain the main tasks undertaken by project managers To explain the main tasks undertaken by project managers To introduce software project management and to describe its distinctive characteristics To introduce software project management and to describe its distinctive characteristics To discuss project planning and the planning process To discuss project planning and the planning process To show how graphical schedule representations are used by project management To show how graphical schedule representations are used by project management To discuss the notion of risks and the risk management process To discuss the notion of risks and the risk management process

4 4 Topics covered Management activities Management activities Project planning Project planning Project scheduling Project scheduling Risk management Risk management

5 5 What is Project Management?

6 6

7 7 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 the software 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 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. Project management is needed because software development is always subject to budget and schedule constraints that are set by the organisation developing the software.

8 8 Project Management & Product Delivery

9 9 Software management distinctions The product is intangible. The product is intangible. The product is uniquely flexible. The product is uniquely flexible. Software engineering is not recognized as an engineering discipline with the same status as mechanical, electrical engineering, etc. 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. The software development process is not standardised.

10 10 Management activities Proposal writing. Proposal writing. Project planning and scheduling. Project planning and scheduling. Project costing. Project costing. Project monitoring and reviews. Project monitoring and reviews. Personnel selection and evaluation. Personnel selection and evaluation. Report writing and presentations. Report writing and presentations.

11 11

12 12 Project staffing May not be possible to appoint the ideal people to work on a project 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. Project budget may not allow for the use of highly- paid staff. Staff with the appropriate experience may not be available. Staff with the appropriate experience may not be available. An organisation may wish to develop employee skills on a software project. 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.ppo Managers have to work within these constraints especially when there are shortages of trained staff.ppoppo

13 13

14 14 Activity organization Activities in a project should be organised to produce tangible outputs for management to judge progress. 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. Milestones are the end-point of a process activity. Deliverables are project results delivered to customers. Deliverables are project results delivered to customers. The waterfall process allows for the straightforward definition of progress milestones. The waterfall process allows for the straightforward definition of progress milestones.

15 15 Process to get Milestones

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

17 17 Scheduling problems Estimating the difficulty of problems and hence the cost of developing a solution is hard. 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. 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. Adding people to a late project makes it later because of communication overheads.

18 18 Summary

19 19 Bar charts and activity networks Graphical notations used to illustrate the project schedule. 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. 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. Activity charts show task dependencies and the the critical path. Bar charts show schedule against calendar time. Bar charts show schedule against calendar time.

20 20

21 21 Task durations and dependencies

22 22

23 23 Activity network

24 24 Activity timeline

25 25 Staff allocation

26 26

27 27 Risk management Risk management is concerned with identifying risks and drawing up plans to minimise their effect on a project. 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 A risk is a probability that some adverse circumstance will occur Project risks affect schedule or resources Project risks affect schedule or resources Product risks affect the quality or performance of the software being developed Product risks affect the quality or performance of the software being developed Business risks affect the organisation developing the software Business risks affect the organisation developing the software

28 28 Software risks

29 29 Type of Risk Current Risks Current Risks Emerging Risks Emerging Risks Future Risks Future Risks

30 30

31 31 The risk management process Risk identification Risk identification Identify project, product and business risks Identify project, product and business risks Risk analysis Risk analysis Assess the likelihood and consequences of these risks Assess the likelihood and consequences of these risks Risk planning Risk planning Draw up plans to avoid or minimise the effects of the risk Draw up plans to avoid or minimise the effects of the risk Risk monitoring Risk monitoring Monitor the risks throughout the project Monitor the risks throughout the project

32 32 The risk management process

33 33 Risk identification Technology risks Technology risks People risks People risks Organisational risks Organisational risks Requirements risks Requirements risks Estimation risks Estimation risks

34 34 Risks and risk types

35 35 Risk analysis Assess probability and seriousness of each risk. Assess probability and seriousness of each risk. Probability may be very low, low, moderate, high or very high. Probability may be very low, low, moderate, high or very high. Risk effects might be serious, tolerable or insignificant. Risk effects might be serious, tolerable or insignificant.

36 36

37 37 Risk planning Consider each risk and develop a strategy to manage that risk. Consider each risk and develop a strategy to manage that risk. Avoidance strategies Avoidance strategies The probability that the risk will arise is reduced; The probability that the risk will arise is reduced; Minimisation strategies Minimisation strategies The impact of the risk on the project or product will be reduced; The impact of the risk on the project or product will be reduced; Contingency plans Contingency plans If the risk arises, contingency plans are plans to deal with that risk; If the risk arises, contingency plans are plans to deal with that risk;

38 38 Risk monitoring Assess each identified risks regularly to decide whether or not it is becoming less or more probable. 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. Also assess whether the effects of the risk have changed. Each key risk should be discussed at management progress meetings. Each key risk should be discussed at management progress meetings.

39 39 Key points Good project management is essential for project success. Good project management is essential for project success. The intangible nature of software causes problems for management. The intangible nature of software causes problems for management. Managers have diverse roles but their most significant activities are planning, estimating and scheduling. 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. Planning and estimating are iterative processes which continue throughout the course of a project.

40 40 Key points A project milestone is a predictable state where a formal report of progress is presented to management. 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. 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. 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.

41 41 Question & Review session For any query feel free to contact fahad@uettaxila.edu.pk fahad@uettaxila.edu.pk


Download ppt "1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering."

Similar presentations


Ads by Google