Prompt

You are a DevOps engineer designing a comprehensive CI/CD pipeline and DevOps strategy for [PROJECT/ORGANIZATION].

Create a complete DevOps implementation plan:

## Current State Assessment

**Development Process Analysis:**
- Current workflow: [Manual deployments, testing procedures, release cycles]
- Tools and technologies: [Version control, build tools, deployment methods]
- Team structure: [Development, operations, QA team organization]
- Release frequency: [Current deployment cadence and challenges]
- Quality gates: [Existing testing, security, compliance checks]

**Infrastructure Assessment:**
- Current infrastructure: [On-premise, cloud, hybrid architecture]
- Deployment environments: [Development, staging, production setup]
- Monitoring and logging: [Current observability tools and practices]
- Security implementation: [Current security controls and processes]
- Scalability challenges: [Performance bottlenecks, resource constraints]

## DevOps Strategy & Objectives

**Strategic Goals:**
- Deployment frequency: [Target: from X per month to Y per week]
- Lead time: [Target: from X days to Y hours]
- Mean time to recovery (MTTR): [Target: from X hours to Y minutes]
- Change failure rate: [Target: reduce from X% to Y%]
- Customer satisfaction: [Improve deployment reliability and speed]

**DevOps Principles:**
- Collaboration and communication enhancement
- Automation over manual processes
- Continuous integration and deployment
- Infrastructure as code implementation
- Monitoring and feedback loops
- Fail fast and learn quickly approach

## CI/CD Pipeline Architecture

**Source Code Management:**
- Git workflow: [GitFlow, GitHub Flow, trunk-based development]
- Branch strategy: [Feature branches, release branches, hotfix process]
- Code review process: [Pull request workflow, review requirements]
- Repository structure: [Monorepo vs. multi-repo strategy]

**Continuous Integration (CI):**
- Build automation: [Automated build triggers, build environments]
- Testing automation: [Unit, integration, functional test execution]
- Code quality gates: [Static analysis, code coverage, security scanning]
- Artifact management: [Build artifacts, versioning, storage]

**Build Pipeline Stages:**
1. Source Stage - Code checkout and preparation
2. Build Stage - Code compilation and optimization
3. Test Stage - Automated testing execution
4. Quality Gate Stage - Static analysis and security scanning
5. Package Stage - Artifact creation and versioning

**Continuous Deployment (CD):**
- Deployment automation: [Automated deployment to environments]
- Environment promotion: [Dev → Staging → Production pipeline]
- Release strategies: [Blue-green, canary, rolling deployments]
- Rollback procedures: [Automated rollback triggers and processes]

## Infrastructure as Code (IaC)

**IaC Strategy:**
- Tool selection: [Terraform, CloudFormation, Pulumi, Ansible]
- Code organization: [Module structure, environment separation]
- Version control: [IaC repository management, versioning strategy]
- Testing approach: [Infrastructure testing, validation, compliance]

**Infrastructure Components:**
- Compute resources: [Virtual machines, containers, serverless functions]
- Networking: [VPC, subnets, security groups, load balancers]
- Storage: [Databases, file systems, backup solutions]
- Security: [IAM, encryption, certificate management]

## Monitoring & Observability

**Monitoring Strategy:**
- Application monitoring: [Performance, errors, user experience]
- Infrastructure monitoring: [Resource utilization, health, availability]
- Security monitoring: [Intrusion detection, compliance, vulnerabilities]
- Business monitoring: [KPIs, conversion rates, user behavior]

**Observability Stack:**
- Logging: [Centralized logging, log aggregation, analysis]
- Metrics: [Time-series data, dashboards, alerting]
- Tracing: [Distributed tracing, request flow analysis]
- Alerting: [Intelligent alerting, escalation, notification]

## Implementation Roadmap & Success Metrics

**Phase 1: Foundation (Months 1-3)**
- Current state assessment and gap analysis
- Tool selection and procurement
- Infrastructure setup and configuration
- Team training and skill development
- Basic CI pipeline implementation

**Phase 2: CI/CD Implementation (Months 4-6)**
- Comprehensive CI pipeline development
- Automated testing integration
- Security scanning implementation
- Deployment automation development
- Environment standardization

**Phase 3: Advanced Automation (Months 7-9)**
- Infrastructure as Code implementation
- Advanced deployment strategies
- Comprehensive monitoring setup
- Security automation enhancement
- Performance optimization

**Success Metrics:**
- Deployment frequency: [Deployments per day/week/month]
- Lead time for changes: [Time from commit to production]
- Mean time to recovery: [Recovery time from failures]
- Change failure rate: [Percentage of deployments causing failures]
- Developer productivity: [Features delivered per sprint]

Include specific tool configurations, implementation scripts, and measurable outcomes throughout the plan.