Friday, 15 May 2009
Too many projects start off with a list of roles which have either been copied from an earlier project (and not updated) or are too loose in description to mean anything. They’ll be hidden will inside the start-up documentation and are unlikely to be given anything more than a cursory glance at sign-off, and certainly won’t be referred to again in the course of the project. So why bother? Because clear definition of roles within a project is as important as defining the requirements – especially in a small company where everyone has other roles to perform outside the project. As the Project Manager you need to know who will do what, and what they will be responsible for. Do you need everyone to sign off each piece of work or will you have the responsibility for this? Clarity around roles will save a lot of time and confusion later on – sit down with the project team including the sponsor, suppliers and end users to talk through what each group will (and won’t!) do so that everyone knows what everyone else will be doing – this may cause issues and arguments but persevere with it – better to have these out at the start of the process than have to deal with them when you’re in full swing!