CHECKLIST OF ASSUMPTIONS
PROJECT
Version #: 1.0
Issue Date:
Assumptions: Checklist
Customer:

Project:
Resource Assumptions
Project staff resources will be available when and as they are needed.
Required computer resources will be available when and as they are needed.
Required client resources will be available when and as they are needed.
At least X% of the project staff will be experienced with the development environment.
At least X% of the project staff will be experienced with the operating environment.
The client will provide staff capable of adequately describing in detail the functional
requirements of the system.
The client will provide staff capable of adequately describing in detail the operational
requirements of the system.
Access to industry experts and specialized skills will occur as needed.
A “full-time” resource implies at least 40 hours productive work per week.
Delivery Assumptions
Deliverables submitted for approval will be reviewed and returned within X working
days.
Deliverables will be subject to no more than X review cycles.
Equipment order lead times are known and can be expected to be met.
Environmental Assumptions
No industrial action will be taken that will affect the project.
Issues will be resolved in a timely manner.
The project organization described in the Project Plan will be put in place.
The methodology [name it] will be used in the project.
Client internal processes (such as purchasing) will be completed in a timely manner.
Systems components will be capable of being integrated with minimum rework.
Page 1
Printed on: February 12, 2016
CHECKLIST OF ASSUMPTIONS
PROJECT
Version #: 1.0
Issue Date:
Budgetary Assumptions
The statistics used in preparing the estimates are accurate within X%.
No travel and living expenses will be required
or
Travel and living expenses are limited to those described.
No outside consulting will be required
or
Outside consulting will be limited to X days at $XX.XX per day.
Functionality Assumptions
The scope of the project is limited to that described in the Project Charter.
Formal scope change procedures will be in place.
Page 2
Printed on: February 12, 2016