Explain Your End-to-End Process for Ranking Competing Backlog Items

Explain how you decide what your team works on next from its product backlog. Take the interviewer through the whole process: where items come from, what you rank them against, how you compare items of different kinds, who weighs in, and when and why the order changes. You may ground the answer in a product you have worked on or in a realistic team you describe. ```hint Map the whole loop Before naming a framework, say what every item is being ranked against, and what happens to the order once it is set: who sees it, and what makes you revisit it. ``` ### Clarifying Questions - Does the backlog hold only new features, or also bugs, technical debt and requests from sales, support or leadership? - Is there an agreed objective for the quarter to rank items against, or is setting that objective part of the task? - How big is the team this backlog feeds, and does it depend on other teams to ship? - How often should the ranking be refreshed: every sprint, every quarter, or only when something changes? ### What a Strong Answer Covers - How new items are captured and made comparable, including the problem each one addresses and the evidence behind it - The objective items are ranked against and how it connects to company strategy - A named, repeatable ranking method, with its inputs explained and its limits acknowledged - How items that do not compete on equal terms are handled, such as severe defects, compliance deadlines, cross-team dependencies and technical debt - How the ranking is agreed with engineering, design and stakeholders, communicated, and revisited ### Follow-up Questions - A senior leader insists on a feature that sits near the bottom of your ranking. What do you do? - How do you weigh technical-debt work whose benefit users never see directly? - How would your process change between a five-person startup and a product area shared by several teams?