A prioritized list of features, user stories, or tasks that need to be completed in a project, maintained and ordered by business value or importance. It serves as the single source of requirements and the input for sprint planning in agile methodologies.
Originally referred to a large log placed at the back of a fireplace to provide sustained heat. First used in business contexts in the 1930s to describe accumulated orders or pending work, then adopted by software development to describe prioritized lists of features or requirements.
A healthy backlog is like a good investment portfolio - constantly rebalanced and pruned! The biggest mistake teams make is treating their backlog like a wish list instead of a strategic tool. The most valuable items should be at the top, and everything else should be regularly questioned: do we still need this, or are we just hoarding requirements?
Complete word intelligence in one call. Free tier — 50 lookups/day.