112 lines
2.9 KiB
Markdown
112 lines
2.9 KiB
Markdown
# Operations and Project Management Intake Template
|
|
|
|
## Overview
|
|
|
|
This template guides the collection of operational procedures and project management approaches.
|
|
|
|
## Interview Structure
|
|
|
|
### 1. Operational Procedures
|
|
- Daily/weekly/monthly routines and rituals
|
|
- System administration and maintenance tasks
|
|
- Monitoring and alerting procedures
|
|
- Backup and recovery processes
|
|
- Security and compliance practices
|
|
- Documentation and knowledge management
|
|
|
|
### 2. Project Management Approaches
|
|
- Project initiation and planning methods
|
|
- Task tracking and progress monitoring
|
|
- Resource allocation and scheduling
|
|
- Risk management and contingency planning
|
|
- Communication and stakeholder management
|
|
- Quality assurance and delivery processes
|
|
|
|
### 3. Infrastructure and Tools
|
|
- Hosting platforms and deployment targets
|
|
- Development and testing environments
|
|
- Monitoring and observability tools
|
|
- Security and compliance tooling
|
|
- Collaboration and communication platforms
|
|
- Automation and orchestration systems
|
|
|
|
### 4. Knowledge Management
|
|
- Information organization and categorization
|
|
- Documentation standards and practices
|
|
- Knowledge sharing and dissemination
|
|
- Learning and improvement processes
|
|
- Archive and retention policies
|
|
- Search and discovery optimization
|
|
|
|
### 5. Continuous Improvement
|
|
- Retrospective and review processes
|
|
- Metric tracking and analysis
|
|
- Process refinement and optimization
|
|
- Technology evaluation and adoption
|
|
- Skill development and training
|
|
- Innovation and experimentation approaches
|
|
|
|
## Response Format
|
|
|
|
Please provide responses in the following structured format:
|
|
|
|
```yaml
|
|
operational_procedures:
|
|
routines:
|
|
daily: []
|
|
weekly: []
|
|
monthly: []
|
|
system_administration: []
|
|
monitoring_procedures: []
|
|
backup_recovery: []
|
|
security_practices: []
|
|
documentation_management: []
|
|
|
|
project_management:
|
|
initiation_planning: []
|
|
task_tracking: []
|
|
resource_allocation: []
|
|
risk_management: []
|
|
stakeholder_communication: []
|
|
quality_assurance: []
|
|
|
|
infrastructure_tools:
|
|
hosting_platforms: []
|
|
development_environments: []
|
|
monitoring_tools: []
|
|
security_tooling: []
|
|
collaboration_platforms: []
|
|
automation_systems: []
|
|
|
|
knowledge_management:
|
|
information_organization: []
|
|
documentation_practices: []
|
|
knowledge_sharing: []
|
|
learning_processes: []
|
|
archive_policies: []
|
|
search_optimization: []
|
|
|
|
continuous_improvement:
|
|
retrospective_processes: []
|
|
metric_tracking: []
|
|
process_refinement: []
|
|
technology_evaluation: []
|
|
skill_development: []
|
|
innovation_approaches: []
|
|
```
|
|
|
|
## Validation Criteria
|
|
|
|
- Alignment with current operational reality
|
|
- Completeness of key operational areas
|
|
- Practicality of implementation
|
|
- Consistency with documented procedures
|
|
- Relevance to current projects and initiatives
|
|
|
|
## Frequency
|
|
|
|
This intake should be updated:
|
|
- Quarterly for operational reviews
|
|
- As-needed for procedure changes
|
|
- Semi-annually for infrastructure updates
|
|
- Annually for comprehensive process reviews |