In Waltzing with Bears: Managing Risk on Software Projects, DeMarco and Lister outline the dangers of penalizing negative thinking:
This is a companion discussion topic for the original blog entry at: http://www.codinghorror.com/blog/2005/09/the-positive-impact-of-negative-thinking.html
At my first company, we would cooperate with the project managers to maintain a top 10 risk list. Unfortunately, companies I’ve worked with afterwards haven’t been interested, so I maintain an informal one internally.
I agree. Let’s get the risks on the table right away and update that list during the project. Let’s be about building great software by doing whatever it takes.
On my projects we list the top risks for a project on the status report we send to the client. We update the report every week and go over it with them so everyone is on the same page: the client, the project team, etc. When we list the risks, I also like describing how we’re addressing the risk .
good ideas congratulations men