Sprint
Designation Office
Appendix A
The complete register
385 entries · 8 genres
A.0 / Preamble Public record

Funny Sprint Names

Every name this office has ever issued, all 385 of them, published in full. They exist because the alternative was another sprint called Synergy & Innovation, and because the generators that produce Sprint Blue Falcon by welding an adjective to a random noun are not actually funny — they just have the shape of a joke.

Nothing here is generated. Every entry was written by hand and earns its place by being either uncomfortably accurate (Refactor and Pray) or tonally deranged (Soft Launch Into Darkness). Mild office humour is the exact failure mode this register exists to escape.

The number after each name is its character count, which matters more than it should — see sprint name character limits in Jira. Click any name to have it stamped properly by the generator.

A.1 / Contents 8 genres
01 / Enterprise Sarcasm 69 entries · 66 under 26

Enterprise Sarcasm Sprint Names

Names for the sprint that exists because a roadmap said so. The vocabulary of steering committees and quarterly objectives, quoted back accurately enough to sting. More on this genre →

  1. Refactor and Pray17
  2. Tactical Optimism17
  3. Ship Happens12
  4. Merge With Caution18
  5. Agile-ish9
  6. Retrospective Regret20
  7. Plausible Deniability21
  8. Overengineered for Safety25
  9. Per My Last Email17
  10. Re: Per My Last Email21
  11. Stakeholder Delight19
  12. Selective Transparency22
  13. Cache Me Outside16
  14. Ship It Anyway14
  15. Optimistic Rollback19
  16. Minimal Viable Apology22
  17. Enterprise Grade Anxiety24
  18. Refinement by Fire18
  19. Unintended Consequences23
  20. Human Interface Problem23
  21. Scope Drift Initiative22
  22. Hotfix Horizon14
  23. Silent Breaking Change22
  24. Rollback Ready14
  25. Minor Major Release19
  26. Soft Deadline13
  27. Future Technical Debt21
  28. Spec Drift10
  29. Incident Driven Dev19
  30. Untested Confidence19
  31. Courageous Refactor19
  32. Blameless Postmortem20
  33. Architectural Regret20
  34. Deadline Negotiation Phase26
  35. Definition of “Done-ish”24
  36. High Risk No Reward19
  37. Just One More Thing19
  38. Regression Roulette19
  39. Release and Regret18
  40. Unverified Assumptions22
  41. Elegant Workaround18
  42. Feature Creep Diplomacy23
  43. Strategic Reprioritization26
  44. Deadline Is a Suggestion24
  45. Continuous Partial Delivery27
  46. Legacy of Tomorrow18
  47. Technical Debt Jubilee22
  48. Ship First, Document Never26
  49. Slightly Deterministic22
  50. Chaos Driven Development24
  51. Bug Driven Development22
  52. Roadmap to Nowhere18
  53. Sustainable Panic17
  54. Test in Prod12
  55. Compliance Adjacent19
  56. Fail Forward Aggressively25
  57. Stakeholder Alignment Ritual28
  58. Soft Launch Into Darkness25
  59. Beta Is the New Stable22
  60. Zero Downtime (Mostly)22
  61. Mission Critical-ish20
  62. Cloud Native Denial19
  63. Scalable Confusion18
  64. Automated Blame Pipeline24
  65. Governance Theater18
  66. Architecture Astronautics25
  67. Incremental Catastrophe23
  68. Proactive Damage Control24
  69. Every User Has a Test System28
02 / Developer Despair 84 entries · 79 under 26

Developer Despair Sprint Names

