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 Mark Kozak-Holland
Background: The Years Before September 1939
Continuing with our series on Churchill the Project Manager (PM), this article discusses the decade preceding his project and why through his actions he became the most credible candidate to lead it. Part 1 introduced the overall series and how Churchill acquired a project from hell, a project that no one wanted. Part 2 looked at his background, and the skills that he brought to bear to the project that made him so uniquely qualified in May 1940.
Most people are very familiar with the rise of the Nazis who came into power in 1933 by taking advantage of a country in chaos and ruin, ravaged by a financial crisis, depression, and the Treaty of Versailles. In the UK and the West there was little response as public support for another war was very limited. The western economies were still recovering from the depression. In fact, many senior British politicians thought that the Treaty had been too harsh on Germany, and leeway be given. Over in the US many believed that involvement in the First World War had been a mistake and attempts were made to stay isolated.
Churchill did not share this view of the Nazis and recognized early what was happening Although he was not in a position of power he did what he could to call the Nazis ambitions out, and grill the politicians in power who tried to ignore him and take no actions. By 1934 he was particularly concerned about the growth of the Luftwaffe, German air force, which could strike directly at the UK.
Read the full text at Churchill the Project Manager (Part 3)
by David C. Fleming
As business involvement between the United States and Mexico continues to increase, so does the need for project managers who understand and can successfully navigate the cultural differences between the two nations. While the U.S. and Mexico are geographically connected and experience heavy cultural crossover, the culture of Mexico still remains very different. If you are given an opportunity to manage a project in Mexico, you will face unique cultural challenges that your experiences in the U.S. will not have prepared you for. A project manager, who does not understand and embrace the cultural differences between the two nations and apply this understanding to the execution of the project management processes, will find it almost impossible to achieve project success.
While nothing beats first hand experience, if you are considering taking on your first project in Mexico, you must have at minimum a basic grasp of the cultural environment that you will be plunging yourself into when you step off the plane. If you are willing to take the challenge, there are several key cultural differences that you must prepare for when you are planning, conducting, and overseeing project tasks. A basic but solid comprehension of the main cultural challenges you will meet and some ideas on how to address them can provide invaluable knowledge that every project manager must have in order to have any chance of achieving project success south of the border.
Since the North American Free Trade Agreement (NAFTA) went into effect on January 1, 1994, trade between Mexico, the United States, and Canada has more than tripled. Mexico continues to be an emerging free market economy, a result of leadership that increasingly supports business friendly legislation. This recent legislation has opened the door for increased competition in Mexico and has also provided for the privatization of many markets that have historically been under the tight control of the Mexican government. This decrease in restrictions has resulted in an enlargement of international business activity, especially between Mexico and the U.S. The growth of cross-border business activity has generated a boost in need for U.S based project managers who can go abroad and successfully manage projects. This provides an open opportunity for you who are up to the challenge of navigating the unique culture, economy, and business environment that is Mexico.
Read the full text at PM South of the Border
by Rob Zanfardino
The roar of the crowd, the smell of blood in the air, the flashing lights, the spin of the big wheel and let us not forget about those “beauties” who walk around on the stage. No, I am not talking about professional wrestling or one of those reality TV shows, if you have not figured out what I am talking about it is the TV game show, The Price is Right hosted by Bob Barker. This game show has captured viewers’ attention longer than any other game show in history.
As I was watching the show one day it dawned on me that this show was very relevant to the world of project management. This epiphany helped me in several ways: One, it gave me an excuse to keep watching it. Two, it provided me a great title for this article to draw you in to read it. It is one of those shameful but necessary evils that writers employ to get your attention! More importantly, the show can be used as a study in how people perceive risks, the calculations used in taking the risk, and their reaction when the risk ends badly. It is very interesting to see folks with different backgrounds from different locations within the United States, view and act to the risk in order to achieve a financial gain.
For those of you who are familiar with the game show, can you see what I am seeing and how this show can apply to project management? It really is amazing how different personalities play the game:
This game show really is a study in risks. How do you determine the percentage of probability in the likelihood the risk will occur in an event not in your control?
Read the full text at The Price is Right
by Quentin W. Fleming and Joel M. Koppelman, Primavera Systems, Inc.
{Originally published in Crosstalk, the Journal of Defense Software Engineering in June 2006, Reprinted by permission.}
In 1965, the U.S. Air Force acquisition managers defined 35 criteria which they felt would capture the essence of earned value management (EVM), and also satisfy their need to oversee the work that was being performed for them by private industry. Two years later, the Departmentof Defense (DoD) adopted these same criteria as their Cost/Schedule Control Systems Criteria (C/SCSC). These 35 standards were then consistently applied to all cost type and incentive type contracts for the next three decades.
Then in 1996, after a rewrite of the 35 C/SCSC criteria by private industry, the DoD accepted the rewriting/rewording of these criteria under a new title called the Earned Value Management System (EVMS). The total number of criteria was reduced to 32. Gone were the incomprehensible terms of Budgeted Cost for Work Schedule, Budgeted Cost for Work Performed, and Actual Cost of Work Performed, etc. In their place were titles like planned value, earned value, and actual costs. People (even busy executives) could understand the concept without the need for special training or a translator being present.
Private industry in the form of the National Defense Industrial Association (NDIA) took the defined criteria concept
one step further. In June 1998, the NDIA obtained acceptance of the EVMS in the form of the American National Standards Institute, termed the ANSI/EIA-748 Standard. The good news in this story is that there has been a consistent application of the earned value criteria concept applied for more than 40 years. The earned value criteria have met the test of time.
The bad news is that these criteria were originally written for applications to complex major system acquisitions. Further bad news is that the original 35 criteria – and the reworded 32 criteria – can be overly prescriptive to most of the projects in the world, in our opinion. They are great for major systems, but likely too much for most projects. Somehow a way must be found to capture the important fundamentals of earned value without overly prescribing requirements, which often discourages individuals wanting to adopt a technique to better manage their projects. And, as the ANSI/EIA-748 Standard becomes more commonplace, likely taking the form of a Federal Acquisition Requirements clause issued in routine procurements, a way must be found to scale back the full requirements to meet the needs of most projects – even small software projects.
Read the full text at Start With “Simple” Earned Value On All Your Projects
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