TiGGR: Push It Real Good
A DevOps Disaster One-Shot for the TiGGR System
Inspired by The Unicorn Project
Written by fate, fire, and the ghost in your Jenkinsfile.
Inspired by the first chapter of The Unicorn Project, this TiGGR one-shot lets players embody the chaos, camaraderie, and quiet despair of IT life:
- The Build Oracle (“I’ve seen this error before…”)
- The Ticket Wrangler (bluffing Jira tickets like it’s poker night)
- The Legacy Whisperer (still speaks fluent XML)
Instead of fixing the system, you just try to survive the sprint.
Deploy something. Don’t blame anyone you’ll see at lunch.
And if Blame Level hits 5? Trigger a Mass Resume Cascade.
It’s like a workplace TPK—but with LinkedIn for your Valhalla.
We all have war stories. And to survive is, in reality, to thrive.
Telling those stories—through play, satire, and shared laughter—might just be how we make sense of them.
TiGGR Compatibility
This is a one-shot adventure designed for the TiGGR RPG system. All core mechanics apply:
- 3 stats (Body, Mind, Charm)
- Roll 2d6 + stat against difficulty (6/8/10)
- 5 HP
- Signature Ability & Signature Gear
- No XP, just vibes
Scenario: “Your First Day”
You’ve just been assigned to the Unicorn Project.
It’s in production. It’s on fire. And somehow… it’s your fault.
Fix the pipeline. Push the release. Survive the day.
Try not to get blamed.
Setting Generator
| Element | Description |
|---|---|
| Faction 1 | The Ops Monks — maintainers of prod, never commit directly |
| Faction 2 | The Business Analysts — demand the release, don’t understand CI |
| Weird Hook 1 | A forgotten CI server wakes up and runs old jobs from 2017 |
| Weird Hook 2 | A surprise audit is happening… today |
| Goal | Deploy by 5PM or get reassigned to the Mainframe Team |
| Cool Gear | root.yaml — you don’t know what it does, but you keep it close |
Pre-Generated Characters
| Name | Stat Focus | Ability | Gear |
|---|---|---|---|
| The Build Oracle | Mind +2 | “I’ve seen this error.” Auto-succeed one log interpretation. | .bash_history |
| The Ticket Wrangler | Charm +2 | “It’s documented somewhere.” Auto-succeed one Jira bluff. | Keyboard missing Esc |
| The Legacy Whisperer | Mind +1 | “I remember this code.” Reroll any action on code pre-2010. | Printed XML configs |
| The Safety Engineer | Charm +1 | “That’s non-compliant.” Block one deploy or redirect blame. | SOX Handbook |
| The Junior | Body +2 | “What does this do?” Ignore the first CI failure. | Copied Stack Overflow post |
| The Platform Monk | Balanced | “I speak YAML.” Fix any misconfigured .yaml once per game. | Blessed kubeconfig file |
Adventure Beats (Choose 3 Scenes)
- Morning Check-In — You’re introduced. Jenkins fails.
- Blame Triangle — Dev blames Ops. Ops blames Dev. Business blames you.
- Pipeline Panic — A build kicks off. Nobody knows who triggered it.
- Git Séance — Your name shows on a commit from 3 months ago.
- Manual Deploy — You must SSH into prod. Someone says “we’ve always done it this way.”
- Surprise Audit — Security appears. “Can you show us the rollback plan?”
Status Tracker
Track these shared team values:
- Blame Level (0–5)
- Time Until Demo (Hours)
- Incidents Triggered
- Tabs Open
If Blame Level hits 5, trigger a Mass Resume Cascade.
Everyone must narrate their new LinkedIn bio.
Win Condition
You don’t win by saving prod.
You win by:
- Shipping something
- Blaming no one you’ll see at lunch
- Living to Slack about it
Attribution
This setting uses the TiGGR RPG System by the Grey Ledger Society, licensed under CC BY 4.0.
Visit TiGGR SRD for full rules.
“It’s not about fixing the system.
It’s about surviving the sprint.”