Churchill: The Agile PM (Part 13)

Home  >  Articles  > 
Churchill: The Agile PM (Part 13)

Mark Kozak-Holland

January 24, 2007






<A TARGET="_blank" HREF="http://www.gantthead.com/clickCount.cfm?ID=243479"><IMG SRC="/flash/build_336x2804.gif" BORDER=0></A>
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. Part 12 looked at his background, why he was so uniquely qualified in May of 1940, the skills that he brought to bear to the project, and his previous project experience along with the battle scars. This article discusses how Churchill put in place a communication plan to bolster morale in the government, media and public.
 
In today’s world, communications management is fundamental to project management (one of nine PMBOK knowledge areas) in managing expectations. Since change is constant in an agile project, constant communication is the only means of maintaining the connections between all the participants. Most projects have internal and external audiences, and the messages differ in content and tone, as well as timing. For example:
  • Awareness communications at the end of each project stage
  • Special-purpose communications, usually a clear call-to-action
  • Data Freeze communications to announce a period of no updates
  • Launch communications to help users with new functionality
  • Stabilization communications of resolution work for known issues
  • Bulletin communications of changes to project dates, scope, or emerging issues, risk or requests
In the early summer of 1940, Churchill had to deal with a series of disasters culminating with Dunkirk (Part 7 and Part 8), the greatest defeat of the British army since the Napoleonic era.



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
Use cases, critical for capturing business requirements, are more art than science. These tips can help you align teams around clear goals for successful software or systems development projects.

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
Hear from one of the leading researchers on IT Portfolio Management and IT Governance, Craig Symons, Vice President and Principal Analyst at Forrester Research, as he discusses critical success factors for IT portfolio management. This webcast is Project Management Institute (PMI) Accredited.
View the Webcast

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.



"My way of joking is to tell the truth. It is the funniest joke in the world."
- George Bernard Shaw