What is a backlog?

Backlog is an ordered list of tasks that need to be completed to achieve the project goal or develop the product.

There are two main types of backlog in Agile methodologies:

• Product Backlog: A dynamic, constantly updated list of functional and non-functional requirements for the product, defect fixes, improvements, and research work. It reflects the product vision and is managed by the product owner. Backlog items are prioritized based on value, risk, dependencies, and other factors. The most priority items are at the top of the list and ready for execution.
• Sprint Backlog: A subset of items from the product backlog selected by the development team to be completed during a single sprint. It is detailed by the team and reflects the work plan for the sprint. The sprint backlog is owned by the team and remains unchanged during the sprint, except when the team decides to add or remove tasks to achieve the sprint goal.

Key characteristics of the backlog:

• Dynamism: The backlog constantly changes: new items are added, existing ones are modified, details are clarified, and priorities are reviewed.
• Prioritization: Backlog items are ordered by their importance and value to users and the business.
• Detailing: Items at the top of the backlog are more detailed and ready for execution, while lower items may be more high-level.
• Transparency: Accessible to all team members and stakeholders.
• Management: Usually managed by the product owner, who is responsible for its content and prioritization.

In QA work, the backlog is important for:

• Understanding requirements and functionality to be tested.
• Planning testing activities.
• Tracking testing-related tasks (e.g., writing test cases, conducting exploratory testing).
• Managing found defects (they are added to the backlog for fixing and retesting).