1 / 43

Dr. Honghui Deng

MIS 746 IS Project Management. Dr. Honghui Deng. Associate Professor MIS Department UNLV. Session 7. Video 11 Project Cost/Completion. Session 7. IS Project Growth. Corcoran (1997): billions spent on technology every year Sources users top management within information systems

ishmael-benjamin
Download Presentation

Dr. Honghui Deng

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MIS 746 IS Project Management Dr. Honghui Deng Associate Professor MIS Department UNLV

  2. Session 7. Video 11 Project Cost/Completion

  3. Session 7. IS Project Growth • Corcoran (1997): billions spent on technology every year • Sources • users • top management • within information systems • Process • idea • estimate benefits, costs

  4. IS Project Motivation • Cost cutting/avoidance • Revenue maintenance/enhancement • Entering new markets • data mining • Gaining market share

  5. Session 7. Cost Estimates • The aggregate cost of work units described in the work breakdown structure. • The work unit approach makes cost estimating more manageable. • There are situations where an overall cost of a project is required for the initial decision and before WBS is done.

  6. Estimation Pitfalls • INTANGIBLES • nebulous benefits • better decision making • HIDDEN OUTCOMES • time, budget subject to great error • CHANGE • technology changes rapidly • outdating many good project ideas

  7. Session 7. Costs • Tangible – easier to estimate. • E.g., routers, switches, connectors, cables, servers, and human resources. • Intangible – difficult to evaluate. • E.g., cost benefit analysis of outsourcing or offshoring information system function in terms of security, privacy, know how, innovation, etc.

  8. Session 7. Costs • Direct – associated with a work unit • E.g., hours worked on a unit or the portion of management time (direct overhead costs) used for a work unit. • Indirect – difficult to assign • E.g., promotional expenses for the entire organization; difficult to prorate portion of this cost to a work unit or a project.

  9. Evaluation Techniques • Economic & Financial • payback 68% • cost-benefit 63% • npv/irr 40% • Multifactor • checklist 38% • project profile 26% • scoring/rating models 26% • multicriteria 11% • Mathematical Programming 18% • Expert Systems 6%

  10. Session 7. Payback analysis • Payback period – the length of time that it takes to recover the amount of money invested in the technology. • Payback occurs when the cumulative benefits are greater than cumulative costs. • For short-term investors, the payback period may be only a couple of years.

  11. Session 7. Payback analysis for two projects

  12. Session 7. Net Present Value • The formula for calculating NPV is: NPV = ∑t=1 …n A/(1+r)t where t represents the year in which cash flow occurs, A represents the amount of cash flow for that year, and r represents the discount rate. • Using a specified rate of interest, this formula sums up the present value for the number of years that estimates have been made.

  13. Session 7. NPV example • The present value of $3,000 cost projected for the third year of a project with an interest rate of 15% is $1972.50; calculated as: $3000 * 1/(1+0.15)3 or $3000 * 0.6575 = $1972.50 • If the projected revenue for the same project in the third year is $2,000 then the present value will be $1512.20; calculated as: $2000 * 1/(1+0.15)3 or $2000 * 0.6575 = $1512.30

  14. Session 7. Discount factors at 15%

  15. Session 7. Payback analysis for Project A

  16. Session 7. NPV for Project A • Year 1 = .8696 * ($20,000) = ($17,392) • Year 2 = .7561 * ($20,000) = ($15,122) • Year 3 = .6575 * $20,000 = $13,150 • Year 4 = .5718 * $30,000 = $17,154 • Year 5 = .4972 * $25,000 = $12,430 • Year 6 = .4323 * $15,000 = $6,485 NPV (Project A) = ∑t=1 …n A/(1+r)t = $16,705

  17. Session 7. ROI analysis for Project A

  18. Session 7. ROI analysis for Project B

  19. Session 7. ROI – Projects A & B • ROI for Project A: ($66,159 – $49,455)/49,455 * 100 = 33.8% • ROI for Project B: ($81,047 – $60,872)/60,872 * 100 = 33.1%

  20. Session 7. Caution • There is a risk in using a single measure to evaluate the potential contribution of a project. • Many organizations put a limit on their project payback period. • Many would use a minimum rate of return on investment. • There are pros and cons to having rigid standards. • IT investment is treated differently.

  21. Session 7. Sources of estimates • Experience – individuals within the organization. • this method considers workplace culture, talent pool, interorganizational relations, and HR policies. • Overestimation? • Underestimation? • ‘Safe’ estimates?

  22. Session 7. Sources of estimates • Documentation – archival information from previous projects. • Relatively current? • Similar projects? • Free from bias? Politics? • Based on actual recorded numbers. • Adjustment may be necessary if changes have occurred since the document was prepared – new laws, new equipment, change in working hours, and holidays.

  23. Session 7. Sources of estimates • Expert opinion – widely used and includes a broad pool of internal and external experts. • Similar to experience in pros and cons • Used for new and innovative systems where little record exists. • More formalized and expensive. • May require visits by external experts and sharing of information.

  24. Session 7. Considerations • A combination of internal and external estimates, while costly, has advantages. • Team members should be involved with providing estimates but the project manager must be aware of biases. • Provide supporting material on methods of estimation. • Establish guidelines for cost and time estimation.

  25. Session 7. Considerations • Based on history and experience, project managers may adjust estimates given by individuals. • This, in turn, will result in further adjustment (overestimation or underestimation) by those providing estimates. • This cycle creates ‘game play’ and a non-productive environment. • It may be necessary to work out some kind of reward for reliable and accurate estimates.

  26. Session 7. Hints • Use work units and bottom-up approach. • Define clearly work units and tasks. • Avoid memory recollection. • Involve team members to improve commitments and match tasks and skills. • Obtain multiple estimates: • The bestcase scenario. • The most probable scenario. • The worstcase scenario. • Assign weights to these estimates.

  27. Session 7. Multiple estimates • Use average scores and variance. • Provide contingency resources for estimates with large variance. • Calculate ‘upper limit’ and ‘lower limit’ measures for project duration. • Example: A project is estimated to take 165 hours to complete with a standard deviation of 29 hours. Assuming + and – 3 standard deviations, we will have:

  28. Session 7. Multiple estimates • The project upper limit: (3 * 29 + 165) = 252 hours • The project lower limit: (-3 * 29 + 165) = 78 hours • Upper limit as % of estimate: (252/165)100 = 152.73% • Lower limit as % of estimate: (78/165)100 = 47.27% There is a high probability that the project will be complete within 78 to 252 hours. The project completion time may be over extended or under extended by about 53%.

  29. Session 7. Phase estimating • Sometimes, due to uncertainty, estimates are feasible for initial phase only. • Only rough estimates of subsequent phases are initially feasible. • Project development life cycle (initiation, planning, development, implementation, closure) can be the base for phase estimating. • Project owners and sponsors must commit to a project with incomplete information about cost and time – not always an easy situation.

  30. Session 7. Considerations • Estimates are used to request funding, make decisions, schedule, negotiate, set goals, evaluate performance, etc. • Events happen, technology advances, priorities change, and biases creep in. • Credibility of the estimates and those preparing them must be considered. • Methods, their appropriateness, strengths, and weaknesses must be explained. • Assume ‘normal conditions’ – free from extreme case assumptions.

  31. Session 7. Contingency plan • For out-of-ordinary situations. • Extreme or extraordinary situations. • Funds must be appropriated at the planning phase of the project development life cycle. • Document and communicate contingency situations. • Such funds are not directly accessible by the project manager. • Simply adding a margin to estimates must be avoided; suggests poor planning, interpreted as add-on slush money by watchful sponsors.

  32. Session 7. Risk analysis • Appropriate where there is uncertainty regarding activity duration. • Leads to developing alternative responses. • Includes prediction or likelihood of happening. • Includes estimate of risk impact • Depending on the nature and size of a project, it could be more or less extensive, detailed, or formalized. • Leads to a change management process.

  33. Session 7. Change management • Change is beneficial - innovative ideas or suggestions are often made by team members. • A change management committee can facilitate and encourage change proposals. • With the approval of management, additional resources can be provided through contingency funds.

  34. Session 7. Change management • Membership includes stakeholders from the entire organization. Change management committee must: • identify possible risks • predict the likelihood of risks happening • estimate risks impact • communicate risks to stakeholders • prepare alternative response.

  35. Session 7. Change management • Changes must be consistent with the overall goals and objectives of the organization and the broad scope of the project. • Responses to change requests must be timely, especially for time-sensitive changes. • Proposals to drastically change a project may replace the project with a new one.

  36. Session 6. Discussion question • Assume you are working for an organization that is keen to invest in information technology to improve employee innovation, productivity, customer satisfaction, and management control. However, top management in your organization has a short-term payback expectation for their technology investment. Explain to the leadership of your organization why such a policy may be dysfunctional in the long term.

  37. Session 6. Discussion question • This chapter argues that organizational game play and politics are a function of management decision-making style. Do you agree with this statement? Why? • Is it possible to totally eliminate organizational politics?

  38. Session 6. Discussion question • Assume you are an IT project manager. How would you deal with issues of politics and game play that affect time and cost estimates for your projects?

  39. Session 6. Discussion question • Would your reaction be the same overestimation and underestimation of cost and time? • When do you think ‘overestimation’ happens? ‘Underestimation’?

  40. Work Package Estimates

  41. Session 6. In-class assignment • Do exercise ? in Chapter 4 (payback analysis, NPV, and ROI for two projects).

More Related