GATE CHECKLISTS: Практические чеклисты для каждой границы

☐ Business Case утверждён Project Sponsor
☐ Project Charter подписан (scope, objectives, constraints)
☐ Бюджет выделен (preliminary allocation)
☐ Стратегическое соответствие подтверждено (alignment with company strategy)
☐ Feasibility study пройдено (технический, финансовый, организационный)
   ☐ Техническая feasibility: решение реализуемо с текущими технологиями
   ☐ Финансовая feasibility: ROI > {X}% (определяется компанией)
   ☐ Организационная feasibility: команда/ресурсы доступны
☐ Legal/Compliance review пройден (нет блокеров)
☐ Project Sponsor назначен (и согласен)
☐ Проект не конфликтует с другими проектами (portfolio check)

[ ] ROI projection:
    1 = <10%, 2 = 10-25%, 3 = 25-50%, 4 = 50-100%, 5 = >100%
    Score: _____

[ ] Strategic importance:
    1 = Low, 2 = Below average, 3 = Average, 4 = High, 5 = Critical
    Score: _____

[ ] Risk level (обратная шкала):
    1 = Very high risk, 2 = High, 3 = Medium, 4 = Low, 5 = Very low
    Score: _____

[ ] Resource availability:
    1 = Resources overloaded, 3 = Tight, 5 = Ample resources
    Score: _____

[ ] Market opportunity:
    1 = Declining market, 3 = Stable, 5 = Growing fast
    Score: _____

TOTAL SCORE: _____ / 25

☐ Project Charter (signed)
☐ Business Case Document
☐ Feasibility Study Report
☐ Preliminary Budget & Timeline
☐ Stakeholder Register (key stakeholders identified)
☐ Initial Risk Assessment
☐ Strategic Alignment Statement

1. [10 min] Презентация бизнес-кейса (PM)
2. [10 min] Feasibility study results (Technical Lead)
3. [15 min] Обсуждение рисков
4. [10 min] Оценка критериев (Must-Meet + Should-Meet)
5. [10 min] Решение: Go / Kill / Hold / Recycle
6. [5 min] Next steps (если GO)

☐ Requirements утверждены ВСЕМИ ключевыми stakeholders
   ☐ Бизнес-требования (BRD) подписаны business owner
   ☐ Функциональные требования (FRD) / User Stories согласованы
   ☐ Нефункциональные требования (NFR) определены
      (performance, security, scalability, availability)
   ☐ Acceptance criteria ясны для каждого requirement
☐ Scope baseline определён (WBS complete)
   ☐ WBS разбит до уровня work packages (100-500 часов)
   ☐ Scope statement задокументирован (что IN, что OUT)
☐ Budget утверждён Finance Department
   ☐ Детализация по фазам
   ☐ Contingency reserve выделен (обычно 10-20%)
☐ Schedule утверждён Sponsor
   ☐ Milestones определены
   ☐ Critical path identified
   ☐ Dependencies mapped
☐ Team assembled (ключевые роли заполнены)
   ☐ Tech Lead assigned
   ☐ Architect assigned (если нужен)
   ☐ UX Designer assigned (если UI проект)
☐ Risk register reviewed (нет showstoppers)
   ☐ High/Critical risks имеют mitigation plan
   ☐ Contingency plan для top 3 risks
☐ Quality criteria определены (Definition of Done)
☐ Communication plan согласован

[ ] Requirements clarity:
    1 = Vague, 2 = Some ambiguity, 3 = Mostly clear, 4 = Clear, 5 = Crystal clear
    Score: _____

[ ] Stakeholder buy-in:
    1 = Resistance, 2 = Skeptical, 3 = Neutral, 4 = Supportive, 5 = Enthusiastic
    Score: _____

[ ] Team experience with similar projects:
    1 = None, 2 = Limited, 3 = Some, 4 = Good, 5 = Extensive
    Score: _____

