Project Scope Checklist


	Quick Links Research IT proposal summary Why change your present system? Project scope checklist IT project proposal Proposal format Basic ROI calculation Return on investment calculator Proposal evaluation sheet

Project Scope Checklist

For an IT software system project

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. However, often 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:

Ref	Project Scope Checklist	Yes	No	Don’t know

	Does your scope definition include:
1	- the need(s) or issue(s) to be resolved by the project?
2	- the outcome(s), objective(s), or deliverable(s)?
3	- the new system(s) to be implemented?
4	- key functionality required within the new system(s)?
5	- technical infrastructure of the new system(s)?
6	- data requirements?
7	- key business processes to be reengineered?
8	- old system(s) to be replaced?
9	- technologies to be changed?
10	- who it is for and who is affected – in terms of business functions, areas and locations?
11	- the expected activities / work to be performed?
12	- resources to be used / anticipated team size?
13	- expected duration / time scales?
14	- deliverable acceptance criteria?

15	Has your scope been quantified wherever possible?
16	Does your scope statement clearly list what is included within the project and specify the project boundaries?
17	Does your scope statement list what is specifically excluded from the project?
18	Do you have an agreed process for dealing with areas / items which you are unsure whether they are included or excluded?
19	Have your scope assumptions been documented?
20	Are the assumptions realistic?
21	Does your scope statement provide a sufficiently detailed baseline – so as to identify whether a future proposed change is within or outside the project scope?
22	Is your scope definition sufficiently detailed? ie is it at least a few pages long?
23	Has your scope definition been carefully checked / verified?
24	Can you confirm - there is nothing else which should be included within your project scope?
25	Is there a common understanding of your project scope by all involved?
26	Has your project team worked with the users / stakeholders to define the project scope?
27	Is your project scope agreed by all ie users, stakeholders, project sponsor, project manager and project team?
28	Have all signed-off their agreement to the project scope statement?
29	Do users / stakeholders understand ‘scope management’ and the potential problems caused by scope creep?
30	Do you have a formal process for managing scope changes, which everyone understands and will use?


	Use the project scope checklist sheet above, or download a free copy (in MS Excel) below or from the download page.




	For other IT project proposal information sheets visit: Why change your present system? / IT project proposal / Proposal format / Basic roi calculation / Return on investment calculator / Proposal evaluation sheet

[Home] [Products] [Services] [Research] [IT Proposal] [Selection Process] [RFP Guidance] [System Trends] [Software Criteria] [Exhibitions] [Directory Links] [Free Downloads] [Site Map] [About Us] [Contact Us]