Corporate DevOps Training — Brief
Company/team: ______________  Location: Noida (on-site / remote / mixed)
Participants: __ people; roles: ______________
Current stack: language ____, CI ____, cloud ____, containers ____
Top goals (after training the team can):
  1.
  2.
  3.
Preferred format: on-site / live online / hybrid
Timeline: start ____, sessions per week ____, avoid ____
Please include in your proposal: syllabus, lab plan, trainer profile,
assessment approach, schedule, commercial terms

Good training goals are observable:
✔ 'Each participant writes a Dockerfile for their own service'
✔ 'Team adds a CI pipeline with tests to two repositories'
✔ 'Ops engineers create a staging environment with Terraform'
✘ 'Understand DevOps'
✘ 'Learn Kubernetes'

Ask the trainer during the trial session:
1. Our CI pipeline takes 40 minutes. Where would you look first?
2. A container works locally but crashes in Kubernetes. How do you debug it?
3. How would you introduce Terraform to a team with existing manual infrastructure?
Good answers are practical, structured and mention specific commands or steps.

Vendor Scoring (1-5)
                         Vendor A   Vendor B   Vendor C
Fit to our goals/stack     ___        ___        ___
Trainer hands-on depth     ___        ___        ___
Trial session quality      ___        ___        ___
Lab readiness              ___        ___        ___
Assessment approach        ___        ___        ___
Schedule flexibility       ___        ___        ___
Commercial clarity         ___        ___        ___
TOTAL                      ___        ___        ___

Pre-training checklist (one week before)
☐ Participant list and roles confirmed
☐ Lab accounts created and tested by one participant
☐ Proxy/firewall allows lab URLs and container registries
☐ Docker runs on participant laptops (or cloud labs ready)
☐ Calendars blocked; managers informed
☐ Room booked with screen and power points (on-site)
☐ Communication channel for questions set up

# Each participant runs this before day one
git --version
docker --version && docker run --rm hello-world
kubectl version --client
curl -sI https://registry-1.docker.io/v2/ | head -1
# Any failure → report in the training channel before the first session

Programme Schedule (example, adjust to your scope)
Session 1: Git workflow and code review
Session 2: Linux and scripting essentials
Session 3: Docker fundamentals on team services
Session 4: CI pipelines with tests
Session 5: Container deployment basics
Session 6: Infrastructure as code
Session 7: Monitoring and alerts
Session 8: Capstone presentations
Between sessions: lab assignments (1-2 hours)

Attendance & Lab Tracker
Name        S1  S2  S3  S4  S5  S6  S7  S8   Labs done
________    ☐   ☐   ☐   ☐   ☐   ☐   ☐   ☐    __/8
________    ☐   ☐   ☐   ☐   ☐   ☐   ☐   ☐    __/8
Follow up with anyone below 75% attendance.

Weekly Stakeholder Update
Week: ____
Sessions completed: __ of __
Average attendance: __%
Labs completed: __%
Highlights: ______________
Blockers (access, schedule): ______________
Next week: ______________