[ ] Risk mitigation plan quality:
    1 = No plan, 2 = Weak, 3 = Basic, 4 = Good, 5 = Comprehensive
    Score: _____

TOTAL SCORE: _____ / 20

☐ Requirements Document (BRD/FRD/User Stories)
☐ Project Management Plan
☐ WBS + Schedule (Gantt chart)
☐ Budget breakdown
☐ Risk Register
☐ Communication Plan
☐ Quality Management Plan
☐ NFR Specification (performance, security, etc.)
☐ Assumptions & Constraints

1. [15 min] Презентация requirements (BA)
2. [15 min] Walkthrough scope (WBS) (PM)
3. [10 min] Budget & Schedule overview (PM)
4. [15 min] Risk discussion (Risk Owner)
5. [15 min] Q&A with Architect/Design team
6. [10 min] Gate criteria review
7. [10 min] Decision: Go / Recycle

☐ Architecture утверждена Technical Steering Committee / CTO
   ☐ High-level design (modules, layers, patterns)
   ☐ Low-level design (key components, interfaces)
   ☐ Technology stack approved (frameworks, libraries, tools)
   ☐ Architecture Decision Records (ADR) созданы для key decisions
☐ UI/UX prototypes валидированы пользователями
   ☐ Wireframes reviewed by stakeholders
   ☐ Interactive prototypes tested with users (5-10 users)
   ☐ Usability issues addressed
☐ Database schema reviewed by DBA
   ☐ Entity-Relationship Diagram (ERD) утверждён
   ☐ Indexes planned
   ☐ Migration strategy defined
☐ API contracts согласованы между командами
   ☐ API specifications (OpenAPI/Swagger) готовы
   ☐ Data models defined
   ☐ Error handling agreed
☐ Security architecture reviewed by InfoSec team
   ☐ Authentication/Authorization design approved
   ☐ Data encryption plan (at rest, in transit)
   ☐ Security threats identified (STRIDE analysis)
☐ Non-functional requirements addressed
   ☐ Performance targets defined (response time, throughput)
   ☐ Scalability plan (horizontal/vertical)
   ☐ Availability/DR plan outlined
☐ Design documentation complete
   ☐ System Design Document
   ☐ Component diagrams (UML/C4)
   ☐ Sequence diagrams for key flows

[ ] Architecture quality:
    1 = Monolithic/tightly coupled, 3 = Modular, 5 = Microservices/loosely coupled
    Score: _____

[ ] Design documentation completeness:
    1 = Sparse, 3 = Adequate, 5 = Comprehensive
    Score: _____

[ ] Testability of design:
    1 = Hard to test, 3 = Testable, 5 = Highly testable (mocks, stubs ready)
    Score: _____

[ ] Scalability potential:
    1 = Not scalable, 3 = Scales with effort, 5 = Easily scalable
    Score: _____

[ ] Technology maturity:
    1 = Bleeding edge, 3 = Proven, 5 = Industry standard
    Score: _____

TOTAL SCORE: _____ / 25

☐ Architecture Design Document (ADD)
☐ System Design Specification
☐ Database Schema (ERD + DDL scripts)
☐ API Specifications (Swagger/OpenAPI)
☐ UI/UX Mockups (Figma links)
☐ Architecture Decision Records (ADR)
☐ Component Diagrams (UML/C4)
☐ Sequence Diagrams (for key flows)
☐ NFR Specification (updated)
☐ Technology Stack Document (versions, libraries)

1. [20 min] Architecture walkthrough (Architect)
2. [15 min] Database schema review (DBA)
3. [15 min] API contracts (Backend Lead)
4. [15 min] UI/UX prototypes (Designer)
5. [15 min] Security architecture (InfoSec)
6. [20 min] Q&A with Dev Team
7. [10 min] Gate criteria review
8. [10 min] Decision + Next steps

☐ Все features реализованы (100% code complete)
   ☐ All user stories marked as DONE
   ☐ All tasks in Jira closed
   ☐ No "TODO" comments in code (or tracked in backlog)
