The challenge addressed in this article is that of using earned value in an IT project of less than US$20 million with multiple solution partners, fixed cost contracts, no labor cost data, and an 18-month deadline. The discussion presents an example of an innovative use of a research and development (R&D)–based earned value technique. The software project overview is presented, traditional earned value reviewed, the derivation of the R&D approach is discussed, and the article closes with a look at the organizational benefit of the technique.
535 items found
This article presents a variant on the use of schedule performance index (SPI) and schedule variance (SV) to manage schedule performance and includes a description, rationale, and explanation on how to apply the technique. An actual project, as well as examples, are used to illustrate the value and application of the technique. A basic understanding of earned value management (EVM) is required to understanding the article, whereas actual practice using earned value management, schedule performance index, and schedule variance is recommended.
The most widely used project management methodology is the waterfall model. In this model the progress of a project is seen flowing steadily downwards (like a waterfall) through the phases of conception, initiation, analysis, design (validation), construction, testing and maintenance. It should be apparent that this model has its origins in the manufacturing and construction industries. And that raises a question: Do all information systems projects need to follow the same model?
Reaching the goals in a project that involves plant shutdowns depends on many factors. This article seeks to establish a set of recommendations for the preparation of Plant Shutdowns based on the experience of the Nomex® Fiber Expansion Project by DuPont® in Asturias (Spain).
Challenges of Project Management for the Integration of Organizations Into Mergers and Acquisitions Processby
This article examines the processes of mergers and acquisitions, with a focus on programs and projects for the integration of the companies. It analyzes the main reasons for success and failure and considers the mistakes to be avoided, within the context of the concepts and processes for managing projects and programs of A Guide to the Project Management Body of Knowledge (PMBOK® Guide)-Fourth Edition, as well as on the basis of reports and experiences of companies that have experienced complex integrations. Project managers are challenged to deal with issues such as cultural influence, strategy, planning of the integration, and especially the management of people, as crucial elements to the success of these projects.
Scenario: A particular software development project is described as critical by the organization that initiated it, but it is difficult to acquire the resources needed to get it done. The needed people and assets are always busy with other projects that higher-level managers insist get done first. The problem described above is an example of a lack of functional governance processes and its effect on IT project management. This paper describes the identifying concepts and features of governance, how it affects IT project management, and some practical examples of what can be done when governance is not functioning.
Reporting the results of what your PMO achieves helps define the value that your PMO provides. This article has some tips on how to produce meaningful reports for a variety of audiences. In this article, "PMO" can mean project, program or portfolio management office.
The goal of this article is to offer practical strategies that will help you manage change effectively. The background and examples in this document have an IT bias, because the author took many ideas and examples from recent experiences managing change for 2 years in a $US20 million dollar database migration project. This project had it all-extended duration, large number of critical business intelligence applications in scope, two external vendors, and several other "critical" projects taking place in the same time frame. Change had to be managed or change would have devoured the project.
Why do design changes, mismatched parts, repetitive safety problems, or high rates of returns allow some businesses to continue "in the pink," while other similar businesses suffer the blues? If problems like these are getting you down, you may have the "configuration management blues." Good configuration management is necessary to keep your products good, your projects on track, and your whole group playing together.
Visual Ishikawa Risk Technique (VIRT) is a technique that is consistent with the Identify Risks process group of the PMBOK® Guide and uses a risk breakdown structure as its main principle artefact. However, it differs in that it uses the Ishikawa diagram (commonly also known as a fishbone, or cause and effect diagram), for the risk structure, to create a graphic view, as opposed to being text based or tabular.