Monday, January 16, 2006
What is a Death March Project and why does it happens? I think every project manager should go and buy this book and read it before planning for the next project as to avoid the following : The immediate consequence of these constraints, in most organizations, is to ask the project team to work twice as hard and/or twice as many hours per week as would be expected in a "normal" project. Thus, if the normal work-week is 40 hours, then a death march project team is often found working 14-hour days, six days a week. Naturally, the tension and pressure escalate in such environments, so that the death march team operates as if it is on a steady diet of Jolt cola. I think most of us developers had already experienced this before and would not like to experience it again. This book will justify that developers are usually innocent in Death March and need not go thru all those suffering and tortures. If you are one of those unfortunate souls, try these Practical Suggestions for Breaking the Bad News.