☐ Code reviews пройдены (100%)
   ☐ All pull requests merged
   ☐ No unresolved code review comments
   ☐ Code style guide followed
☐ Unit tests пройдены (coverage > {X}%)
   ☐ Unit test coverage > 80% (adjust per company standard)
   ☐ All unit tests green (0 failures)
   ☐ Test results in CI/CD dashboard
☐ Build успешный на CI (все pipelines green)
   ☐ Compilation successful (no errors)
   ☐ Linter passed (no critical issues)
   ☐ Security scan passed (dependency check, SAST)
☐ Code merged to main branch (or release branch)
   ☐ Feature branches merged
   ☐ Conflicts resolved
   ☐ Version tagged (e.g., v1.0.0-rc)
☐ Developer documentation complete
   ☐ API documentation (Swagger/Javadoc/etc.)
   ☐ README updated (setup, run, test)
   ☐ Architecture diagrams updated (if changed)
☐ Known bugs задокументированы в backlog
   ☐ Known issues list created
   ☐ Workarounds documented (if any)

[ ] Code quality (SonarQube score):
    1 = F (много issues), 2 = D, 3 = C, 4 = B, 5 = A
    Score: _____

[ ] Test coverage:
    1 = <50%, 2 = 50-70%, 3 = 70-80%, 4 = 80-90%, 5 = >90%
    Score: _____

[ ] Documentation quality:
    1 = Minimal, 2 = Basic, 3 = Good, 4 = Very good, 5 = Excellent
    Score: _____

[ ] Code maintainability (subjective):
    1 = Spaghetti, 2 = Hard, 3 = OK, 4 = Good, 5 = Excellent
    Score: _____

TOTAL SCORE: _____ / 20

☐ Source Code (Git tag: v1.0.0-rc)
☐ Build Artifacts
   ☐ Binaries / JAR / Docker images (with version tag)
   ☐ Build instructions (or automated via CI/CD)
☐ Unit Test Reports
   ☐ Test results (JUnit XML, etc.)
   ☐ Coverage reports (HTML/XML)
☐ Code Quality Reports
   ☐ SonarQube report (or equivalent)
   ☐ Security scan report (SAST, dependency check)
☐ API Documentation
   ☐ Swagger UI link
   ☐ Postman collection (if applicable)
☐ Known Issues List
   ☐ Bugs deferred to post-release
   ☐ Workarounds documented
☐ Test Environment Setup Guide
   ☐ How to deploy to test environment
   ☐ Test data setup instructions

1. [15 min] Demo of implemented features (Tech Lead)
2. [10 min] Code quality metrics (SonarQube walkthrough)
3. [10 min] Unit test results (Developer)
4. [15 min] Known issues discussion (Tech Lead)
5. [20 min] Test environment setup (DevOps)
6. [10 min] Q&A with QA team
7. [10 min] Gate criteria review

☐ Все test cases выполнены (100%)
   ☐ Functional tests: ____ / ____ passed
   ☐ Integration tests: ____ / ____ passed
   ☐ Regression tests: ____ / ____ passed
☐ Critical bugs исправлены (P0/P1 = 0)
   ☐ P0 (Blocker): 0
   ☐ P1 (Critical): 0
   ☐ P2 (High): ≤ {X} (определяется компанией, обычно ≤5)
☐ Performance tests пройдены (SLA met)
   ☐ Response time < {X} ms (95th percentile)
   ☐ Throughput > {Y} requests/sec
   ☐ No memory leaks detected
   ☐ Load test passed (expected peak load)
☐ Security scan пройден (no critical vulnerabilities)
   ☐ DAST (Dynamic Application Security Testing) passed
   ☐ Penetration test passed (if required)
   ☐ Critical vulnerabilities: 0
   ☐ High vulnerabilities: 0 (or with accepted risk)
