Churchill: The Agile PM (Part 14) |
|||||||||||||||||||||||||||||||
|
|
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. Part 13 looked at how Churchill put a communication plan in place to bolster morale in the government, media and public. This article discusses how Churchill personally communicated using both verbal and non-verbal communication to fight the mood of defeatism, build confidence and get buy-in into his plan.
In today’s world, PMs need to set up effective communication mechanisms, as pointed out in Maintaining Communications...And Project Control by Joe Wynne, where “effective project communications preserves your control in a project.” This requires a monitoring component in the communication plan to provide feedback on the plans effectiveness.
The core to Churchill’s project communications were around radio broadcasts used to speak directly with the public.
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.
|
| |||||||||||||||||||||||||||||