MIS COURSE: CHAPTER 14 MANAGING PROJECTS

Slides:



Advertisements
Similar presentations
Information Systems: the Foundation of E-Business (CIS 108) Exploring the business of value of IS and Managing Change Lecture NINE (14 th March 2005)
Advertisements

Copyright Kenneth M. Chipps Ph.D
SESSION 13 UNDERSTANDING THE BUSINESS VALUE OF SYSTEMS
UNDERSTANDING THE BUSINESS VALUE OF SYSTEMS AND MANAGING CHANGE
Moving from Analysis to Design
Essentials of Management Information Systems, 6e Chapter 14 Understanding the Business Value of Systems and Managing Change Chapter 14 Understanding the.
Understanding the Business Value of Systems and Managing Change
Chapter 14 Project Management: Establishing the Business Value of Systems and Managing Change.
13.1 © 2004 by Prentice Hall Management Information Systems 8/e Chapter 13 Understanding the Business Value of Systems and Managing Change 13 UNDERSTANDING.
14.1 © 2007 by Prentice Hall 14 Chapter Project Management: Establishing the Business Value of Systems and Managing Change.
Redesigning the Organization with Information System
Sheu 1 n Spectrum of Organizational Changes (& Impacts) –Paradigm shift / Reengineering / Rationalization /Automation n IS as Planned Org. Change Information.
IT Planning.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
The Analyst as a Project Manager
CHAPTER 9 DEVELOPING BUSINESS/IT STRATEGIES. IT Planning Planning an information system doesn’t start with bits, and bytes, or a Web site. It starts with.
Managing Projects
Charting a course PROCESS.
Scis.regis.edu ● CIS 480/BA 479: Managing Technology for Business Strategies Week 5 Dr. Jesús Borrego Regis University 1.
Chapter 14 Managing Projects.
Managing Projects Chapter 14 VIDEO
Chapter 14 Managing Projects.
Developing an IS/IT Strategy
An Integrated Control Framework & Control Objectives for Information Technology – An IT Governance Framework COSO and COBIT 4.0.
Module 4: Systems Development Chapter 12: (IS) Project Management.
PROJECT MANAGEMENT. A project is one – having a specific objective to be completed within certain specifications – having defined start and end dates.
14.1 © 2010 by Prentice Hall 14 Chapter Managing Projects.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 8 Moving from Analysis to Design.
3 1 Project Success Factors u Project management important for success of system development project u 2000 Standish Group Study l Only 28% of system development.
Lecture 4. IS Planning & Acquisition To be covered: To be covered: – IS planning and its importance Cost-benefit analysis Cost-benefit analysis Funding.
14 Chapter Managing Projects. Runaway projects and system failure Runaway projects: 30-40% IT projects Exceed schedule, budget Fail to perform as specified.
1.Upgrade bandwidth 2.Upgrade desktop operating systems 3.Increase the number of servers 4.Determine industry standards 5.Convert to VoIP Which of the.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
14.1 © 2007 by Prentice Hall 12 Chapter Project Management: Establishing the Business Value of Systems and Managing Change.
Managing Projects Chapter 14 VIDEO
14-1 Copyright © 2013 Pearson Canada Inc. Project Management, Business Value, and Managing Change Oleh : Kundang K Juman Project Management, Business Value,
Information Systems Week 14 Managing Projects.
14.1 © 2010 by Prentice Hall Managing Projects © 2010 by Prentice Hall LEARNING OBJECTIVES Identify and describe the objectives of project management.
6.1 Copyright © 2014 Pearson Education, Inc. publishing as Prentice Hall Managing Projects Chapter 14 VIDEO Video Case 1: Blue Cross Blue Shield: Smarter.
Phase-1: Prepare for the Change Why stepping back and preparing for the change is so important to successful adoption: Uniform and effective change adoption.
CHAPTER 14 MANAGING PROJECTS. Project Management (Introduction) These numbers vary based on the study but… We spend about $1 trillion on IT projects 3.
Chapter 11 Project Management.
Strategic Information Systems Planning
BUSINESS PLUG-IN B15 Project Management.
BUSINESS DRIVEN TECHNOLOGY
Information Systems Development
TIM 58 Continuing Ch 2: Project Management
Building Information Systems
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design in a Changing World, 4th Edition
Planning for Information System
Principles of Information Systems Eighth Edition
PLANNING TOOLS AND TECHNIQUES
The importance of project management
Understanding the Business Value of Systems and Managing Change
UNDERSTANDING THE BUSINESS VALUE OF SYSTEMS AND MANAGING CHANGE
Balanced Score Card and Transworld Auto Parts (A)
Reaching Goals and Objectives
“Plan the work. Work the plan.” ~ Old Saying
Why can a new information system be considered planned organizational change? An information system is a sociotechnical entity, an arrangement of both.
Strategic Human Resource Management
Recognization and management of RISK in educational projects
Building Information Systems
Introduction to Information Systems
The Capital Budget: Evaluating Capital Expenditures
Systems Analysis and Design Chapter1: Introduction
Project Management Process Groups
Project Management Chapter 11.
Module 2 Topics Information technology governance: Organization and planning for IS.
Time Scheduling and Project management
Presentation transcript:

