Project Recovery


Book Description

Best practices for picking up the pieces when projects fail There are plenty of books available offering best practices that help you keep your projects on track, but offer guidance on what to do when the worst has already happened. Some studies show that more than half of all large-scale project fail either fail completely, or at least miss targeted budget and scheduling goals. These failures cost organizations time, money, and labor. Project Recovery offers wise guidance and real-world best practices for saving failed projects and recovering as much value as possible from the wreckage. Since failing project cannot be managed using the same lifecycle phases employed with succeeding projects, most project management professionals are unprepared to tackle the challenge of project recovery. This book presents valuable case studies and a recovery project lifecycle to help project managers identify and respond effectively to a troubled project. Includes case studies and best practices for saving failing projects or recovering projects that have already failed Written by experience project manager Howard Kerzner, the author of Project Management Best Practices, Third Edition Features proven techniques for performing project health checks and determining the degree of failure and the recovery options available Includes a new recovery lifecycle that includes phases and checklists for turning around failing projects With comprehensive case studies, checklists, worksheets, and cross listings to the appropriate project management body of knowledge, Project Recovery offers a much needed lifeline for managers facing the specter of failure.




Rescue the Problem Project


Book Description

Rescue the Problem Project provides project managers, executives, and customers with ways to accurately assess issues and fix problems. Many books explain how to run a project, but only this one shows how to bring it back from the brink of disaster.




Project Flop


Book Description

The only class I ever failed in college was Intro to Art Education. If you put this book down and stop reading right now I will totally understand. If you keep reading, you will learn that over the years, I've frequently clashed and often collided and have had plenty of failures in the world of art education. My college, The School of Visual Arts (SVA) is located on 23rd Street on the island of Manhattan. As the course title suggests, Intro to Art Education was designed to provide those considering a possible career as an art educator a look at the process. I can't truly remember why I enrolled in the class. I can only assume I had fond memories of being in my high school art class and saw this as an avenue back. I soon would learn there would be no nostalgia. I don't recall ever meeting in a classroom on SVA's facilities. I do remember meeting at a local elementary school. There, the course instructor taught a lesson to the elementary school children while her college students (including me) watched her teach. After the lesson, when the elementary students had left the room, we would discuss, evaluate, and critique the events of the day. Eventually, I believe the students would be preparing our own lessons and taking turns teaching the class. I use the word “believe” because I never found out. I stopped going to class. I stopped going because I didn't understand the “edu-speak” the teacher used. Words like curriculum and standards. I stopped going because none of this was creative or experimental or fun. I stopped going because I came to the realization that art education was about objectives and summaries and not about art at all. At least, that's what I thought.I went to student services to withdraw from the class. I was informed that it was too late. The deadline to drop a class without it being on my permanent record had passed. If I didn't return to class, I would fail. Fail? What did I care? I didn't need to worry about failing this class because I would never, ever become an art teacher.




Fail-Safe Management


Book Description

There are five critical rules to keep in mind in development projects, to avoid implementation failure: If you do not know where you are going, ask the right questions; Keep your champions close, but your naysayers closer; Know that informal networks matter; Find and remove bottlenecks; Build the ship as it sails.




Why Projects Fail


Book Description

We are all involved at some time in our lives in projects, if not professionally then in our private and community lives. Some projects fail completely and many more disappoint. We frequently hear reports of IT, construction, engineering, and personal projects failing by going over budget, or running late, or failing to meet the client’s expectations; or all three. This book deals with the nine features that almost all failing projects share. In this easy to read book, the author uses his nine laws of project design and control to lead the reader through the traps that that can catch out not only project managers but also the project client and other members of a project community. This book is not a treatise of project management theory but practical guide, based on wide experience and the study of the causes of project failure, aimed at the professional and amateur alike.




Software Development Failures


Book Description

An empirically based study of why software development failures happen, and the lessons we can learn. Failed or abandoned software development projects cost the U.S. economy alone billions of dollars a year. In Software Development Failures, Kweku Ewusi-Mensah offers an empirically grounded study that suggests why these failures happen and how they can be avoided. Case studies analyzed include the well-known Confirm travel industry reservation program, FoxMeyer's Delta, the IRS's Tax System Modernization, the Denver International Airport's Baggage Handling System, and CODIS. It has been estimated that one-third of software development projects fail or are abandoned outright because of cost overruns, delays, and reduced functionality. Some consider this an acceptable risk—that it is simply the cost of doing business. Ewusi-Mensah argues that understanding the factors involved in development failures will help developers and businesses bring down the rate of software failure and abandoned projects. Ewusi-Mensah explores the reasons software development projects are vulnerable to failure and why issues of management and organization are at the core of any failed project. He examines these projects not from a deterministically technical perspective but as part of a complex technical and social process; he proposes a framework of factors that contribute to the decision to abandon a project and enumerates the risks and uncertainties inherent in each phase of a project's life cycle. Exploring the multiplicity of factors that make software development risky, he presents empirical data that is reinforced by analyses of the reported cases. He emphasizes the role of the user in the development process and considers the effect of organizational politics on a project. Finally, he considers what lessons can be learned from past failures and how software development practices can be improved.




