Editorial | Viewpoints | Papers | Community |Scene | Publications
The
full text of featured papers are available as PDF files. Click on the full
text link in the summary to access the full content in PDF format.
by Patrick Weaver
The science of ‘scheduling’ as defined by Critical Path Analysis (CPA) will celebrate its 50th Anniversary on the 7th May 2007. In 1956/57 Kelly and Walker started developing the algorithms that became the ‘Activity-on-Arrow’ or ADM methodology for DuPont. The program they developed was trialed on plant shutdowns in 1957 and the first paper on critical path scheduling was published in 1958. The critical meeting to approve this project was held on the 7th May 1957 in Newark Delaware where DuPont and Remington Rand jointly committed US$226,400 to fund the development. This date seems the most appropriate ‘start point’ for a development process that borrowed from previous research and developments and continues to this day.
The PERT system was developed by the US military in parallel with CPM, but lagged CPM by 6 to 12 months (although the term ‘critical path’ was invented by the PERT team). Later the Precedence (PDM) methodology was published by Dr. John Fondahl in 1961 as a ‘non-computer’ alternative to CPM. Arguably, the evolution of modern project management is a direct consequence of the need to make effective use of the data generated by the schedulers in an attempt to manage and control the critical path.
Read the full text at A Brief History of Scheduling
by Rob Zanfardino, Senior Project/Program Manager
For those of you who ever watched the Pink Panther movie series written and directed by Blake Edwards and starring Peter Sellers, by far one of the most famous movie scenes is in the movie The Pink Panther Strikes Again. The scene starts when Inspector Clouseau the bumbling main character of the movie goes up to an inn keeper and asks for a room. During the conversation with the inn keeper the inspector says the following:
Inspector Clouseau: "Does yer dewg (dog) bite?”
Inn Keeper: “No”
Inspector Clouseau: “Nice Doggy” (he bends down to pet a dachshund - it snarls and bites him.)
Inspector Clouseau: ”I thought you said yer dewg did not bite!”
Inn Keeper: “Zat... iz (That is) not my dog!”
To this day when my wife Dawn and I want to laugh about a situation where we assumed one thing and it turned out to be something else we recite this scene to each other. If you look at the scene in the movie this could very well take place on any of your projects. If you analyze the scene Inspector Clouseau did what any reasonable person would ask when approaching an unknown pet, he asked a reasonable question but assumed the nearness of the individual accurately determined the ownership of the pet.
Mistaking ownership of a project can happen to any one of us while on a project. If you fail to ask the right questions as you determine your risk plan, if you fail to follow through with the series of right questions or you minimize the risk itself, you may unintentionally fail to capture the risk in its entirety and therefore it will come up to bite you somewhere in the project.
Read the full text at “Does Yer Dewg Bite?” Be It the Customer or Your Manager, Only If You Let Them
by: Curt Finch, CEO, Journyx
When payroll executives implement time and attendance systems to automate payroll, they often miss the chance to facilitate greater profitability throughout the entire company. These executives are, of course, payroll experts. They are usually not, however, experts at project management or billing automation.
The time data they collect, if collected appropriately, can also be used to automate project management, project costing, project tracking and project estimation improvement, as well as for internal, external and reverse billing automation. Most payroll and HR executives know little about these subjects, but increasingly, they are being asked to rise to new challenges.
These new challenges are being caused by the tectonic shift from capital businesses to people businesses. This is a shift of valuing time as much as money. About 50 years ago, when most people twisted bolts in a factory, workers were not considered volunteers, they were not empowered, and managing the money of the company (i.e. the capital) was much more important than maximizing the time and knowledge of the worker. Such businesses are called capital businesses because power and wealth flowed from the capital.
Today, capital businesses are on the wane and businesses are becoming people businesses.
Read the full text at Tracking Employee Time: It's Not Just For Payroll Anymore
by Chris Lynch, VP Product Engineering, eProject
The death of the desktop has been predicted for many years. Since 1995, everyone from Larry Ellison to Scott McNealy has declared the desktop computing model to be dead at one time or another. These very smart prognosticators were not wrong. They were just too early. Technologies simply weren’t ready to support the vision of Software as a Service (SaaS) – nor were business attitudes ready to accept it.
Due to a number of different converging factors, we are finally at a time where the vision of on-demand software is becoming a reality. One important market driver is the growing popularity of online consumer applications like Google Gmail and Microsoft Virtual Earth. These products are changing public perceptions about web-based applications by exposing users to the benefits of having software delivered as a service via the web.
With the growing popularity of web-based business products such as NetSuite and Salesforce.com, applications like ERP and CRM have become drivers in the corporate software arena. These on-demand applications allow businesses to quickly and easily extend the value of a program to the entire enterprise – a previously daunting task for organizations using the client/server-based approach.
Read the full text at The Desktop is Dead: the Fourth Wave of Business Applications
by Jean Brittingham
Over the past decade, the knowledge of how to successfully manage extensive capital improvement programs has grown considerably. Innovative management information systems linked to project and program controls, enhanced delivery capability through the use of integrated owner-consultant teams, and the strengthening of project management within engineering divisions have provided real improvements and significant cost savings for program delivery. It has become evident that a clearly defined project management approach, consistently applied on all projects within the capital plan, may be the most important first step in preparing an organization for world class delivery of a capital program.
This is largely because it has become increasingly clear that there is a critical and dynamic inter-relationship between program management and project management. This relationship, and the concurrent interdependencies, should be understood before choosing a program management approach for delivering your Capital Plan. The purpose of this paper is to discuss and clarify the relationship between program management and project management, and define the attributes of a strong project management approach.
Read the full text at Aligning Project Delivery for Success in a Program Management Environment
by Eduardo Miranda
As organizations turn to the project form as their preferred way to organize product development work, the need to coordinate the use of scarce resources and align initiatives becomes evident.
The Project Management Office (PMO) is the line organization that provides the infrastructure and competence necessary to manage projects. Its main responsibilities include: project portfolio management, capacity planning, scope management, inter-project coordination, overall project oversight, cost estimation, contingency planning, quality assurance, subcontract management, project managers’ development, process management and tool support.
The PMO objective, in contrast with those of a single project, is to complete all projects to best achieve the goals of the organization. Its responsibilities include: project portfolio management, strategic resource planning, inter-project coordination, overall project oversight, cost estimation, contingency planning, quality assurance, external provisioning, project managers’ development, process management and tool support.
Read the full text at Blueprint for a Project Management Office
Editorial Policy: The PMFORUM® has no connection to any national or international project management organization nor does it reflect the policy of any project management professional or commercial organization. The PMFORUM® maintains an objective and impartial view of project management affairs. In the interests of advancing professional project management the PMFORUM® will publish contending and objective views on issues that reflect collegial differences and perspectives