Professional Documents
Culture Documents
CHECKLIST
c 1. Is your organization structure appropriate for the Operations Readiness and Assurance projects
size and complexity?
c 2. Will tasks be marked complete only after QA has been successfully completed?
c 5. Will the risk status be reported to management on a regular and frequent basis?
c 6. Has the format for tracking and monitoring schedules and costs been defined?
c 7. Did your Operations Readiness and Assurance project ask for this?
c 8. How often do you estimate that the scope might change, and why?
c 12. Are there issues that could affect the existing requirements for the result, service, or product if
the scope changes?
c 13. Will statistics related to QA be collected, trends analyzed, and problems raised as issues?
c 18. Is the plan for your organization of the Operations Readiness and Assurance project resources
adequate?
c 19. Has a method and process for requirement tracking been developed?
c 20. Operations Readiness and Assurance project lead, team lead, solution architect?
1
PROJECT SCOPE STATEMENT
c 21. What is the most common tool for helping define the detail?
c 22. Identify how your team and you will create the Operations Readiness and Assurance project
scope statement and the work breakdown structure (WBS). Document how you will create the
Operations Readiness and Assurance project scope statement and WBS, and make sure you
answer the following questions: In defining Operations Readiness and Assurance project scope
and the WBS, will you and your Operations Readiness and Assurance project team be using
methods defined by your organization, methods defined by the Operations Readiness and
Assurance project management office (PMO), or other methods?
c 23. Are the meetings set up to have assigned note takers that will add action/issues to the issue
list?
c NOTES:
2
PROJECT SCOPE STATEMENT
Project Deliverables
Project Exclusions
Project Constraints
Project Assumptions