Don’t increase scope without adjusting your schedule and budget! Seems simple enough but probably the single https://www.sunmolds.com most common mistake. People always try to add small things that involve minimal effort. These add up and the impact is often not addressed, which ultimately leads to a failure in schedule and budget. The change board is your main defense against this, see change board below.
Requirements Requirements in any project are tricky and many excellent books are dedicated to this subject alone. It is true that of the projects that fail most issues can be traced back to requirements. Strange how this continues to be the case when requirements are the easiest and cheapest way to find and fix problems.
A problem will never be cheaper than it is right now. When you review your requirements, you need to really review them, dont just scan them. Think about and try to visualize what they are saying. You will often find problems are apparent at the surface. Take the time to do thoughtful reviews and continue to refine the requirements until everyone feels they are correct. Compare the expense of re-writing a sentence in a word processor to re-writing hundreds of lines of code, re-testing and re-deploying and youll see these are the last chances you have at a cheap fix.
Change BoardsWhen done properly Change Boards can almost single-handedly manage even the most challenging projects.
What it is. Very simply the change board is a meeting where each of the key departments and sometimes clients are represented and have a chance to discuss the project from every angle. The idea is to make sure everyone is aware of the status and is able to speak to the impact any change in requirements or schedule will have on their respective department.
Who is there? Generally the list consists of the following: Marketing, Sales, QA, Operations, Development, IT, Project management, Clients. Essentially everyone who has a stake in or is affected by the project. Depending on the nature of the project Marketing or Sales will often represent the client. The most important rule here is, if someone is identified as a stakeholder in the project, do not have a meeting without them. If they cant be there, reschedule.
Follow these steps in any process you adopt or any project you manage and you should find it really will improve your chances at success.
Requirements Requirements in any project are tricky and many excellent books are dedicated to this subject alone. It is true that of the projects that fail most issues can be traced back to requirements. Strange how this continues to be the case when requirements are the easiest and cheapest way to find and fix problems.
A problem will never be cheaper than it is right now. When you review your requirements, you need to really review them, dont just scan them. Think about and try to visualize what they are saying. You will often find problems are apparent at the surface. Take the time to do thoughtful reviews and continue to refine the requirements until everyone feels they are correct. Compare the expense of re-writing a sentence in a word processor to re-writing hundreds of lines of code, re-testing and re-deploying and youll see these are the last chances you have at a cheap fix.
Change BoardsWhen done properly Change Boards can almost single-handedly manage even the most challenging projects.
What it is. Very simply the change board is a meeting where each of the key departments and sometimes clients are represented and have a chance to discuss the project from every angle. The idea is to make sure everyone is aware of the status and is able to speak to the impact any change in requirements or schedule will have on their respective department.
Who is there? Generally the list consists of the following: Marketing, Sales, QA, Operations, Development, IT, Project management, Clients. Essentially everyone who has a stake in or is affected by the project. Depending on the nature of the project Marketing or Sales will often represent the client. The most important rule here is, if someone is identified as a stakeholder in the project, do not have a meeting without them. If they cant be there, reschedule.
Follow these steps in any process you adopt or any project you manage and you should find it really will improve your chances at success.
コメント