A project scope statement is one of the key project requirements. It defines what the project is about, what’s included or excluded, the deliverables and much other critical information. It is the agreement which binds everyone - users, stakeholders, project sponsor, project manager and project team together. Often however, a project scope is just a few lines or paragraphs of general intent included within the IT project proposal. But making the project scope more comprehensive, will not only aid understanding, it will reduce the likelihood of scope creep during the project. The Project Scope Checklist below contains 30 points to consider: Does your scope definition include:  the need(s) or issue(s) to be resolved by the project?  the outcome(s), objective(s), or deliverable(s)?  the new system(s) to be implemented?  key functionality required within the new system(s)?  technical infrastructure of the new system(s)?  data requirements?  key business processes to be re-engineered?  old system(s) to be replaced?  technologies to be changed?  who it is for and who is affected – in terms of business functions, areas and locations?  the expected activities / work to be performed?  resources to be used / anticipated team size?  expected duration / time scales?  deliverable acceptance criteria? Project scope quantification  Has your scope been quantified wherever possible?  Does your scope statement clearly list what is included within the project and specify the project boundaries?  Does your scope statement list what is specifically excluded from the project?  Do you have an agreed process for dealing with areas / items which you are unsure whether to include or exclude?  Does your scope statement provide a detailed baseline – so as to identify whether a future proposed change is within or outside the project scope?  Is your scope definition sufficiently detailed? ie at least a few pages long?  Have your scope assumptions been documented?  Are the assumptions realistic? Project scope verification and understanding  Has your scope definition been carefully checked / verified?  Can you confirm - there is nothing else which should be included within your project scope?  Is there a common understanding of your project scope by all involved?  Has your project team worked with the users / stakeholders to define the project scope?  Is your project scope agreed by all ie users, stakeholders, project sponsor, project manager and project team?  Have all signed-off their agreement to the project scope statement?  Do users / stakeholders understand scope management and the potential problems caused by scope creep?  Do you have a formal process for managing possible future scope changes, which everyone understands and will use? For more IT project proposal information visit: Reasons for changing software / Project scope checklist / IT project proposal / Proposal format / Basic ROI calculation / ROI calculator and tips for maximising systems project ROI / Hidden costs of acquiring software / Project budget template and tips for improving IT software budgets / Proposal evaluation sheet