Typical Project Assumptions
Resource Assumptions
- Project staff resources
will be available when and as they are needed.
- Required
hardware resources will be available when and as they are needed.
- Required
customer resources will be available when and as they are needed.
- A
significant percentage of the project staff will be experienced with the
technical environment.
- A
significant percentage of the project staff will be experienced with the
operating environment.
- Access
to industry experts and specialized skills will occur as needed.
- A
"full-time" resource implies at least 35 hours productive work
per week.
Delivery Assumptions
- Deliverables
will be subject to no more than a specific number of 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.
- Systems
components will be capable of being integrated with minimum rework.
Budgetary Assumptions
- The statistics used in
preparing the estimates are accurate within a given percent.
- No outside consulting
will be required or Outside consulting will be limited to a specified
number of days at a specified rate per day.
Functionality Assumptions
- The scope of the project is limited to
that described in the project charter.
- Formal
charter and scope change procedures will be followed.