Stop IT Project Failure Through Risk Management


Book Description

This book is about information systems development failures and how to avoid them. It considers what goes wrong with information systems development projects and what actions may be taken to avoid potential difficulties.The reduction of the impact,or even the elimination of the problems,is discussed in terms of an information systems risk management programme. Stop I.T.Project failure helps to ensure that IS project managers are successful in helping to deliver application systems. However, IS development risk can never be entirely eliminated and consequently the practitioner needs to bear in mind that an IS development project is never without risk, and hence there is a continuing potential for something to go wrong. The book covers the key issues and variables and makes specific practical suggestions about the good management practice that is required to implement IS project risk processes. Dr. Dan Remenyi has spent more than 25 years working in the field of corporate computers and information systems. He has worked with computers as an IS professional, business consultant and user. In all these capacities he has been primarily concerned with benefit realisation and obtaining the maximum value for money from the organisations' information systems investment and effort. He has worked extensively in the field of information systems project management, specialising in the area of project risk identification and management. He has written a number of books and papers in the field of IT management and regularly conducts courses and seminars as well as working as a consultant in this area. Dr.Dan Remenyi holds a B.Soc.Sc., an MBA and a PhD. He is a Visiting Professor at Chalmers University of Technology in Gothenberg, Sweden and an associate member of faculty at Henley Management College in the United Kingdom.




How to Save a Failing Project


Book Description

You CAN Turn Around A Failing Project! Poor project results are all too common and result in dissatisfied customers, users, and project staff. With countless people, goals, objectives, expectations, budgets, schedules, deliverables, and deadlines to consider, it can be difficult to keep projects in focus and on track. How to Save a Failing Project: Chaos to Control arms project managers with the tools and techniques needed to address these project challenges. The authors provide guidance to develop a project plan, establish a schedule for execution, identify project tracking mechanisms, and implement turnaround methods to avoid failure and regain control. With this valuable resource you will be able to: • Identify key factors leading to failure • Learn how to recover a failing project and minimize future risk • Better analyze your project by defining proper business objectives and goals • Gain insight on industry best practices for planning




Situational Project Management


Book Description

Most project managers would agree that every project is unique. But not all project managers would agree that the best way to manage a unique project is unique. Many still cling to the old practice of having a methodology that is applied to all projects. "One size fits all" is still in common use, and this approach has proven to lead to project failure. Flexibility, situational intelligence, and creativity are essential to deliver project success. The need to recognize and master ever-changing requirements and environmental conditions is a tough challenge for professional project managers. The same practices that led to success yesterday may cause failure today. Selecting favorable responses to a given situation is often the most critical factor of the dynamics of success and failure. This book is designed to help project professionals assess a situation, predict the appropriate approach, methodology and achieving styles, and then apply them in a situational fashion. To guide project managers in selecting the appropriate responses, Situational Project Management (SitPM) shows how to assess a given project, determine its unique characteristics, and select the appropriate methods to complete the project. With this book, projects managers can use SitPM to develop profiles of their projects on the basis of the projects’ physical characteristics, the project teams’ behavioral characteristics, the enterprise environment, and the market environments receiving project deliverables. These profiles help project managers to determine the appropriate project life cycle approach and leadership style. The book also explores various ways to engage stakeholders on the basis of a project’s SitPM profile. The book’s author, Oliver F. Lehmann, has developed a set of templates to apply SitPM in practice. It can be downloaded from www.oliverlehmann.com/SitPM/Templates.zip.




Grand Successes and Failures in IT: Public and Private Sectors


Book Description

This book constitutes the refereed proceedings of the IFIP WG 8.6 International Working Conference on Transfer and Diffusion of IT, TDIT 2013, held in Bangalore, India, in June 2013. The 35 revised full papers presented together with an invited paper, 12 short papers and 3 poster papers were carefully reviewed and selected from 65 submissions. The full papers are organized in the following topical sections: IS success and failure; studies of IT adoption; software development; IT in the public sector; and theory and methods.