The Engineering Team vs. The Sisyphean Product Backlog
Description
This meme uses the famous 2021 photo of the Ever Given container ship stuck in the Suez Canal. The massive bow of the ship, which has 'EVER' visible on it, is labeled in red text as 'Product backlog'. On the sandy bank of the canal, a comically small excavator and two workers are positioned next to the colossal vessel, labeled 'Engineering Team'. The image perfectly captures the overwhelming and often hopeless feeling experienced by software development teams when faced with an enormous, ever-growing product backlog. The scale difference between the tiny excavator and the giant ship serves as a powerful visual metaphor for an under-resourced engineering team trying to make a dent in a seemingly insurmountable mountain of tasks, features, and technical debt. It’s a relatable scenario for any developer who has felt their efforts are just a drop in the ocean
Comments
7Comment deleted
That excavator is the senior dev trying to remove one small piece of tech debt while the PM keeps adding more containers to the ship and asking for an ETA
Product: “Just increase velocity 20% and we’re on track.” Me, the lone digger whispering Little’s Law to an Ever-Given-sized backlog: “At this throughput, the only thing leaving the canal is my optimism.”
Just like the Ever Given, our product backlog has been blocking all forward progress since Q1, and somehow management thinks one excavator-sized engineering team can clear 400 meters of technical debt by next sprint. At least the Suez Canal eventually got unblocked
When the product backlog is so massive it literally blocks the entire delivery pipeline, and stakeholders keep asking why the engineering team can't just 'dig faster' with their single excavator. Bonus points if PM suggests 'just adding more excavators' without considering the canal's width constraints - classic resource allocation fallacy meets the mythical man-month
Classic Agile: tiny team shoveling story points while the JIRA arrival rate (lambda) exceeds our throughput (mu); Little’s Law says we’re not shipping, just landscaping
Enterprise Agile in one photo: splitting epics until they fit the shovel while Little’s Law reminds us the constraint is the canal, not the story size
Product backlog hits escape velocity: now it's the Ever Given of your delivery pipeline, partitioning throughput across the devops canal