The largest genre, which tells you something about the sample. For sprints defined less by their goal than by the state of the codebase they inherited. More on this genre →

  1. Works on My Machine19
  2. Git Blame the Other Guy23
  3. Not My Branch13
  4. Works in Production19
  5. Probably Not My Bug19
  6. Wasn’t Me9
  7. Ask the Previous Developer26
  8. It Was Like That Already24
  9. I Inherited This16
  10. Who Wrote This?15
  11. Future Me’s Problem19
  12. Cannot Reproduce16
  13. It Worked In Staging20
  14. Just Don’t Touch It19
  15. Do Not Refactor15
  16. Please Don’t Look17
  17. It’s Probably Caching21
  18. Must Be DNS11
  19. You’re Sure It’s not DNS?25
  20. Must Be a Race Condition24
  21. Legacy by Choice16
  22. Technical Debt Enjoyer22
  23. Tech Debt Is Due16
  24. Held Together by Hope21
  25. Comments Are the Documentation30
  26. README was Lying16
  27. The Tests Know Too Much23
  28. Tests Are Optional18
  29. CI Said Maybe13
  30. Green Enough12
  31. Pipeline Roulette17
  32. Merge and Find Out18
  33. Push First, Understand Later28
  34. Commit and Forget17
  35. Revert and Pretend18
  36. Git Revert My Life18
  37. Git Reset My Expectations25
  38. Force Push of Despair21
  39. Branching Out of Control24
  40. Detached From Reality21
  41. Lost in Git History19
  42. Commit Archaeology18
  43. Blame Driven Development24
  44. Debugging by Astrology22
  45. Stack Overflow Archaeology26
  46. Copy Paste Engineering22
  47. Cargo Cult Coding17
  48. Trial and Error™16
  49. Null and Void13
  50. Undefined Behavior, Defined Lifestyle37
  51. Concurrency Is a Social Problem31
  52. State Management Crisis23
  53. One More If11
  54. Just One More Flag18
  55. Just One More Bitmap20
  56. Temporary Permanent Fix23
  57. Permanent Temporary Fix23
  58. Quick Fix, Long Term Consequences33
  59. Five Minute Refactor20
  60. Small Change™13
  61. Tiny Little Hotfix18
  62. Harmless Change15
  63. Mostly Harmless15
  64. Nothing Could Go Wrong22
  65. Past Me Was an Idiot20
  66. Past Me Did This16
  67. Past Me Had Reasons19
  68. Future Me Hates This20
  69. Somebody Approved This22
  70. It Passed Review16
  71. LGTM4
  72. Approved Under Duress21
  73. Peer Reviewed, Allegedly24
  74. Tested in Spirit16
  75. QA Has Been Notified20
  76. Waiting for Reproduction24
  77. Waiting for Godot.js20
  78. QA Has Feedback15
  79. Users Are the Test Suite24
  80. Customer Driven Debugging25
  81. Live Debugging Experience25
  82. Monday Morning Rollback23
  83. Deploy First, Panic Later25
  84. Git History Repeats Itself26
03 / On-Call Horror 23 entries · 23 under 26

On-Call Horror Sprint Names

For the sprint that follows an incident, or contains one. Named from the pager's point of view, at the hour the pager prefers. More on this genre →

  1. Three AM Deployment19
  2. Escalation Pending18
  3. Wake Up, It’s Prod18
  4. Who Has the Phone17
  5. Weekend Incident16
  6. On Call, On Sight17
  7. Rotating the Suffering22
  8. Severity: Weekend17
  9. Blast Radius: Bedroom21
  10. Five Nines, Zero Sleep22
  11. Uptime at Any Cost18
  12. Availability Has a Price24
  13. SLA Versus REM14
  14. Prod Has Your Number20
  15. Prod Needs You14
  16. Prod Called11
  17. Prod Calls Again16
  18. Prod Knows Where You Sleep26
  19. Weekend Availability Event26
  20. Pinged by DevOps16
  21. Not My Oncall Duty18
  22. Pager Duty Jump Scare21
  23. Friday Deploy Survivor22
04 / Hope Driven Dev 42 entries · 38 under 26

Hope Driven Dev Sprint Names

Optimism deployed as an engineering methodology. Best used at the start of a quarter, before the estimates have met the calendar. More on this genre →

  1. Optimism Under Review21
  2. Hope Driven Development23
  3. Confidence Pending18
  4. Probably Fine13
  5. Trust the Process17
  6. Faith Based Deployment22
  7. Strategic Optimism18
  8. Hope as a Strategy18
  9. Deferred Optimism17
  10. Tentative Success17
  11. Fingers Crossed15
  12. Managed Expectations20
  13. Controlled Optimism19
  14. Hopeful Regression18
  15. Confidence in Progress22
  16. Promisingly Unstable20
  17. Potentially Fine16
  18. Eventually Correct18
  19. Progress, Allegedly19
  20. Low Confidence, High Hopes26
  21. Operational Optimism20
  22. Best Case Scenario18
  23. Plan B Is Hope14
  24. Nothing Can Go Wrong20
  25. Surely This Time16
  26. One More Sprint15
  27. The Next Sprint Will Fix It27
  28. We’ll Get There15
  29. Forward With Confidence23
  30. Confidence Without Evidence27
  31. Premature Success17
  32. Unvalidated Hope16
  33. Optimistically Incorrect24
  34. Statistically Encouraging25
  35. A Reasonable Amount of Hope27
  36. Hope Based Prod Deployment26
  37. Release With Confidence23
  38. Confidence Is Key17
  39. Plan Adjacent13
  40. Outcome Pending15
  41. Positive Developments Pending29
  42. Please Do Not the Code22
