1. NORCOM Questions
1.1. How are we defining tasks vs projects? I would expect different documentation requirements for each.
2. Project framework
2.1. Initiation & Planning
2.1.1. Initiating - All the activities leading up to formal authorization to begin a project.
2.1.1.1. Identifying the project or business need
2.1.1.2. Documenting the business justification
2.1.1.3. Business case validation
2.1.1.4. Pre-project plan
2.1.1.4.1. More specifics
2.1.1.4.2. Only req'd for big ticket projects
2.1.1.5. Charter
2.1.1.5.1. ID from Prioritization SS
2.1.1.5.2. Goals and Objectives
2.1.1.5.3. Business Needs / Problem statement
2.1.1.5.4. Description
2.1.1.5.5. Key Deliverables
2.1.1.5.6. Key stakeholders
2.1.1.5.7. High level requirements, risks, costs and dependencies
2.1.1.5.8. Scope
2.1.1.5.9. Equipment
2.1.1.5.10. Resource list
2.1.2. Planning - Where the goals, objectives and deliverables are broken down into manageable units of work.
2.1.2.1. Project plan
2.1.2.1.1. Project scope statement
2.1.2.1.2. Work breakdown structure
2.1.2.1.3. Communications plan creation
2.1.2.1.4. Required resources determined
2.1.2.1.5. Human resources plan
2.1.2.1.6. Procurement plan
2.1.2.1.7. Stakeholder list
2.1.2.1.8. Risk plan
2.1.2.1.9. Cost plan
2.1.2.1.10. Quality plan
2.1.2.1.11. Group setup
2.1.2.1.12. Time estimates and schedule created
2.1.2.1.13. Change control procedures
2.1.2.1.14. Requirements
2.1.2.1.15. Contact list
2.1.2.1.16. Test planning
2.1.2.1.17. Expectations
2.1.2.1.18. Post go-live support defined
2.1.2.1.19. Assumptions
2.1.2.1.20. Closure / Transition plan
2.1.2.1.21. Establishing performance measures
2.1.2.2. Project kick-off
2.1.2.2.1. Vendor Support
2.2. Execution
2.2.1. Project oversight
2.2.2. Change management
2.2.2.1. Implementation of change control board
2.2.2.2. Change request documentation
2.2.2.3. Updating stakeholders and plans
2.2.3. Risk monitoring
2.2.4. Monitor performance measures
2.2.5. Create Deployment plan
2.2.6. Go-live planning
2.2.6.1. Rollback procedures
2.2.6.2. Task list creation
2.2.6.3. Go / No Go criteria
2.2.7. QA / Testing execution
2.2.8. Create / Coordinate Training
2.2.8.1. Tech training
2.2.8.2. Agency training
2.2.9. Information documentation
2.2.9.1. Maintenance planning
2.2.9.1.1. Equipment replacement planning
2.2.9.1.2. Specific task documentation
2.2.9.1.3. Service list and RAM usage
2.2.9.1.4. Troubleshooting & how to guides
2.2.9.1.5. Define NORCOM/Agency Support Responsibilities
2.2.9.2. Security planning
2.2.9.2.1. Log file locations
2.2.9.2.2. CJIS / CALEA special handling
2.2.9.3. Flowcharts
2.2.9.3.1. Business task workflows
2.2.9.3.2. Network diagrams
2.2.9.3.3. Dataflow diagrams
2.2.10. Issue handling
2.2.11. Communication updates
2.2.11.1. Status updates
2.2.11.2. Fault summary updates
2.3. Closure
2.3.1. Documentation sign off checklist
2.3.2. Techteam training
2.3.3. Final acceptance sign off
2.3.4. Post project post mortem
2.3.5. Address outstanding tickets going to day-to-day maintenance
2.3.5.1. Handoff to service desk
2.3.6. Archival of project documents
3. PMO
3.1. Stakeholder approval, prioritization and communication
3.1.1. Selecting which projects to work on
3.2. Manage Project Prioritization SS
3.3. Receive ongoing status reporting from Project Mgr
3.3.1. Provide ongoing status reporting of all projects to Upper Mgmt & NORCOM Boards