Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

11
  • 23
    If you delete these tickets in your backlog, does that mean that they are not tracked/documented at all? Commented Jun 29, 2020 at 16:48
  • 80
    This strikes me as removing the wet floor sign so that there won't be any more wet floor. Commented Jun 29, 2020 at 18:56
  • 5
    How expensive are these tickets to make and how likely is it that you create a duplicate by mistake? E.g., are these made by an automated code scanner like SonarQube or are people manually making these based on issues they know about or something else entirely? Commented Jun 29, 2020 at 19:52
  • 6
    Maybe if you start describing the backlog to your PO as "thick and lustrous", it will become more acceptable. Commented Jun 30, 2020 at 12:07
  • 5
    Do you have another column you can move them to, just to make PO happier with the backlog? Maybe create a "Wishlist" column, or simply a "Tech Debt" column. Personally, I think your PO doesn't understand the purpose of Backlog. It's the stuff you don't have a specific timeframe for. It can be very large, if you need it to be. Commented Jun 30, 2020 at 19:27