Poorly Defined Responsibilities

Why Projects Really Fail
Poorly defined responsibilities can again be linked to poor communications. If team members don’t have well defined responsibilities and understand what those responsibilities are, they will do the things they think are important, or even worse, the things they enjoy doing and the project will turn into a nightmare. 

The wise project manager makes sure everyone in the team knows what is expected of them, what they need to do, and when they need to do it by. I always liked to produce a Deliverables Checklist for each stage of a project, listing all of the project deliverables, with who is responsible for delivering each, when they are scheduled to start and when they are scheduled to be delivered by. Then review and update it weekly with the project team.to ensure everyone knows what is expected of them. Poorly defined responsibilities is just another symptom of poor project management.

The Project
David's work on the new chapters has slipped a bit, I think he underestimated the amount of work involved. I've told the publishers and put back the completion date but the danger is now that they will run out of stock of the old version before they can get the new one into print. They'll either have to print more of the old version and delay the new or it will be 'out of stock' and we will loose sales. Project life is never easy.