Lab 05: Step-by-Step Guide
Overview
This guide walks you through completing Lab 05: The POC Sprint, from initial scoping to final demo.
Phase 1: Planning (1-2 hours)
Step 1: Scope the POC
Review templates:
bashcd labs/05-poc-sprint ls templates/Fill out scope document:
- Open
templates/poc-scope-document.md - Fill in all sections
- Define objectives
- Set scope boundaries
- Open
Define success criteria:
- Open
templates/success-criteria.md - Define must-have criteria
- Define should-have criteria
- Define nice-to-have criteria
- Open
Get stakeholder approval:
- Share scope document
- Get sign-off
- Set expectations
Step 2: Prepare Demo Materials
Review demo script:
- Open
demo-prep/demo-script.md - Customize for your POC
- Practice the flow
- Open
Prepare backup demo:
- Review
demo-prep/backup-demo.md - Prepare screenshots
- Prepare architecture diagrams
- Review
Review common questions:
- Open
demo-prep/common-questions.md - Prepare your answers
- Practice responses
- Open
Phase 2: Deployment (15-30 minutes)
Step 3: Deploy Infrastructure
Option A: GCP Deployment
cd labs/05-poc-sprint/minimal-deployment
cp terraform.tfvars.example terraform.tfvars
# Edit terraform.tfvars with your project ID
cd ..
./scripts/quick-deploy.shOption B: Local Deployment (Kind)
# Create Kind cluster
kind create cluster --name poc-cluster
# Deploy Argo Workflows
helm repo add argo https://argoproj.github.io/argo-helm
helm install argo-workflows argo/argo-workflows \
--namespace argo \
--create-namespace \
--waitStep 4: Verify Deployment
# Check cluster
kubectl get nodes
# Check Argo Workflows
kubectl get pods -n argo
# Check services
kubectl get svc -n argoStep 5: Deploy Demo Workflows
# Deploy all demo workflows
kubectl apply -f manifests/
# Verify workflows
kubectl get workflows -n argoPhase 3: Preparation (30-60 minutes)
Step 6: Prepare Demo Environment
./scripts/prepare-demo.shThis will:
- Verify Argo Workflows is running
- Deploy demo workflows
- Set up demo namespace
- Provide access information
Step 7: Test Demo Workflows
Access Argo UI:
bashkubectl port-forward -n argo svc/argo-workflows-server 2746:2746Open: http://localhost:2746
Test each workflow:
- Submit simple workflow
- Submit multi-step workflow
- Submit parallel workflow
Verify everything works:
- All workflows execute
- Logs are accessible
- UI displays correctly
Step 8: Prepare Backup Materials
Take screenshots:
- Argo UI dashboard
- Workflow executions
- Architecture diagrams
Prepare architecture discussion:
- Review architecture
- Prepare talking points
- Prepare diagrams
Test backup demo:
- Practice with screenshots
- Practice architecture discussion
- Ensure materials are ready
Phase 4: Execution (1-2 weeks)
Step 9: Daily Standups
Use templates/daily-standup-format.md:
- What did you accomplish yesterday?
- What will you do today?
- Any blockers?
Step 10: Track Progress
Update success criteria:
- Track must-have criteria
- Track should-have criteria
- Document nice-to-have
Document issues:
- Track problems
- Document solutions
- Update stakeholders
Adjust if needed:
- Scope adjustments
- Timeline adjustments
- Resource adjustments
Phase 5: Demo (15-30 minutes)
Step 11: Deliver Demo
Follow demo-prep/demo-script.md:
- Introduction (2 min)
- Architecture Overview (3 min)
- Simple Workflow (3 min)
- Multi-Step Workflow (4 min)
- Parallel Workflow (4 min)
- Q&A (3-5 min)
Step 12: Handle Questions
Use demo-prep/common-questions.md:
- Answer technical questions
- Address business concerns
- Discuss next steps
Step 13: Follow Up
Send materials:
- Demo recording
- Architecture diagrams
- Documentation
Answer questions:
- Respond to outstanding questions
- Provide additional information
Schedule next steps:
- Based on demo feedback
- Address concerns
- Plan implementation
Phase 6: Documentation (1-2 hours)
Step 14: Create Final Report
Use templates/final-report-template.md:
- Executive Summary
- What Was Accomplished
- Success Criteria Results
- Lessons Learned
- Recommendations
- Next Steps
Step 15: Share Outcomes
Distribute report:
- Send to stakeholders
- Share with team
- Archive for future reference
Present findings:
- Present to decision makers
- Answer questions
- Discuss recommendations
Plan next steps:
- Based on outcomes
- Address recommendations
- Plan implementation (if approved)
Phase 7: Cleanup (5 minutes)
Step 16: Clean Up Resources
./scripts/cleanup.shOr manually:
cd minimal-deployment
terraform destroyTips for Success
Planning
✅ Start with clear problem statement ✅ Define specific objectives ✅ Set realistic timeline ✅ Get stakeholder buy-in
Execution
✅ Deploy quickly ✅ Test early and often ✅ Communicate regularly ✅ Stay focused on scope
Demo
✅ Practice beforehand ✅ Have backup plan ✅ Engage audience ✅ Be honest about limitations
Documentation
✅ Document everything ✅ Capture lessons learned ✅ Provide clear recommendations ✅ Share knowledge
Common Pitfalls
Pitfall 1: Scope Too Broad
Problem: Trying to prove everything Solution: Focus on 2-3 core objectives
Pitfall 2: No Success Criteria
Problem: Unclear what success means Solution: Define measurable criteria upfront
Pitfall 3: Poor Communication
Problem: Stakeholders don't know status Solution: Regular updates, daily standups
Pitfall 4: No Backup Plan
Problem: Demo fails, no recovery Solution: Always have backup materials
Pitfall 5: Incomplete Documentation
Problem: Can't remember what happened Solution: Document as you go