☐ UAT approved by business (sign-off)
   ☐ Key user scenarios tested by business users
   ☐ UAT feedback addressed
   ☐ Business owner sign-off obtained
☐ Regression tests пройдены (no new defects)
   ☐ Automated regression suite: 100% pass
   ☐ No regression in existing functionality
☐ Test reports delivered
   ☐ Test execution summary
   ☐ Bug summary report
   ☐ Performance test report
   ☐ Security scan report

[ ] Test coverage (functional):
    1 = <50%, 2 = 50-70%, 3 = 70-85%, 4 = 85-95%, 5 = >95%
    Score: _____

[ ] Bug severity distribution:
    1 = Many P2/P3, 3 = Few P2/P3, 5 = Only P4/P5
    Score: _____

[ ] UAT user satisfaction:
    1 = Dissatisfied, 2 = Needs work, 3 = OK, 4 = Satisfied, 5 = Very satisfied
    Score: _____

[ ] Performance margin:
    1 = Barely meets SLA, 3 = Meets SLA, 5 = Exceeds SLA significantly
    Score: _____

TOTAL SCORE: _____ / 20

☐ Test Execution Report
   ☐ Summary: total tests, passed, failed, blocked
   ☐ Test coverage by feature
☐ Bug Reports (resolved + known issues)
   ☐ Fixed bugs list (with verification)
   ☐ Known issues list (with severity, workarounds)
   ☐ Deferred bugs (to be fixed post-release)
☐ Performance Test Results
   ☐ Load test report (response time, throughput)
   ☐ Stress test report (breaking point)
   ☐ Soak test report (memory leaks, stability)
☐ Security Audit Report
   ☐ DAST report
   ☐ Penetration test report (if done)
   ☐ Vulnerability list (with remediation status)
☐ UAT Sign-off Document
   ☐ Business owner signature
   ☐ UAT test results
   ☐ User feedback summary
☐ Release Notes (draft)
   ☐ New features
   ☐ Bug fixes
   ☐ Known issues
   ☐ Upgrade instructions (if applicable)

1. [10 min] Test execution summary (QA Manager)
2. [15 min] Bug review (critical/high bugs discussion)
3. [10 min] Performance test results (QA Engineer)
4. [10 min] Security audit findings (Security Engineer)
5. [10 min] UAT feedback (Business Owner)
6. [15 min] Production readiness discussion (DevOps)
7. [10 min] Gate criteria review
8. [10 min] Decision + Deployment plan

☐ Deployment успешен (rollout complete)
   ☐ All services deployed to production
   ☐ No deployment errors
   ☐ Health checks green
☐ Smoke tests пройдены в production
   ☐ Key user flows tested (top 3-5 scenarios)
   ☐ All critical APIs responding
   ☐ Database connectivity OK
☐ Monitoring настроен (dashboards created)
   ☐ Application metrics (response time, error rate)
   ☐ Infrastructure metrics (CPU, memory, disk)
   ☐ Business metrics (if applicable: orders, users)
   ☐ Dashboards accessible to operations team
☐ Alerting настроен (on-call setup)
   ☐ Critical alerts defined (downtime, high error rate)
   ☐ Alert routing configured (PagerDuty/Opsgenie)
   ☐ On-call schedule set up
   ☐ Escalation policy defined
☐ Logs aggregated and accessible
   ☐ Application logs → centralized logging (ELK/Loki)
   ☐ Log retention policy set (e.g., 30 days)
   ☐ Log search accessible to operations team
☐ Runbook delivered and reviewed
   ☐ How to restart service
   ☐ How to scale (up/down)
   ☐ How to troubleshoot common issues
   ☐ How to check health
☐ Operations team trained (handover session done)
   ☐ Runbook walkthrough completed
   ☐ Demo of monitoring dashboards
   ☐ Incident response process explained
☐ Rollback plan tested
   ☐ Rollback procedure documented
   ☐ Rollback tested in staging (or dry-run)
   ☐ Rollback can be executed within {X} minutes
