Most problems in a project occur when the project is actually running. This may seem obvious, but consider the amount of time spent on analyzing the situation and taking measurements to counter potential problems; the majority of this is done at the start of the project. When the project is running on full speed, when everybody is very occupied with their day-to-day work the need for analyzing project circumstances increases, but is hardly done.
To be a good project manager you have to "see" potential problems. Literature provides us with large lists of potential problems in projects. You could look on all those lists to see if your problem is on it somewhere. But wouldn't it be great to be able to look at problems in your project on a more fundamental level? That would be the best thing that can happen to you, and the techniques discussed in this free report, will help you just with that!
"Project Profiling With Systems Thinking"
Learn Systems Thinking with
1. Reinforcing Feedback Loops
2. Balancing Feedback Loops
3. Delays
Learn how to apply them on software projects using Archetypes like:
- Shifting The Burden
- Fixes That Backfire
- Limits To Growth
- Tragedy Of The Commons
Download the PDF file here.
Leave a Reply