Project Management for Information Systems Essay

3604 Words15 Pages
Project Management for Information Systems Abstract Information systems (IS) projects are vulnerable to resource cutbacks and the increasing complexity of systems and advances in information technology make finding the right personnel difficult and the associated development costs high. Good project management is essential for success. Some alignment methodologies include IBM's business systems planning (BSP), Robert Holland's strategic systems planning, James Martin's (1989) information engineering and method/1 from Anderson Consulting. Critical success factors (Rockart, 1979) methodology focuses on identifying key information needs of senior executives and building information systems around those key needs. Williams,…show more content…
Information systems (IS) projects are often seen as being vulnerable to cutbacks in resources. Combined with the increasing complexity of system design and the rapid advances in information technology can make project management difficult due to the lack of experienced personnel and the associated high costs. These pressures force project managers to optimize the use of allocated resources to ensure that IS projects are delivered on time and on budget. IS has become integral to the core business and helps to facilitate management decisions allowing improved ability to anticipate, respond, and react to the growing demands of the marketplace. Now, more than ever, effective business strategy centers on aggressive, efficient use of information technology and the project manager plays a central role to ensure that IS projects facilitate this need (Sumner, M 1999). Project Management Success requires excellent project management. The first step of any project plan is that scope should be established (Holland et al., 1999) and controlled to prevent continuous changes in requirements referred to scope creep. The scope must be clearly defined and be limited to avoid additional expenses of time and money. This can be achieved by limiting the amount of systems implemented, involvement of business units, and amount of business process reengineering needed. Any proposed changes should be
Open Document