☐ Production environment documented
   ☐ Infrastructure diagram (servers, databases, load balancers)
   ☐ Configuration management (where config is stored)
   ☐ Secrets management (where secrets are stored)
☐ SLA/SLO defined and agreed
   ☐ Uptime target (e.g., 99.9%)
   ☐ Response time target (e.g., <200ms p95)
   ☐ Error rate target (e.g., <0.1%)

[ ] Runbook quality:
    1 = Minimal, 2 = Basic, 3 = Good, 4 = Comprehensive, 5 = Excellent
    Score: _____

[ ] Operations team readiness:
    1 = Not ready, 2 = Somewhat ready, 3 = Ready, 4 = Confident, 5 = Very confident
    Score: _____

[ ] Monitoring coverage:
    1 = <50%, 2 = 50-70%, 3 = 70-85%, 4 = 85-95%, 5 = >95%
    Score: _____

[ ] Automation level:
    1 = Manual, 2 = Mostly manual, 3 = Semi-automated, 4 = Mostly automated, 5 = Fully automated
    Score: _____

TOTAL SCORE: _____ / 20

☐ Runbook (operational procedures)
   ☐ Service overview
   ☐ How to start/stop/restart
   ☐ How to scale
   ☐ How to check health
   ☐ Common troubleshooting (top 10 issues)
   ☐ Emergency contacts
☐ Deployment Plan (executed)
   ☐ Deployment steps (completed)
   ☐ Rollback plan
   ☐ Post-deployment checklist
☐ Production Readiness Checklist (completed)
   ☐ All items checked off
☐ Monitoring Dashboards
   ☐ Links to Grafana/Datadog dashboards
   ☐ Credentials (if needed)
☐ Alert Configuration
   ☐ List of alerts (critical/warning)
   ☐ Alert routing (PagerDuty/Opsgenie)
☐ Incident Response Plan
   ☐ Who to call (escalation path)
   ☐ How to declare incident
   ☐ Communication plan (stakeholder notification)
☐ SLA/SLO Agreement
   ☐ Uptime target
   ☐ Performance targets
   ☐ Error budget
☐ Release Notes (final)
   ☐ What's new
   ☐ Known issues
   ☐ Migration steps (for users, if applicable)
☐ Access & Credentials
   ☐ Production access (who has it)
   ☐ Secrets location (vault, etc.)
   ☐ On-call access (VPN, jump hosts)

1. [15 min] Deployment review (Release Manager)
2. [20 min] Runbook walkthrough (DevOps)
3. [15 min] Monitoring demo (SRE)
4. [15 min] Alerting & on-call setup (SRE)
5. [15 min] Incident response process (Operations Manager)
6. [20 min] Q&A with Operations team
7. [10 min] Gate criteria review
8. [10 min] Sign-off + Next steps

☐ EOL decision утверждён бизнесом
   ☐ Business case for retirement approved
   ☐ Sponsor sign-off
☐ Replacement system готов (если применимо)
   ☐ New system deployed and tested
   ☐ Feature parity verified
☐ Migration plan утверждён
   ☐ Data migration strategy defined
   ☐ User migration plan defined
   ☐ Rollback plan (if migration fails)
☐ Data retention policy определена
   ☐ What data to archive (compliance requirements)
   ☐ How long to retain (legal requirements)
   ☐ Where to archive (storage location)
☐ Users уведомлены (minimum notice given)
   ☐ Notification sent (minimum 3 months notice)
   ☐ Alternative solution communicated
   ☐ Migration support offered
☐ Decommissioning plan утверждён Compliance
   ☐ Compliance review passed
   ☐ Legal review passed (data handling)
☐ Stakeholders согласовали closure
   ☐ Business owner OK
   ☐ IT management OK
   ☐ Finance OK (budget closure)

[ ] Migration readiness:
    1 = Not ready, 2 = Some gaps, 3 = Ready, 4 = Well prepared, 5 = Fully ready
    Score: _____

