Berkun reading group discussion
MakingThingsHappen
>
Chapter 11: Discussion and Questions
date
newest »

message 1:
by
Scott
(new)
Apr 13, 2015 09:21AM

reply
|
flag

This was my favorite chapter so far in the book. The quote above sums up the challenge for managing projects. I think this chapter will still be viable another ten years from now. My key takeaway was that we need to better educate ourselves with simulations and case studies on what can go wrong on a project. I loved the analogy used about pilots and their approach when something goes wrong.
Most helpful sections for me in this chapter were
1. 8-point rough guide for dealing with adversity. It's a simple checklist that can be easily discussed with our teams.
2. Continuous learning needs to include simulations because it's difficult for people to relate to a problem they haven't experienced.
3. Quality is not free. You need to sacrifice something for quality: slow rate of progress, cut features or increase time, and define good quality with measurable goals for your team.
4. Satir Model - this makes more sense to me now than when I read the book ten years ago.
5. Coping mechanism when under pressure - Find a solution for yourself and team for dealing with stressful situations.
My only critique is that I wish we had an exhaustive list of difficult situations and problems on a project that can be used for training. You mentioned that Chapter 3 of Rapid Development by Steve McConnell as the best resource you read on the topic. Is that still your best recommendation?
It's one of my favorite chapters too. There was a time while writing the book I thought it should be the first chapter of the book itself. Some projects and organizations are always being managed as if it's a crisis (even if the people involved don't think of it that way).
Exhaustive lists are tough to write since projects are so different, especially if you're thinking of not just software projects, but engineering and construction projects too.
I haven't looked at Rapid Development in a long time, so that's a qualified yes :) Another good book on situations, although it doesn't often a list, is Roundtable on Project Management. http://www.amazon.com/Roundtable-Proj... - each short chapter is a tough situation, and you get to hear advice from a range of different experts. It's a fantastic book, but it's not going to directly provide a situational checklist.
Exhaustive lists are tough to write since projects are so different, especially if you're thinking of not just software projects, but engineering and construction projects too.
I haven't looked at Rapid Development in a long time, so that's a qualified yes :) Another good book on situations, although it doesn't often a list, is Roundtable on Project Management. http://www.amazon.com/Roundtable-Proj... - each short chapter is a tough situation, and you get to hear advice from a range of different experts. It's a fantastic book, but it's not going to directly provide a situational checklist.