His blog is devoted to project management and he has original ideas about how to manage people. I think he believes that we lack some thinking and understanding for the others and this is why I feel his blog so close to my blogs PM Stories and Stop and Think!. And probably this is the reason why I like his blog so much.

Read the interview here. You may find some food for thought.

If you like the posts in this blog or you are interested in the discussed topics, please, subscribe to the RSS feed to guarantee yourself that you won’t miss an interesting post. You can do it in an RSS reader or by Email.

You may also find these posts interesting:

• Top-down Planning – Good or Bad?
• Walking on Water
• The Most Important Rules of Delegation
• Project Management and Hiking
• The Recommended Weekly Readings (2007-08-18). Project Management

Here they are, the 10 mistakes we should avoid in software development:

1. Never committing to project success. This is too obvious, I don’t see any wisdom in it.
2. Freezing the schedule and budget before a project is sufficiently understood. Unfortunately, this happens everywhere, every time. In my opinion, this is the main problem of the software project management: What to do when you are asked to give estimates about the cost and the time, and even to sign a contract before you know what this project is about?
3. Overscoping a solution. Yes, this is a mistake but I believe it happens more and more rarely.
4. Circumventing the application development organization altogether. I don’t think it’s a mistake if you know what you are doing. Sometimes it is the necessary if you’ve been assigned to a “Death March” project. The real question is: Can you still manage to succeed?
5. Underestimating the complexity of a problem. Usually, this is the reason for signing contracts with low budgets and shortened schedules. Unfortunately, this mistake is mostly made by the upper management mostly because they don’t consult with their team. I believe, that every company should invest some time upfront to investigate the customer’s problem ti gain a better understanding of its complexity.
6. Being stingy with subject-matter experts, in which their participation is not sufficient. I think this is also a result of the previous one.
7. Choosing the wrong project leadership. Or the wrong leaders. Or the wrong managers. Or the wrong customers (Can there be wrong customers?)
8. Distrusting managers who have had tasks delegated to them. I would say that not trusting anyone in your team or company is a mistake.
9. Jumping into development without enough research. Again, it happens as a result of underestimating the problem.
10. Suppressing bad news, in which dialogue is insufficient. Do you know a manager who likes to hear bad news?

Well, some would say that I am too skeptic or that I am a naysayer. No, am not. I think there are a lot of problems in our industry but this is my profession and I love it. I really want to discover the biggest mistakes we make, to analyze the reasons for them and to make a plan how to avoid them. Which is really hard. And when we look at our mistakes we just need to be more specific, especially when looking for the causes of those mistakes.

You may also find these posts interesting:

• Krishna Kumar Did An Interview With Me On Software Development
• Classic Mistakes 2008
• A "Classic" Story of Classic Mistakes by Steve McConnell
• Classic Mistakes – GigaLease Case Study, Part 2
• Classic Mistakes – GigaLease Case Study, Part 1