05 / Gen Z Brainrot 70 entries · 57 under 26

Gen Z Brainrot Sprint Names

Internet vernacular applied to release planning. The irony is load-bearing — check the size of your stakeholder audience before committing. More on this genre →

  1. Trigger Warning: Story Points29
  2. Agile Goblin Mode17
  3. POV: We Actually Finish This28
  4. Delulu Is the Solulu20
  5. No Cap, Just Bugs17
  6. Copium Driven Development25
  7. It’s Giving Technical Debt26
  8. Main Character Deployment25
  9. Lowkey Production Ready23
  10. Highkey Not Tested18
  11. Let Him Cook12
  12. Who Let Him Cook?17
  13. Never Cook again16
  14. We’re So Back13
  15. Never Been More Joever22
  16. Chat, Are We Cooked?20
  17. Chat, We’re So Back19
  18. Bro Thought It Was Agile24
  19. Skill Issue: Requirements25
  20. Absolute Unit of Scope22
  21. Aura Farming: Sprint Edition28
  22. Negative Aura Deployment24
  23. Aura Based Deployment21
  24. +100 Aura, 0 Tests18
  25. Vibes-Based Engineering23
  26. Trust Me Bro12
  27. Canon Event: Production Bug27
  28. Lore Accurate Technical Debt28
  29. Plot Armor Deployment21
  30. The Sprint Lacks Aura21
  31. Unspoken Rizz Requirements26
  32. Requirements? I Barely Know Her31
  33. Yapping In The Review Comments30
  34. Cooked by Refinement20
  35. Let Him Merge13
  36. Deploy and Manifest19
  37. Manifesting a Green Pipeline28
  38. Manifesting No Rollback23
  39. Manifestation > Estimation26
  40. Delulu Planning Session23
  41. Certified Copium Sprint23
  42. Premium Copium14
  43. Enterprise Grade Copium23
  44. Copium as a Service19
  45. Hopepilled10
  46. Optimismpilled14
  47. Sprintpilled12
  48. Agilepilled11
  49. Kanbanmaxxing13
  50. Agilemaxxing12
  51. Productivitymaxxing19
  52. Techdebtmaxxing15
  53. Stakeholdermaxxing18
  54. Refactormaxxing15
  55. We Ship7
  56. No QA, We Ball14
  57. YOLO Driven Development23
  58. Skill Issue, Scalable21
  59. It’s Giving Incident20
  60. It’s Giving Rollback20
  61. It’s Giving 50015
  62. Slay Now, Debug Later21
  63. Gaslight, Gatekeep, Git Push28
  64. Gaslight the Acceptance Criteria32
  65. POV: The Estimate Was Binding29
  66. POV: QA Found Nothing21
  67. POV: Friday Deployment22
  68. POV: We Learned From Last Sprint32
  69. POV: This Time Is Different27
  70. Vibe-Based Architecture23
06 / BOFH Excuses 36 entries · 26 under 26

BOFH Excuses Sprint Names

In the tradition of the Bastard Operator From Hell: explanations offered to users, none of them true, all of them technically unfalsifiable. More on this genre →

  1. Root Dried Out14
  2. Woodworms in Hashtable22
  3. Cookies Went Stale18
  4. Kernel Got Damp15
  5. Packets Got Lost16
  6. Hash Collision Outbreak23
  7. Bitrot in Staging17
  8. Trust Store Has Trust Issues28
  9. Garbage Collector Unionized27
  10. Race Condition Won18
  11. Deadlock Became Permanent25
  12. Heap Developed Mold19
  13. Pointer Wandered Off20
  14. Null Pointer Escaped20
  15. Bytecode Got Wet16
  16. Merge Conflict Metastasized27
  17. Commit Lost Structural Integrity32
  18. HEAD Detached Itself20
  19. Repository Developed Termites29
  20. Build Server Is Haunted23
  21. Stubborn Processes18
  22. Pipeline Lost Pressure22
  23. Pipeline Started Leaking24
  24. Ether Leak10
  25. Microservice Became Macroservice32
  26. Endpoint Migrated Spontaneously31
  27. Load Balancer Developed Bias28
  28. Reverse Proxy Reversed Too Far30
  29. TLS Certificate Lost Confidence31
  30. Session Wandered Off20
  31. Regex Became Self-Aware23
  32. YAML Indentation Drift22
  33. Backbone Collapsed18
  34. Solar Flares12
  35. Cosmic Build Failure20
  36. Daemons7
