Skip to main content
Share Your Experience: Take the 2024 Developer Survey
74 votes

Should non-priority technical debt tickets be pruned from backlog?

You are considering deleting the records of genuine problems with the codebase because the product owner wants a shorter backlog? For me, the only reason to delete (close) an item in the backlog is ...
Dan Saunders's user avatar
36 votes

Should non-priority technical debt tickets be pruned from backlog?

I agree with Dan Saunders's answer, but I'm going to go one step further. I agree that the only reason to close a request for a new feature or a modification to an existing feature is if the change ...
Thomas Owens's user avatar
  • 82.8k
10 votes
Accepted

Should non-priority technical debt tickets be pruned from backlog?

I would say that there isn't a single best answer for this problem. You've got a few overall strategies, you would probably be best doing all of them. But the information should never be deleted, but ...
Mattisdada's user avatar
8 votes

Is there a recommended format for writing a technical debt story?

The roadblock you're running into is there by design, and you're running into it for the correct reasons. User stories are things the user cares about. That's why it's written from the point of view ...
Flater's user avatar
  • 51.7k
7 votes
Accepted

Product Backlog vs. huge features

My personal perspective from having worked in agile for a few years, is that you really shouldn't fear a large backlog (to a point). If you are writing self-contained user stories, each of which is ...
Ben's user avatar
  • 349
6 votes
Accepted

Correct way to break feature into user stories

A more "vertical" approach is the common guidance on splitting stories. What it reinforces is: A multi-functional team capable of working on the whole product Building a dirt road and then adding ...
Berin Loritsch's user avatar
6 votes

Should non-priority technical debt tickets be pruned from backlog?

Does your bug tracking software allow you to mark a bug according to its priority? If so, then you can ask your boss if it's OK to create a "lean and healthy backlog" by simply viewing the ...
Ben Crowell's user avatar
6 votes

Should non-priority technical debt tickets be pruned from backlog?

Yes, you likely should prune your backlog of un-prioritized technical debt, as you won't fix it (similar to YAGNI). Think of fixing technical debt as an investment opportunity. Something developers ...
dlasalle's user avatar
  • 842
5 votes

User stories with multiple users/roles

You seem to have already answered your own question: Scenario: - There are two external user types - sellers and buyers. From this, I infer that you have other roles that are considered internal (...
Flater's user avatar
  • 51.7k
5 votes

In scrum, if tasks are estimated in hours, how to avoid assigning the task in sprint planning?

The statements that you claim should be true in Scrum aren't necessarily true in Scrum, according to the Scrum Guide. It is not true, according to Scrum, that you should be estimating user stories in ...
Thomas Owens's user avatar
  • 82.8k
5 votes
Accepted

Sprint planning: who decides which items of the Product backlog to be included into the Sprint backlog?

The product owner knows what is important, and prioritizes the backlog. The team knows what is possible, and can estimate backlog items. Together, they can create a sprint goal that is both relevant ...
amon's user avatar
  • 134k
5 votes

Are accomplished requirements still part of the Product Backlog?

If you read a bit farther in the Scrum Guide page you linked, it also says: The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to ...
Robert Harvey's user avatar
5 votes
Accepted

When epics are used, should all user stories belong to an epic?

What do you mean by "Epic"? It's not a well-defined term or concept. Sometimes, the term "Epic" is used as a short, simple way of saying "unrefined story". When you have ...
Thomas Owens's user avatar
  • 82.8k
4 votes
Accepted

Are accomplished requirements still part of the Product Backlog?

A backlog, by definition, is "an accumulation or buildup, especially of unfilled orders or unfinished work". A Product Backlog is only the work that is known to be remaining on the product, just like ...
Thomas Owens's user avatar
  • 82.8k
4 votes

PBI vs User Story

All of the above answers fail to reference the authoritative source document for the Scrum framework: The Scrum Guide. Product Backlog There is a section describing the Product Backlog and the items, ...
Alan Larimer's user avatar
4 votes

Correct way to break feature into user stories

Here's the trouble I have with the user stories you list: it seems like there is an exact implementation in mind and someone is trying to write user stories around that. That isn't the point or ...
Daniel's user avatar
  • 2,041
4 votes

Correct way to break feature into user stories

I don't agree that the stories you presented are sliced horizontally. With horizontal slicing, you see stories that are targeted at different disciplines within the team or stories that don't offer ...
Bart van Ingen Schenau's user avatar
4 votes

Sprint planning: who decides which items of the Product backlog to be included into the Sprint backlog?

This is a bit confusing, but in the Scrum Guide, there are two key responsibilities split between the Dev Team and Product Owner: 1) Product Owner owns the priority in the backlog. 2) Only the team ...
Daniel's user avatar
  • 2,041
4 votes
Accepted

How to manage library(ies) used by multiple projects?

Based on your description, the common library appears to be a collection of business functionality and utilities common to many of your projects. Regressions caused by one product's modifications may ...
metacubed's user avatar
  • 966
4 votes

Is there a recommended format for writing a technical debt story?

"Scrum Framework only describes what needs to be done, but does not enforce how it needs to be done." "User Stories are a great technique for capturing functional requirements in a ‘good enough for ...
kriscorbus's user avatar
4 votes

Should non-priority technical debt tickets be pruned from backlog?

I expected to see someone reference Joel Spolsky's old article. Since you say that these tickets haven't been prioritized it sounds like no one's looking at them, and in that case it's ok, leave them, ...
IceGlasses's user avatar
3 votes

User stories with multiple users/roles

How you split the story depends on the sizing of the story. I see two possible options. The first option, and where I would start, would be to write your story in a way that encompasses both user ...
Thomas Owens's user avatar
  • 82.8k
3 votes

Does the Product Backlog just consists out of User Stories in Agile Development?

The product backlog is simply list of user stories.
Rumen Georgiev's user avatar
3 votes

Product Backlog vs. huge features

tl;dr Should I write these features on a product backlog and order them according to their priorities or they will confuse my plan so they may deviate my product from what I expect? Do not spend ...
Alan Larimer's user avatar
3 votes
Accepted

How track backlog items origin using scrum?

Scrum says nothing about how to track where backlog items come from. In fact, relatively little is said in the Scrum Guide as to what information should be included in a Product Backlog Item and how ...
Thomas Owens's user avatar
  • 82.8k
3 votes

Should non-priority technical debt tickets be pruned from backlog?

It makes no sense to have a "lean and healthy" backlog for a codebase which isn't equally "lean and healthy". The backlog's job is to reflect the state of what must/could/should/...
Kafein's user avatar
  • 436
3 votes
Accepted

Common details in the acceptance criteria of related user stories

"Student must be logged to the system" on its own is a bit confusing in the context of either the fee story or the login story - is it a prerequisite or is it an outcome? For the login story,...
casablanca's user avatar
  • 4,964
2 votes

Agile User Stories for Deep Thought Machine

This generalising, abstract thing is distracting you. Agile will teach you very quickly to become pragmatic. There is more to be learnt by taking on problems in small parts that are highly specific. ...
cottsak's user avatar
  • 216
2 votes

Agile User Stories for Deep Thought Machine

Since there is no such thing as a "true agilist", I'll make up my own definition. A "true agilist" knows that a larger story is composed of smaller stories. Agile practices teach us to relate these ...
Bryan Oakley's user avatar
  • 25.3k
2 votes

PBI vs User Story

There is a common misunderstanding that only user stories are allowed in a Product Backlog. By contrast, Scrum is neutral on requirement techniques. As the Scrum Primer states, Product Backlog ...
user666's user avatar
  • 143

Only top scored, non community-wiki answers of a minimum length are eligible