Professional Documents
Culture Documents
2.7 Assumption and Constraint Log
2.7 Assumption and Constraint Log
CHECKLIST
c 1. Are there ways to reduce the time it takes to get something approved?
c 3. Are funding and staffing resource estimates sufficiently detailed and documented for use in
planning and tracking the Operations Readiness and Assurance project?
c 7. Are processes for release management of new development from coding and unit testing, to
integration testing, to training, and production defined and followed?
c 9. If appropriate, is the deliverable content consistent with current Operations Readiness and
Assurance project documents and in compliance with the Document Management Plan?
c 11. Is the amount of effort justified by the anticipated value of forming a new process?
c 12. Are there processes in place to ensure internal consistency between the source code
components?
c 14. Does a specific action and/or state that is known to violate security policy occur?
c 15. If it is out of compliance, should the process be amended or should the Plan be amended?
c 16. Do you know what your customers expectations are regarding this process?
1
ASSUMPTION AND CONSTRAINT LOG
c 19. When can log be discarded?
c 22. Have the scope, objectives, costs, benefits and impacts been communicated to all involved
and/or impacted stakeholders and work groups?
c 23. Does the document/deliverable meet general requirements (for example, statement of work)
for all deliverables?
c 24. Is the steering committee active in Operations Readiness and Assurance project oversight?
c NOTES:
2
ASSUMPTION AND CONSTRAINT LOG
Responsible
ID Category Assumption/Constraint Party Due Date Actions Status Comments