Churchill: The Agile PM (Part 22) |
|||||||||||||||||||||||||||||||
|
|
Home > Articles >
Most people are very familiar with Winston Churchill but may not be familiar with his “agile” approach to project management and his skills as a PM in the summer of 1940. Parts 16-21 looked at how Churchill’s organization prepared itself for the air battle to meet his short term objectives of staving off the invasion, and how it put together a solution.
This article switches gears and enters the final phase of the series that examines the historical sequence of events between June and October 1940. This analysis will reflect on the effectiveness of Churchill’s solution and how well it was utilized.
Some of the most difficult questions to answer with any project are: Did it meet the requirements and reach its goals? Did the output (solution) achieve what it was designed to do? Did it assist in a critical situation and help the organization react to it?
In early June 1940, most of the news for Churchill is bad.
Please login/register to read the entire article.
sponsored announcements and special offers
Independent Evaluation of Requirements Management Solutions - Compliments of MKS
Forrester Research has released its evaluation of the requirements management market and gives MKS the highest score for its current offering. Get your complimentary copy of: The Forrester Wave: Requirements Management, Q2 2008
White Paper: Tips For Writing Good Use Cases The Best and Most Informative Toolkit for the PMO by Daptiv (formerly eProject). The Daptiv PMO Toolkit features quality Project Management knowledge, tips and tools, recommended best practices, and case studies from our partners. For a successful PMO - Download the FREE PMO Toolkit!
Leading Analyst Research: Managing Your IT Portfolio in Challenging Times 50% of software defects can be traced back to requirements. 40% of a development organization's budget is spent on rework. 0% reason to ignore your Software Requirements and Management Process. Download the White Paper Why Projects Fail—and What Executives Can Do About It: The Truth About Requirements Definition and Management.
|
| |||||||||||||||||||||||||||||