LOCAL PREVIEW View on GitHub

Behavioural Scenarios — CI/CD Pipeline Conflicts

Overview

This subfolder contains 4 realistic conflict scenarios that arise during CI/CD pipeline design and operation for the Amazon AI Chatbot. Each scenario involves disagreements between team leads, architects, product managers, and/or DevOps engineers — reflecting the kinds of cross-functional tensions that occur in real production AI systems.

These scenarios are structured for behavioral interview preparation using the STAR format (Situation, Task, Action, Result) and provide multiple stakeholder perspectives with justified positions.


Scenarios

# Scenario Core Conflict Stakeholders
BH-01 Deployment Frequency Conflict PM demands daily deploys vs Architect wants weekly release trains vs Team Lead facing developer burnout PM, Architect, Team Lead
BH-02 ML Model Deployment Gate Disagreement DS Lead wants immediate model push vs Architect requires full shadow+canary vs PM sides with urgency DS Lead, Architect, PM
BH-03 CI/CD Tooling Choice Conflict Architect mandates CodePipeline vs Team Lead champions GitHub Actions vs DevOps prefers Terraform Cloud Architect, Team Lead, DevOps, PM
BH-04 Rollback Policy Conflict Post-incident: Architect wants 2hr canary on ALL changes vs PM says it kills A/B testing vs Team Lead wants better alerts Architect, PM, Team Lead

Scenario Structure

Each scenario follows a consistent format:

  1. Scenario Context — The situation, project phase, and what's at stake
  2. The Conflict — Each stakeholder's position with their rationale (presented fairly — no villain)
  3. Stakeholder Position Map — Mermaid diagram showing the tension vectors
  4. Your Role — You are the Senior Developer navigating this conflict
  5. STAR Analysis — Situation, Task, Action, Result walkthrough
  6. Resolution — What was decided, why, and what compromises were made
  7. Key Takeaways — Generalizable lessons for similar situations
  8. Interview Tips — How to present this scenario in a behavioral interview

How to Use

  • Interview prep: Practice articulating each scenario in 2-3 minutes using the STAR format
  • Team discussions: Use as discussion starters for CI/CD process design meetings
  • Conflict resolution patterns: Each scenario demonstrates a different resolution strategy (data-driven, compromise, tiered approach, risk-based)

Relationship to User Stories

Scenario Related User Story Connection
BH-01 CD-01: Application Code Pipeline Deployment frequency directly impacts pipeline design
BH-02 CD-03: ML Model Pipeline Quality gate strictness determines model deployment speed
BH-03 CD-01, CD-02 Tooling choice affects all pipelines
BH-04 CD-06: Config & Prompt Pipeline Rollback policy scope determines config change velocity