MIS COURSE: CHAPTER 14 MANAGING PROJECTS Composed by DUONG TO DUNG, MAR 2019

CONTENT What are the objectives of PM and why is it so essential in developing ISs? What methods can be used for selecting and evaluating ISs projects and aligning them with the firm’s business goals? How can firms assess the business value of ISs? What are the principal risk factors in IS projects, and how can they be managed?

What are the objectives of PM and why is it so essential in developing ISs? There is a very high failure rate among IS projects. In nearly every organization, IS projects take much more time and money to implement than originally anticipated, or the completed system does not work properly. When an IS does not meet expectations or costs too much to develop, companies may not realize any benefit from there is investment, and the system may not be able to solve the problems for which it was intended. The development of a new system must be carefully managed and orchestrated, and the way a project is executed is likely to be the most important factor influencing its outcome. That’s why it’s essential to have some knowledge about managing IS projects and the reasons why they succeed or fail.

RUNAWAY PROJECTS AND SYSTEM FAILURE What are the objectives of PM and why is it so essential in developing ISs? RUNAWAY PROJECTS AND SYSTEM FAILURE How badly are projects managed? On average, private sector projects are underestimated by half in terms of budget and time required to deliver the complete system promised in the system plan. Many projects are delivered with missing functionality. A joint study by McKinsey and Oxford University found that large software projects on average run 66% over budget and 33% over schedule; as many as 17% of projects turn out so badly that they can threaten the existence of the company. Between 30 and 40% of all software projects are “runaway” projects that far exceed the original schedule and budget projections and fail to perform as originally specified.

What are the objectives of PM and why is it so essential in developing ISs? Consequences of Poor PM

What are the objectives of PM and why is it so essential in developing ISs?

What are the objectives of PM and why is it so essential in developing ISs?

What are the objectives of PM and why is it so essential in developing ISs? PROJECT MANAGEMENT OBJECTIVES + Project: is a planned series of related activities for achieving a specific business objective. + PM + Scope of a project: defines what work is/is not included in a project. + Time, Cost, Quality of a project + Risk

What methods can be used for selecting and evaluating ISs projects and aligning them with the firm’s business goals? MANAGEMENT STRUCTURE FOR IS PROJECT Each level of management in the hierarchy is responsible for specific aspects of systems projects, and this structure helps give priority to the most important systems projects for the organization.

What are the objectives of PM and why is it so essential in developing ISs? LINKING SYSTEMS PROJECTS TO THE BUSINESS PLAN: IS PLAN Identifies systems projects that will deliver most business value, links development to business plan Road map indicating direction of systems development, includes: Purpose of plan Strategic business plan rationale Current systems/situation New developments Management strategy Implementation plan Budget (See Table 14.1 on page 561)

What are the objectives of PM and why is it so essential in developing ISs? INFORMATION REQUIREMENTS AND KEY PERFORMANCE INDICATORS (KPIs) To develop an effective IS plan, the org. must have a clear understanding of both its long- and short-term information requirements. A strategic approach to info. requirements, strategic analysis, or critical success factors, argues that an org.’s info. requirements are determined by a small number of KPIs of managers. New ISs should focus on providing information that helps the firms meet these goals implied by KPIs.