07 / Corporate Cult 28 entries · 18 under 26

Corporate Cult Sprint Names

For organisations where “alignment” has quietly stopped being a metaphor. Onboarding as initiation, company values as liturgy. More on this genre →

  1. Welcome to the Process22
  2. Trust the Framework19
  3. The Framework Knows19
  4. Velocity Is Watching20
  5. The Ceremony Begins at 09:0028
  6. Your Feedback Is Valuable25
  7. You Have Been Selected for Refinement37
  8. The Backlog Provides20
  9. Do Not Question the Roadmap27
  10. The Roadmap Is Eternal22
  11. Scrum Master Sacrifice22
  12. Compliance Is Enlightenment27
  13. Attendance Is Mandatory23
  14. The Board Sees All18
  15. Alignment Is Peace18
  16. Deviation Has Been Logged25
  17. The Scope Is Sacred19
  18. Sprint Zero Never Ended23
  19. Your Capacity Has Been Assigned31
  20. Resistance Is a Blocker23
  21. The Velocity Must Rise22
  22. We Do Not Question Estimates28
  23. The Ceremony Cannot Be Skipped30
  24. All Praise the Burndown23
  25. The Sprint Will Continue Without You36
  26. The Burndown Shall Judge Us27
  27. Blessed Are The Aligned23
  28. May The Framework Have Mercy28
08 / Occult Scrum 33 entries · 19 under 26

Occult Scrum Sprint Names

Agile ceremony taken literally. Stand-up as summoning, retrospective as séance, and a backlog that grows when nobody is observing it. More on this genre →

  1. Summoning the Definition of Done32
  2. Ritual of the Missing Requirement33
  3. The Forbidden Backlog21
  4. Blood Pact With Production26
  5. The Ancient Ticket Awakens26
  6. Invoke the Hotfix17
  7. The Stakeholder Has Foreseen It31
  8. Seven Sprints of Darkness25
  9. The Pipeline Demands a Sacrifice32
  10. KPI Exorcism12
  11. The Merge Beyond the Veil25
  12. As the Prophecy Predicted25
  13. Do Not Merge After Midnight27
  14. The Standup Has No End22
  15. Nine Voices, One Estimate25
  16. The Sprint Goal Chose Us24
  17. Something Is in the Backlog27
  18. The Retro Remembers19
  19. It Knows Your Velocity22
  20. Do Not Name the Sprint22
  21. The Ticket Was Always There27
  22. Whispers in the Changelog25
  23. We Have Always Been Sprinting29
  24. The Scrum Master Has No Reflection34
  25. The Burndown Never Reaches Zero31
  26. Speak Not of the Velocity25
  27. It Estimated Itself19
  28. Something Groomed the Backlog29
  29. The Daily Never Ended21
  30. We Do Not Speak of Sprint 1328
  31. The Velocity Wants More23
  32. The Backlog Grows in Darkness29
  33. Nothing Was Committed. Something Was.37
A.9 / Character limits Why the counts are there

How many of these fit in Jira

Jira caps a sprint name at 30 characters, and a board prefix spends part of that before the name begins. The full explanation, with sources, is on sprint names for Jira. The short version is this table.

GenreNames≤ 30≤ 26
Enterprise Sarcasm696966
Developer Despair848179
On-Call Horror232323
Hope Driven Dev424238
Gen Z Brainrot706757
BOFH Excuses363226
Corporate Cult282518
Occult Scrum332619
Total385365326
A.10 / Disposal End of register

Reading a list is not the same as being handed a verdict. The generator convenes a committee, deliberates briefly, and stamps exactly one name — and it remembers which ones you have already been given, so it keeps serving fresh ones until a genre runs dry.

Convene the committee