Lecture 9 (02-06-2011)

374 views
304 views

Published on

software scheduling and risk management

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
374
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Lecture 9 (02-06-2011)

  1. 1. 1<br />Project Scheduling and Risk Management <br />
  2. 2. 2<br />Previous Discussion<br /> Function Point<br />Cocomo Model<br />Discussion<br />
  3. 3. 3<br />The Four P’s<br />People — the most important element of a successful project<br />Product — the software to be built<br />Process — the set of framework activities and software engineering tasks to get the job done<br />Project — all work required to make the product a reality<br />
  4. 4. 4<br />Stakeholders<br />Senior managerswho define the business issues that often have significant influence on the project.<br />Project (technical) managers who must plan, motivate, organize, and control the practitioners who do software work.<br />Practitionerswho deliver the technical skills that are necessary to engineer a product or application.<br />Customerswho specify the requirements for the software to be engineered and other stakeholders who have a peripheral interest in the outcome.<br />End-userswho interact with the software once it is released for production use.<br />
  5. 5. 5<br />How to lead?<br />How to organize?<br />How to collaborate?<br />How to motivate?<br />How to create good ideas?<br />Software Teams<br />
  6. 6. 6<br />Team Leader<br />The MOI Model<br />Motivation. The ability to encourage (by “push or pull”) technical people to produce to their best ability.<br />Organization. The ability to mold existing processes (or invent new ones) that will enable the initial concept to be translated into a final product.<br />Ideas or innovation. The ability to encourage people to create and feel creative even when they must work within bounds established for a particular software product or application.<br />
  7. 7. 7<br />Software Teams<br />The following factors must be considered when selecting a software project team structure ...<br />the difficulty of the problem to be solved<br />the size of the resultant program(s) in lines of code or function points<br />the time that the team will stay together (team lifetime)<br />the degree to which the problem can be modularized<br />the required quality and reliability of the system to be built<br />the rigidity of the delivery date<br />the degree of sociability (communication) required for the project<br />
  8. 8. 8<br />Organizational Paradigms<br />closed paradigm—structures a team along a traditional hierarchy of authority<br />random paradigm—structures a team loosely and depends on individual initiative of the team members <br />open paradigm—attempts to structure a team in a manner that achieves some of the controls associated with the closed paradigm but also much of the innovation that occurs when using the random paradigm<br />synchronous paradigm—relies on the natural compartmentalization of a problem and organizes team members to work on pieces of the problem with little active communication among themselves<br />suggested by Constantine [Con93]<br />
  9. 9. 9<br />Why Are Projects Late?<br />an unrealistic deadline established by someone outside the software development group<br />changing customer requirements that are not reflected in schedule changes;<br />an honest underestimate of the amount of effort and/or the number of resources that will be required to do the job;<br />predictable and/or unpredictable risks that were not considered when the project commenced;<br />technical difficulties that could not have been foreseen in advance;<br />human difficulties that could not have been foreseen in advance;<br />miscommunication among project staff that results in delays;<br />a failure by project management to recognize that the project is falling behind schedule and a lack of action to correct the problem<br />
  10. 10. 10<br />Scheduling Principles<br />compartmentalization—define distinct tasks<br />interdependency—indicate task interrelationship <br />effort validation—be sure resources are available<br />defined responsibilities—people must be assigned<br />defined outcomes—each task must have an output<br />defined milestones—review for quality<br />
  11. 11. 11<br />40-50%<br />15-20%<br />30-40%<br />Effort Allocation<br />“front end” activities<br /> customer communication<br /> analysis<br /> design<br /> review and modification<br />construction activities<br /> coding or code generation<br />testing and installation<br /> unit, integration<br /> white-box, black box<br /> regression <br />
  12. 12. 12<br />Defining Task Sets<br />determine type of project<br />assess the degree of rigor required<br />identify adaptation criteria<br />select appropriate software engineering tasks<br />
  13. 13. 13<br /> CPM<br /> Definition: In CPM activities are shown as a network of precedence relationships using activity-on-node network construction<br />Single estimate of activity time<br />Deterministic activity times<br />USED IN : Production management - for the jobs of repetitive in nature where the activity time estimates can be predicted with considerable certainty due to the existence of past experience.<br />
  14. 14. 14<br />Critical Path Analysis<br />
  15. 15. 15<br />The last activities that must be completed before an activity can begin<br />Precedence table<br />
  16. 16. 16<br />Activity on Arc Network <br />2<br />B(8)<br />A(3)<br />D(12)<br />1<br />5<br />3<br />E(10)<br />F(20)<br />C(7)<br />4<br />The network will build up with each mouse click, in the order you would construct it on paper. <br />
  17. 17. 17<br />Event Times <br />Earliest event timeEET<br />Latest event timeLET<br />Each event node needs two boxes, to mark in the event times.<br />2<br />B(8)<br />A(3)<br />D(12)<br />1<br />5<br />3<br />E(10)<br />F(20)<br />C(7)<br />4<br />
  18. 18. 18<br />Earliest Event Times <br />The EET for an event occurs when all activities leading into that event are complete.<br />3<br />2<br />B(8)<br />A(3)<br />42<br />12<br />D(12)<br />1<br />5<br />3<br />E(10)<br />0<br />F(20)<br />C(7)<br />4<br />22<br />To find EETs, work forwards through the network from the start node to the finish node.<br />
  19. 19. 19<br />Latest Event Times <br />The LET for an event is the latest it can occur without delaying subsequent events.<br />4<br />2<br />B(8)<br />A(3)<br />42<br />12<br />D(12)<br />1<br />5<br />3<br />E(10)<br />0<br />F(20)<br />C(7)<br />4<br />22<br />To find LETs, work backwards through the network from the finish node to the start node.<br />
  20. 20. 20<br />Critical Activities <br />Critical activities are activities that cannot run late. For critical activities:<br />Latest finish — Earliest start = length of activity<br />2<br />B(8)<br />A(3)<br />D(12)<br />1<br />5<br />3<br />E(10)<br />F(20)<br />C(7)<br />4<br />The green arrows mark the critical activities, which form the critical path. The critical path(s) must form a continuous route from the start node to the finish node.<br />
  21. 21. 21<br />Tasks<br />Week 1<br />Week 4<br />Week 3<br />Week n<br />Week 2<br />Task 1<br />Task 2<br />Task 3<br />Task 4<br />Task 5<br />Task 6<br />Task 7<br />Task 8<br />Task 9<br />Task 10<br />Task 11<br />Task 12<br />Timeline Charts<br />
  22. 22. 22<br />Use Automated Tools toDerive a Timeline Chart<br />
  23. 23. 23<br />Schedule Tracking<br />conduct periodic project status meetings in which each team member reports progress and problems.<br />evaluate the results of all reviews conducted throughout the software engineering process.<br />determine whether formal project milestones (the diamonds shown in Figure 27.3) have been accomplished by the scheduled date.<br />compare actual start-date to planned start-date for each project task listed in the resource table (Figure 27.4).<br />meet informally with practitioners to obtain their subjective assessment of progress to date and problems on the horizon.<br />use earned value analysis (Section 27.6) to assess progress quantitatively.<br />
  24. 24. 24<br />Earned Value Analysis (EVA)<br />Earned value<br />is a measure of progress<br />enables us to assess the “percent of completeness” of a project using quantitative analysis rather than rely on a gut feeling<br />
  25. 25. 25<br />Computing Earned Value-I<br />The budgeted cost of work scheduled (BCWS) is determined for each work task represented in the schedule. <br />BCWSi is the effort planned for work task i.<br />To determine progress at a given point along the project schedule, the value of BCWS is the sum of the BCWSi values for all work tasks that should have been completed by that point in time on the project schedule. <br />The BCWS values for all work tasks are summed to derive the budget at completion, BAC. Hence,<br />BAC = ∑ (BCWSk) for all tasks k<br />
  26. 26. 26<br />Computing Earned Value-II<br />Next, the value for budgeted cost of work performed (BCWP) is computed. <br />The value for BCWP is the sum of the BCWS values for all work tasks that have actually been completed by a point in time on the project schedule.<br />“the distinction between the BCWS and the BCWP is that the former represents the budget of the activities that were planned to be completed and the latter represents the budget of the activities that actually were completed.” [Wil99] <br />Given values for BCWS, BAC, and BCWP, important progress indicators can be computed:<br />Schedule performance index, SPI = BCWP/BCWS<br />Schedule variance, SV = BCWP – BCWS<br />SPI is an indication of the efficiency with which the project is utilizing scheduled resources.<br />
  27. 27. 27<br />Computing Earned Value-III<br />Percent scheduled for completion = BCWS/BAC<br />provides an indication of the percentage of work that should have been completed by time t.<br />Percent complete = BCWP/BAC<br />provides a quantitative indication of the percent of completeness of the project at a given point in time, t.<br />Actual cost of work performed, ACWP, is the sum of the effort actually expended on work tasks that have been completed by a point in time on the project schedule. It is then possible to compute<br />Cost performance index, CPI = BCWP/ACWP<br />Cost variance, CV = BCWP – ACWP<br />
  28. 28. 28<br />Project Risks<br />What can go wrong?<br />What is the likelihood?<br />What will the damage be?<br />What can we do about it?<br />
  29. 29. 29<br />Reactive Risk Management<br />project team reacts to risks when they occur<br />mitigation—plan for additional resources in anticipation of fire fighting<br />fix on failure—resource are found and applied when the risk strikes<br />crisis management—failure does not respond to applied resources and project is in jeopardy<br />
  30. 30. 30<br />Proactive Risk Management<br />formal risk analysis is performed<br />organization corrects the root causes of risk<br />TQM concepts and statistical SQA<br />examining risk sources that lie beyond the bounds of the software<br />developing the skill to manage change <br />
  31. 31. 31<br />Risk Management Paradigm<br />control<br />track<br />RISK<br />identify<br />plan<br />analyze<br />
  32. 32. 32<br />Risk Identification<br />Product size—risks associated with the overall size of the software to be built or modified.<br />Business impact—risks associated with constraints imposed by management or the marketplace.<br />Customer characteristics—risks associated with the sophistication of the customer and the developer's ability to communicate with the customer in a timely manner.<br />Process definition—risks associated with the degree to which the software process has been defined and is followed by the development organization.<br />Development environment—risks associated with the availability and quality of the tools to be used to build the product.<br />Technology to be built—risks associated with the complexity of the system to be built and the "newness" of the technology that is packaged by the system.<br />Staff size and experience—risks associated with the overall technical and project experience of the software engineers who will do the work.<br />
  33. 33. 33<br />Risk Components<br />performance risk—the degree of uncertainty that the product will meet its requirements and be fit for its intended use.<br />cost risk—the degree of uncertainty that the project budget will be maintained.<br />support risk—the degree of uncertainty that the resultant software will be easy to correct, adapt, and enhance.<br />schedule risk—the degree of uncertainty that the project schedule will be maintained and that the product will be delivered on time.<br />
  34. 34. 34<br />Risk Projection<br />Risk projection, also called risk estimation, attempts to rate each risk in two ways<br /> the likelihood or probability that the risk is real <br /> the consequences of the problems associated with the risk, should it occur. <br />The are four risk projection steps:<br />establish a scale that reflects the perceived likelihood of a risk<br />delineate the consequences of the risk<br />estimate the impact of the risk on the project and the product,<br />note the overall accuracy of the risk projection so that there will be no misunderstandings.<br />
  35. 35. 35<br />Building a Risk Table<br />Risk<br />Probability<br />Impact<br />RMMM<br />Risk<br />Mitigation<br />Monitoring<br />& <br />Management<br />
  36. 36. 36<br />Building the Risk Table<br />Estimate the probability of occurrence<br />Estimate the impact on the project on a scale of 1 to 5, where<br /> 1 = low impact on project success<br /> 5 = catastrophic impact on project success<br /> sort the table by probability and impact<br />
  37. 37. 37<br />Risk Exposure (Impact)<br />The overall risk exposure, RE, is determined using the following relationship [Hal98]:<br />RE = P x C<br />where <br />P is the probability of occurrence for a risk, and <br />C is the cost to the project should the risk occur.<br />
  38. 38. 38<br />Risk Exposure Example<br />Risk identification. Only 70 percent of the software components scheduled for reuse will, in fact, be integrated into the application. The remaining functionality will have to be custom developed.<br />Risk probability. 80% (likely).<br />Risk impact. 60 reusable software components were planned. If only 70 percent can be used, 18 components would have to be developed from scratch (in addition to other custom software that has been scheduled for development). Since the average component is 100 LOC and local data indicate that the software engineering cost for each LOC is $14.00, the overall cost (impact) to develop the components would be 18 x 100 x 14 = $25,200.<br />Risk exposure. RE = 0.80 x 25,200 ~ $20,200.<br />
  39. 39. 39<br />Risk Mitigation, Monitoring,and Management <br />mitigation—how can we avoid the risk?<br />monitoring—what factors can we track that will enable us to determine if the risk is becoming more or less likely?<br />management—what contingency plans do we have if the risk becomes a reality?<br />
  40. 40. 40<br />Risk Due to Product Size<br />Attributes that affect risk:<br />• estimated size of the product in LOC or FP?<br />• estimated size of product in number of programs, <br />files, transactions?<br />• percentage deviation in size of product from <br />average for previous products?<br />• size of database created or used by the product?<br />• number of users of the product?<br />• number of projected changes to the requirements <br />for the product? before delivery? after delivery?<br />• amount of reused software?<br />
  41. 41. 41<br />Risk Due to Business Impact<br />Attributes that affect risk:<br />• affect of this product on company revenue?<br />• visibility of this product by senior management?<br />• reasonableness of delivery deadline?<br />• number of customers who will use this product <br />• interoperability constraints<br />• sophistication of end users?<br />• amount and quality of product documentation that <br />must be produced and delivered to the customer?<br />• governmental constraints<br />• costs associated with late delivery?<br />• costs associated with a defective product?<br />
  42. 42. 42<br />Risks Due to the Customer<br />Questions that must be answered:<br />• Have you worked with the customer in the past?<br />• Does the customer have a solid idea of requirements?<br />• Has the customer agreed to spend time with you? <br />• Is the customer willing to participate in reviews?<br />• Is the customer technically sophisticated?<br />• Is the customer willing to let your people do their <br />job—that is, will the customer resist looking over your <br />shoulder during technically detailed work?<br />• Does the customer understand the software <br />engineering process?<br />
  43. 43. 43<br />Risks Due to Process Maturity<br />Questions that must be answered:<br />• Have you established a common process framework? <br />• Is it followed by project teams?<br />• Do you have management support for <br />software engineering <br />• Do you have a proactive approach to SQA? <br />• Do you conduct formal technical reviews?<br />• Are CASE tools used for analysis, design and <br />testing?<br />• Are the tools integrated with one another?<br />• Have document formats been established?<br />

×