What are the objectives of PM and why is it so essential in developing ISs? PORTFOLIO ANALYSIS Allows a company to objectively rate multiple alternative projects for their risk and potential benefits. Companies too often get locked into just one idea without understanding that multiple choices exist. There is always more than one way to meet the organization’s goals.

(See example on table 14.2 p. 564) What are the objectives of PM and why is it so essential in developing ISs? SCORING MODELS The scoring model is effective for comparing various alternatives in terms of their costs. This model can go a long way toward helping organizations determine the best course of action and quantify their decision making. And, if nothing else, it creates a dialog among the managers about strategic factors they should consider for the good of the firm. (See example on table 14.2 p. 564)

How can firms assess the business value of ISs? IS COSTS & BENEFITS + Tangible vs. Intangible Benefits: quantifiable or not + Capital Budgeting for IS: There are several methods for analyzing a new system in terms of dollars and cents using capital budgeting techniques. Each method measures the financial worth of the system by determining the difference between cash outflows and cash inflows. Payback Method: time required to pay back the initial investment. Accounting Rate of ROI: approximation of the accounting income earned. Net Present Value: amount of money an investment is worth, taking into account its cost, earnings, and the time value of money. Internal Rate of Return: rate of return or profit that an investment is expected to earn.

How can firms assess the business value of ISs? LIMITATIONS OF FINANCIAL MODELS There are limitations to each financial model used to evaluate new systems. As we’ve seen in the last few years, the hardware costs can change drastically within a short period of time. As soon as the system is installed, new technology can render it obsolete. How do you factor those realities into a financial evaluation model? Most of the time you can’t. On the other hand, you’ll remember that the costs of adding new users to an existing network is marginal according to Metcalfe’s Law and Network Economics. That must be factored into the financial models as well as elements of the TCO (total cost of ownership). It is not unusual for the personnel costs in the TCO model to be underestimated or even totally overlooked.

What are the principal risk factors in IS projects, and how can they be managed? DIMENSIONS OF PROJECT RISK The level of project risk is influenced by project size, structure, and level of technical expertise of the IS staff and project team. CHANGE MANAGEMENT AND THE CONCEPT OF IMPLEMENTATION Change is a given element in the business world. From mergers and acquisitions, to complete corporate purchases, to changing work processes and methodologies within the same company, change is hard on people and organizations. But change management is one of those necessary evils that keep companies in the lead or helps destroy them.

What are the principal risk factors in IS projects, and how can they be managed? CHANGE MANAGEMENT AND THE CONCEPT OF IMPLEMENTATION The Concept of Implementation Implementation of a new system is not just about how to put the hardware and software into place. You have to address and manage people and processes to make sure they are in sync with the hardware and software. In essence you become a change agent. You have to convince users that the system is going to improve their world and that the new will be better than the old. If people are going to lose their jobs because of the new system or if they are going to experience a significant difference in responsibilities, you must be clear in communicating those changes to them.

What are the principal risk factors in IS projects, and how can they be managed? CHANGE MANAGEMENT AND THE CONCEPT OF IMPLEMENTATION The Role of End Users Make users feel they own the new system instead of it being an enemy or something they should fear. That’s why we stress user involvement through the entire development process. The new system shouldn’t be a surprise on Monday morning! Familiarity doesn’t always breed contempt; it should breed acceptance when it comes to new information systems.

What are the principal risk factors in IS projects, and how can they be managed?

What are the principal risk factors in IS projects, and how can they be managed? CHANGE MANAGEMENT AND THE CONCEPT OF IMPLEMENTATION Management Support and Commitment Management support and commitment for new projects is required for these reasons: Creates a positive perception for both users and technical information services staff Ensures sufficient funding and resources are devoted to the project Implementing changes in work habits and procedures are easier Enforcing organizational realignments

What are the principal risk factors in IS projects, and how can they be managed? CHANGE MANAGEMENT AND THE CONCEPT OF IMPLEMENTATION Change Management Challenges for Business Process Reengineering, Enterprise Applications, and Mergers and Acquisitions 70% of all business process reengineering projects fail to deliver promised benefits. Key factor of the failures and successes is people. If the changes required by and in people are managed properly, then the success rate increases. The leading threats of BPR projects are: Dealing with fear and anxiety throughout the organization Overcoming resistance by key managers Changing job functions, career paths, and recruitment practices Training

