This is a series of notes on Terry Schmidt’s book Strategic Project Management Made Simple, which adds the Logical Framework Approach to traditional project management in order to facilitate strategic planning. The first chapter of his book is Thinking Outside The Bar Chart, and introduces the reasons why strategic planning is important.
As mentioned in the last post, NASA Rule #15 states
A review of most failed project problems indicates that the disasters were well-planned to happen from the start. The seeds of problems are laid down early. Initial planning is the most vital part of a project.
What are some of the specific planning mistakes that can create disasters on a project? The following chart describes six dangerous planning mistakes, and gives some concepts for solutions to these mistakes.
Planning Mistake | Explanation | Solution Concepts |
1. Tolerating VagueObjectives | In rush to implement, not enough serious, upfront thinking goes into clarifying Objectives, Measures, and their interconnections. |
|
2. Ignoring Environmental Context | People sometimes ignore how risk factors outside their project boundaries might affect them. |
|
3. Poor Planning Tools and Process | Tools are best used when it comes time to start breaking down tasks, not during the “fuzzy front end” when you are still firming up Objectives. |
|
4. Neglecting Stakeholder Interests | Without the buy-in from stakeholders involved in or affected by the project, projects suffer. |
|
5. One-Shot Planning | Project plans must be updated to reflect new learning and progress. |
|
6. Mismanaging People Dynamics | Some project managers run roughshod over their team. |
|
It is Terry Schmidt’s contention that the Logical Framework Approach will provide solutions which will help you avoid all of these dangerous planning mistakes. How? By helping you create a strong project backbone which has the strength to carry the planning load, but at the same time has enough flexibility to change when new information comes to light.
The principles of creating that strong project background are covered in the next chapter, Chapter 2: “Building Strong Project Backbones,” which will be covered in the next few posts.
Filed under: Uncategorized |
Leave a Reply