Editor's note: This post is satire. Please do not threaten your colleagues. CocoaPatterns does not endorse workplace violence. Brad, our legal team would like to speak with you again.
In the literature on software development methodologies, researchers have examined the effects of deadlines, incentives, and psychological safety on engineer productivity. One variable that remains conspicuously unstudied — due to what I can only assume is IRB cowardice — is the effect of mild, proportionate, and clearly telegraphed physical consequence on ticket closure rates.
"Pair programming creates accountability through observation. Violence-Driven Development creates accountability through... a different mechanism."
The VDD Sprint Cycle
In a traditional two-week sprint, engineers commit to story points with the implicit understanding that incomplete stories roll over, where they will also be incomplete, until they are eventually split, deprioritized, or quietly deleted during a roadmap refresh.
In VDD, incomplete stories have a different consequence. Specifically, the consequence is a firm handshake from a designated Sprint Enforcer — a role that rotates among senior engineers and is, in our model, entirely consensual and metaphorical.
The Sprint Enforcer role is, in practice, a person who stands near the incomplete ticket and makes sustained eye contact. That's it. That's the violence. We may have oversold the concept in the title.
Observed Outcomes
- Story point completion rate: up 31% (engineers are completing stories specifically to make the eye contact stop)
- Sprint Enforcer satisfaction: high (turns out some engineers find this extremely enjoyable)
- Standup duration: down 40% (nobody wants to explain why their ticket is still "In Progress")
- HR inquiries: 3 (all resolved once we clarified "eye contact" was the full extent of the methodology)
We're now exploring Guilt-Driven Development, where the Sprint Enforcer simply sighs audibly near your desk when your PR has been open for more than 48 hours. Early results suggest it's twice as effective and significantly more scalable.