|
Project ManagementProject Management is the discipline of planning, organizing and managing resources to bring about the successful completion of specific project goals and objectives.A project is a finite endeavor--having specific start and completion dates--undertaken to meet particular goals and objectives, usually to bring about beneficial change or added value. This finite characteristic of projects stands in contrast to processes, or operations--which is repetitive, permanent or semi-permanent functional work to produce products or services. In practice, the management of these two systems is often found to be quite different, and as such requires the development of distinct technical skills and the adoption of separate management. The primary challenge of project management is to achieve all of the project goals and objectives while honoring the preconceived project constraints. Typical constraints are scope, time and budget. The secondary—and more ambitious—challenge is to optimize the allocation and integration of inputs necessary to meet pre-defined objectives. History of project managementRoman Soldiers Building a Fortress, Trajan's Column 113 .D.Project management has been practiced since early civilization. Until 1900 projects were generally managed by creative architects and engineers themself, among those for example Christopher Wren (1632–1723) , Thomas Telford (1757-1834) and Isambard Kingdom Brunel (1806–1859) It has been since the 1950s, that organizations started applying systemic project management tools and techniques to complex projects. Henry Gantt (1861-1919), the father of planning and control techniques. As a discipline, Project Management developed from different fields of application including construction, engineering and defense. In the United States, the two forefathers of project management are Henry Gantt, called the father of planning and control techniques, who is famously known for his use of the Gantt chart as a project management tool, and Henri Fayol for his creation of the 5 management functions, which form the basis for the body of knowledge associated with project and program management. Both Gantt and Fayol were known as being students of Frederick Winslow Taylor's theories of scientific management. His work is the forerunner to modern project management tools including work breakdown structure (WBS) and resource allocation. The 1950s marked the beginning of the modern Project Management era. Project management was formally recognized as a distinct discipline arising from the management discipline. Again, in the United States, prior to the 1950s, projects were managed on an ad hoc basis using mostly Gantt Charts, and informal techniques and tools. At that time, two mathematical project scheduling models were developed. The "Critical Path Method" (CPM) developed in a joint venture by both DuPont Corporation and Remington Rand Corporation for managing plant maintenance projects. And the "Program Evaluation and Review Technique" or PERT, developed by Booz-Allen & Hamilton as part of the United States Navy's (in conjunction with the Lockheed Corporation) Polaris missile submarine program; These mathematical techniques quickly spread into many private enterprises. PERT network chart for a seven-month project with five milestones. At the same time, technology for project cost estimating, cost management, and engineering economics was evolving, with pioneering work by Hans Lang and others. In 1956, the American Association of Cost Engineers (now AACE International; the Association for the Advancement of Cost Engineering) was formed by early practitioners of project management and the associated specialties of planning and scheduling, cost estimating, and cost/schedule control (project control). AACE has continued its pioneering work and in 2006 released the first ever integrated process for portfolio, program and project management (Total Cost Management Framework). In 1969, the Project Management Institute (PMI) was formed to serve the interests of the project management industry. The premise of PMI is that the tools and techniques of project management are common even among the widespread application of projects from the software industry to the construction industry. In 1981, the PMI Board of Directors authorized the development of what has become A Guide to the Project Management Body of Knowledge (PMBOK Guide), containing the standards and guidelines of practice that are widely used throughout the profession. The International Project Management Association (IPMA), founded in Europe in 1967, has undergone a similar development and instituted the IPMA Competence Baseline (ICB). The focus of the ICB also begins with knowledge as a foundation, and adds considerations about relevant experience, interpersonal skills, and competence. Both organizations are now participating in the development of an ISO project management standard. Project Management Approaches:There are several approaches that can be taken to managing project activities including agile, interactive, incremental, and phased approaches.Regardless of the approach employed, careful consideration needs to be given to clarify surrounding project objectives, goals, and importantly, the roles and responsibilities of all participants and stakeholders. The Traditional ApproachA traditional phased approach identifies a sequence of steps to be completed. In the "traditional approach", we can distinguish 5 components of a project (4 stages plus control) in the development of a project:Typical development phases of a project
Not all the projects will visit every stage as projects can be terminated before they reach completion. Some projects don't have planning and/or monitoring stages. Some projects will go through steps 2, 3 and 4 multiple times. Many industries utilize variations on these stages. For example, in bricks and mortar architectural design, projects typically progress through stages like Pre-Planning, Conceptual Design, Schematic Design, Design Development, Construction Drawings (or Contract Documents), and Construction Administration. In software development, this approach is often known as the waterfall model, i.e., one series of tasks after another in linear sequence. In software development many organizations have adapted the Rational Unified Process (RUP) to fit this methodology, although RUP does not require or explicitly recommend this practice. Waterfall development can work for small tightly defined projects, but for larger projects of undefined or unknowable scope, it is less suited. The Cone of Uncertainty explains some of this as the planning made on the initial phase of the project suffers from a high degree of uncertainty. This becomes especially true as software development is often the realization of a new or novel product, this method has been widely accepted as ineffective for software projects where requirements are largely unknowable up front and susceptible to change. While the names may differ from industry to industry, the actual stages typically follow common steps to problem solving — "defining the problem, weighing options, choosing a path, implementation and evaluation." Critical Chain Project ManagementCritical Chain Project Management (CCPM) is a method of planning and managing projects that puts more emphasis on the resources required to execute project tasks. It is an application of the Theory of Constraints (TOC) to projects. The goal is to increase the rate of throughput (or completion rates) of projects in an organization. Applying the first three of the five focusing steps of TOC, the system constraint for all projects is identified as resources. To exploit the constraint, tasks on the critical chain are given priority over all other activities. Finally, projects are planned and managed to ensure that the critical chain tasks are ready to start as soon as the needed resources are available, subordinating all other resources to the critical chain.For specific projects, the project plan should undergo Resource Leveling, and the longest sequence of resource-constrained tasks is identified as the critical chain. In multi-project environments, resource leveling should be performed across projects. However, it is often enough to identify (or simply select) a single "drum" resource—a resource that acts as a constraint across projects—and stagger projects based on the availability of that single resource. Planning and feed back loops in Extreme Programming (XP) with the time frames of the multiple loops. Extreme Project ManagementIn critical studies of Project Management, it has been noted that several of these fundamentally PERT-based models are not well suited for the multi-project company environment of today. Most of them are aimed at very large-scale, one-time, non-routine projects, and nowadays all kinds of management are expressed in terms of projects.Using complex models for "projects" (or rather "tasks") spanning a few weeks has been proven to cause unnecessary costs and low maneuverability in several cases. Instead, project management experts try to identify different "lightweight" models, such as Agile Project Management methods including Extreme Programming for software development and Scrum techniques. The generalization of Extreme Programming to other kinds of projects is extreme project management, which may be used in combination with the process modeling and management principles of human interaction management. Event Chain MethodologyEvent chain methodology is the next advance beyond critical path method and critical chain project management.Event chain methodology is an uncertainty modeling and schedule network analysis technique that is focused on identifying and managing events and event chains that affect project schedules. Event chain methodology helps to mitigate the negative impact of psychological heuristics and biases, as well as to allow for easy modeling of uncertainties in the project schedules. Event chain methodology is based on the following major principles.
|