[ ] User impact (обратная шкала):
    1 = High impact, 2 = Medium, 3 = Low, 4 = Minimal, 5 = None
    Score: _____

[ ] Data archival plan quality:
    1 = Minimal, 2 = Basic, 3 = Good, 4 = Comprehensive, 5 = Excellent
    Score: _____

TOTAL SCORE: _____ / 15

☐ Decommissioning Plan
   ☐ Timeline (phases of shutdown)
   ☐ Resource plan (who does what)
   ☐ Risk assessment
☐ Data Archival Plan
   ☐ What data to archive
   ☐ How to export data
   ☐ Where to store (S3 Glacier, tape, etc.)
   ☐ Retention period (per compliance)
☐ Migration Plan (if applicable)
   ☐ Migration steps
   ☐ User migration guide
   ☐ Rollback plan
☐ User Communication Plan
   ☐ Notification emails (drafted)
   ☐ Support plan during transition
☐ Infrastructure Inventory
   ☐ Servers to decommission
   ☐ Databases to archive/delete
   ☐ Licenses to cancel

1. [10 min] EOL decision rationale (Business Owner)
2. [15 min] Decommissioning plan review (PM)
3. [15 min] Data archival plan (Compliance Officer)
4. [10 min] Migration plan (if applicable)
5. [15 min] User communication plan (Communications)
6. [10 min] Infrastructure inventory (Operations)
7. [10 min] Gate criteria review
8. [5 min] Decision + Timeline

☐ Все данные архивированы per retention policy
   ☐ Data export completed
   ☐ Data archived to designated storage
   ☐ Archival verification (can restore if needed)
   ☐ Archival documented (where, what, when)
☐ Вся инфраструктура decommissioned
   ☐ Servers shut down
   ☐ Databases deleted (after archival)
   ☐ DNS records removed
   ☐ Load balancers removed
   ☐ Monitoring alerts disabled
☐ Все пользователи мигрированы
   ☐ Active users migrated to replacement system
   ☐ User data migrated (if applicable)
   ☐ No orphaned users
☐ Все лицензии отменены
   ☐ Software licenses cancelled
   ☐ Cloud resources terminated
   ☐ Final invoices paid
☐ Post-project review завершён
   ☐ Review meeting held (team + stakeholders)
   ☐ What went well documented
   ☐ What went wrong documented
☐ Lessons learned задокументированы
   ☐ Key learnings captured
   ☐ Recommendations for future projects
   ☐ Shared with organization (wiki, presentation)
☐ Финансовый closure
   ☐ All invoices paid
   ☐ Final budget report
   ☐ Cost variance analysis
☐ Team released
   ☐ Team members assigned to new projects
   ☐ Thank you notes sent (recognition)

☐ Data Archival Report
   ☐ What was archived
   ☐ Where it's stored
   ☐ How to retrieve (if needed)
   ☐ Retention expiry date
☐ Decommissioning Completion Report
   ☐ Infrastructure shutdown checklist (completed)
   ☐ Licenses cancelled list
   ☐ Final costs
☐ Post-Project Review Document
   ☐ Project summary (goals, outcomes)
   ☐ Successes
   ☐ Challenges
   ☐ Metrics (budget, schedule, quality)
☐ Lessons Learned Document
   ☐ What worked
   ☐ What didn't
   ☐ Recommendations
   ☐ Best practices to replicate
☐ Final Financial Report
   ☐ Budget vs Actual
   ☐ Cost breakdown
   ☐ ROI (if measurable)
☐ Project Closure Document (signed)
   ☐ Project completed statement
   ☐ Sponsor signature
   ☐ Date of closure

1. [10 min] Decommissioning summary (Operations)
2. [10 min] Data archival report (Compliance)
3. [15 min] Post-project review (PM)
4. [15 min] Lessons learned discussion (Team)
5. [5 min] Final sign-off (Sponsor)
6. [5 min] Team recognition & celebration