What are the principal risk factors in IS projects, and how can they be managed? CHANGE MANAGEMENT AND THE CONCEPT OF IMPLEMENTATION Change Management Challenges for Business Process Reengineering, Enterprise Applications, and Mergers and Acquisitions Mergers and acquisitions that didn’t work out or were not cost effective. Many of the problems can be traced to employees who didn’t adapt to the changes or to poorly integrated systems. To ensure a successful merger managers must recognize: The realistic costs of integration The estimated benefits of economies in operation scope, knowledge, and time Any problematic systems that require major investments to integrate Any likely costs and organizational changes required to upgrade the IT infrastructure

What are the principal risk factors in IS projects, and how can they be managed? CONTROLLING RISK FACTORS Managing Technical Complexity You can use special tools to help you manage the implementation of a new information system (internal integration tools). It’s important that the project leaders and team members have the appropriate level of expertise and experience in the project’s technology. Otherwise, you should obtain it from outside sources. Formal Planning and Control Tools: Gantt chart, PERT chart Increasing User Involvement and Overcoming User Resistance Get users involved from the very beginning of a project and keep them involved. Use external integration tools to keep people involved and informed. Guard against destructive, although innocent, sabotage of the system (counterimplementation).

What are the principal risk factors in IS projects, and how can they be managed? CONTROLLING RISK FACTORS Increasing User Involvement and Overcoming User Resistance Some of the strategies you can use to overcome user resistance include: User participation User education and training Management edicts and policies Better incentives for users who cooperate Improve the end-user interface Solve organizational problems before introducing a new system

What are the principal risk factors in IS projects, and how can they be managed? GANTT CHART See full table of Gantt chart at Figure 14.4 on page 562

What are the principal risk factors in IS projects, and how can they be managed? PERT CHART

What are the principal risk factors in IS projects, and how can they be managed? DESIGNING FOR THE ORGANIZATION “Just what will this new system do for us?” That’s a very appropriate question but unfortunately, it’s often ignored. Everyone seems to get caught up in the hustle and bustle of the implementation process and they forget to address basic questions about the new system. An organizational impact analysis will help answer questions about org. structure changes, attitudes, decision making, and operations. Write down what we want the end result to be in terms of the org., this can be a great communication tool to explain to people how their jobs will be affected, to explain the changes required, and to help them plan the individual efforts required for a successful new system. How will the new system fit into the human element? That’s the idea behind ergonomics; getting human and machine to agree and complement each other.

What are the principal risk factors in IS projects, and how can they be managed? DESIGNING FOR THE ORGANIZATION Sociotechnical Design One way of addressing human and org. issues is to incorporate sociotechnical design practices into IS projects. Designers set forth separate sets of technical and social design solutions. The social design plans explore different workgroup structures, allocation of tasks, and the design of individual jobs. The proposed technical solutions are compared with the proposed social solutions. The solutions that best meet both social and technical objectives is selected for the final design. The resulting sociotechnical design is expected to produce an IS that blends technical efficiency with sensitivity to org. and human needs, leading to higher job satisfaction and productivity.

What are the principal risk factors in IS projects, and how can they be managed? PROJECT MANAGEMENT SOFTWARE TOOLS Because PM is so difficult, there are some great SW programs you can use to help you manage projects regardless of their size. The programs automate many of the mundane tasks such as defining tasks, assigning resources, establishing start and end dates, tracking progress, and creating and maintaining PERT and Gantt charts. Best of all, when one element of a project changes, it’s easy to see how other elements are affected. That will help you make better decisions about the project and keep track of the myriad of details. If your organization has several projects in the works, managers should consider using project portfolio management software to help track the proposals and projects against budgets and resource capacity. The software also helps manage dependencies among the projects and helps executives and managers determine the optimal mix and sequencing of projects.

CONTENT What are the objectives of PM and why is it so essential in developing ISs? What methods can be used for selecting and evaluating ISs projects and aligning them with the firm’s business goals? How can firms assess the business value of ISs? What are the principal risk factors in IS projects, and how can they be managed?

LET’S GO THROUGH THEM TOGETHER! END! THANK YOU! REVIEW QUESTIONS LET’S GO THROUGH THEM TOGETHER! END! THANK YOU!