What are the characteristics of a good Product Backlog item?

Short answer: A well-formed backlog item (often a User Story) should be: ✅ INVEST: Independent – Can be developed separately Negotiable – Not a fixed contract Valuable – Delivers user or business value Estimable – Team can estimate its size Small – Can be completed within a Sprint Testable – Has clear acceptance criteria Example: Poor: “Fix bugs” Better: “As a user, I want error messages when login fails, so I know why I can’t…

Real-world example (ShopNest)

“Add UPI” is a story with acceptance criteria. Points reflect effort/risk, not days on a calendar.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.