Ah yes the forgotten land of uncompleted tasks. Slated to be a hotfix when it becomes a problem.
And one that requires several people to give up a weekend, too.
I don’t know when this meme was originally made, but my boss unironically has this taped to his office door, and it’s glorious
Everywhere I’ve ever been,
If it’s lower than “High” or “2”, it’s as good as “backlog” :)
(There can never be a priority “1” and seldom “Highest”, never “Blocker”, otherwise the CEO gets a text or something.)
Scrum Master: “Do we really have to make it a blocker?”
Me: “Uh yeah. It’s blocking these three other tasks.”
Scrum Master: “But is it really?”
Me: “Yes.”
Scrum Master: “Let’s just leave it on in development and we can review the progress tomorrow.”
Me: “That’s what you said yesterday.”
Scrum Master: “Alright guys. I’m going to give you back five minutes of your time today.”
Holy shit that’s too real. I come here to get away from work!
Don’t forget breaking everything up into ever-smaller tasks just so that something, anything, can be closed every day. 😂 Because the process matters, not the work.
At every company I’ve worked at there were basically 3 priority levels - normal, stuff the client says is urgent, and the stuff that’s actually urgent. “We’ll fix it later” is basically for the week in December that everyone’s on vacation and the juniors have nothing to do.
Lol, I love that week. Feels so productive working on low priority shit that’s been around forever
Refactoring that parser you did for the internal DSL in 2011.
deleted by creator
Backlog isn’t sexy. Management wants sexy. Nobody’s boss wants to hear about how the DB schema was improved - they want to see some new, flashy widget.
And the whole product line suffers because of it.
Yet the solution is so simple. Let the them spend 20 – 35 % of their paid time on backlog. Let them refactor the architecture. Let them improve the code base. You know, that thing the Lean book talks about, the part that everyone overlooks, the part so critical yet so often overlooked that others wrote books that ride that one aspect home.
But why do that when instead you can just pretend those issues don’t exist (or simply fail to understand them) and secure a bonus/promotion/personal favour by cutting “unnessecary” labour costs then celebrate by burbling on about how capitalism “maximises efficiency”.
I’m a Senior developer, and I’m still playing the part of the Junior in this meme.
I hate it when people insist on leaving their trash lying around where I work.
Backlogs are great. Sometimes while working on prioritized tasks the depriorized backlog tasks are made irrelevant and thus you never have to do them and you don’t waste effort. Call it strategic deprioritization or perhaps even tactical laziness.
Ummm yeah it will be in “Phase 2” of the project.
My longest lived backlog task is 3 years old
Those are rookie numbers!
Somehow their company is only 2 years old 🤔
I completed a ticket made in 2011 today!
Good for you. My oldest backlog task is from 2012. And that was imported from the previous ticketing system (AKA an Excel Sheet).
We let a bot close our backlogs after 60 days of inactivity. It has a valuable “get it done or let it go” effect.
IMO it’s good to have a “shadow backlog” for stuff like this. Keep the actual backlog for prioritised product work, “ideas” and tech debt can be kept in GitHub Issues or even just a wiki page somewhere.
I have two levels of backlog. The first level is my curated list of tickets that are highly worth doing in the near future and is limited in size. It’s currently larger than I’d like at 30-something (for a team of a little under 10), but I’m trying to get the team to focus on it more after historically neglecting it.
The second level is literally just everything else. Hundreds upon hundreds of tickets, ranging from restructuring unit tests (which will frankly never happen unless the structure of the tests somehow became a major barrier) to cool features that just aren’t important enough yet (or would take too long). Plus all the super low risk bugs, often in edge cases that nobody really cares about yet or aren’t worth the time to fix yet. And then there’s all the automation style tickets about improving the handling of something (commonly edge cases of things already automated for the happy path), but often that something just isn’t common enough to be worth it.
Tickets in the second level sometimes do get done. Usually because some issue becomes more common, enough people ask for it, or we simply finally have time for a new feature (can only do so many of those at a time). A common theme I have is I’ll encounter a problem, file a ticket, then eventually encounter the problem enough times that I go, “fuck it, I’ll do it myself”.
This is the way 🤝
deleted by creator
Because then when someone else suggests the same thing you can say that its in the backlog 😉
ugh Jira. At my first job in 2006 I was the Jira administrator. Every project wanted their own custom fields. We had a Jira project for “infra” problems it had 3 fields yall Title/Description/priority and it worked so well. Moved to a company with a simple ticket system with not much more but the concept of “tags” it was heavily
Ah, but is this a double blocker or a triple blocker?
Our solutions architect is like this. Not because we’re working on anything important at the moment, but because we keep pushing back important upgrades further and further, making each day a more challenging operation to keep our rickety-ass distributed monolith alive.
We were supposed to upgrade from Java 8 on Springboot 2.1 to 17 on Springboot 3. That got wiped off the table because the bosses think shoving our inefficient solution into a cloud product is what will attract customers.
Do we work for the same company lol
Likely not, but I’m happy and sad that this seems to be a common scenario.
deleted by creator
Dump it into ec2-type lol. It’s not a product that can or should be cloud native without becoming a security nest of hornets for customer cybersecurity departments.
Damn bro quite literally same
Except i think some of our spring boot might still be 1.5
Sharpening the résumé as we speak
“I archived them all Padme. They’re gone…every single one of them. And not just the minor tickets.”
But the stories and epics too
In our case, tossing stuff in the backlog to never get done is just part of trying to get through life.
We have an… eccentric colleague who demands the craziest stuff that no one else wants. Now in a sane world, we explain that his requests are either extremely costly for a minor thing no one cares about, or, like 90% of his requests, run explicitly counter to what our customers want even if we could trivially do it. He is not a customer nor is he in contact with customers or marketing or sales, he’s in a different technical team but has an “armchair enthusiast” interest in my teams product.
We used to try to have that discussion to reject items to make it clear they will never ever get worked on. However whenever we did that he would demand hour after hour after hour of meeting to discuss each request that we want to reject and convince us why his requirement is the most awesome thing in the planet, and with enough meetings maybe we’d stop being so clueless and come around to recognize the brilliance.
So now we toss it in the backlog, and there’s always a point of comparison like “Customer giving us $40M asks for feature X”, and he has to rationally accept why X jumps ahead of his backlog items, even if he is displeased. One new project manager made the mistake of trying to close out the backlog items and the meeting invites flew about us daring to ignore his awesome requests.
So we have a chunk of backlog that every one knows will never happen, and in fact if our backlog ever dried up, then we’d have a big problem because then we’d actually have to have that tough conversation about why his ideas are bad. At this point some of his wacky stories have been on the backlog for over five years.
That’s why scrum teams need aggressive POs and scrum masters.
I’m the Sr. Dev in this meme.
I usually just do this when a jr has fallen in love with a piece of work and wants to keep polishing it. They start to confuse “I could do X” with “I should do X”… And confuse “less than perfect but still acceptable” with “bug”.
I tell them to slap it on the backlog and to move on.
We have backlog grooming meetings every few weeks. If they still actually want to do it, we can talk, but like 19 times out of 20 they’ve found a new shiny rock by then anyways, and we’re now in a position where we can both agree it isn’t a good use of our time, and close it out as a “will not do”.
You don’t need aggressive POs or scrum masters to operate as a pragmatic team. I far prefer having a lean overhead. When there are more people shouting directions than people actually coding you’ve got too many cooks.
It’s interesting how people have different interpretations of mwmes. You took it as a reflection of a perfectly normal good thing, while I took it as a perfectly normal bad thing.
Iny experience, “put it on the backlog (and never look at it again)” is the response to someone raising a serious architectural problem.
Yeah exactly. I think you hit the nail on the head with the “(and never look at it again)”.
It’s not explicit in the meme. “Not doing it” and “never look at it” are totally different things… But I think you’ll fill it in based on your personal experience.
I’m sorry your backlog doesn’t get regularly revisited.
If I were you, I’d push for setting aside time to get it under control.
If your backlog is gigantic, I expect there will be pushback just because once the problem gets sufficiently large nobody is brave enough to broach it.
But, you can apply story slicing skills to these kinds of problems too. Break it down into smaller bits with clear and realistic objectives. Setting aside 30 minutes with the goal of, say, picking 5 items on your backlog that you know you won’t ever do because they’re super low value? Pick 5 items and close them off as won’t do. Baby steps.
Currently, I am not living this hell. But I gotta tell you, you are supporting a pipe dream.
Literally, if I cannot describe a direct benefit to the so-called end user it won’t even be looked at. The development and engineering team are unimportant. The first part I was told directly, the second part was implicit.
Most corporate environments use scrum or agile as ceremony - decorations to make everybody think they’re doing something better than what they’re really doing. Then when it fails, they can go back to what they were really doing and claim agile was just a fad.
When there are more people shouting directions than people actually coding you’ve got too many cooks.
Ha ha what about when the shouters:coders ratio hits 10:1?
deleted by creator
No matter how aggressive PO & SM are they don’t get to decide priority.
Yep. Gotta clean out that backlog by deleting the stuff that will never get done.
