Backlog Introduction

Backlog is like a team's to-do list—the "headquarters" for all work. It helps teams:

• 📋 Track all requirements and tasks (feature development, bug fixes, etc.)
• 🎯 Clearly identify immediate priorities
• 🔄 Flexibly adjust plans to adapt to changes

With AngusTester, you can manage team tasks as efficiently as a shopping list!

What is Backlog? The Team's "Task Inventory"

Think of Backlog as your personal task manager:

• Smart Notebook: Records all pending tasks
• Priority Sorter: Helps focus on the most critical work
• Planning Assistant: Aids the team in scheduling each iteration

Real-World Example:
An e-commerce team maintained their Backlog in AngusTester:

• Tracked 158 feature requests (e.g., "Shopping Cart Save Function")
• Selected 12 high-priority tasks for the current month's iteration
• Successfully delivered core features in two weeks, boosting user satisfaction by 40%

Two Types of Backlogs

Backlogs are categorized by time horizon, much like managing household tasks:

Comparison	Product Backlog	Iteration Backlog
Purpose	Long-term task repository	Short-term execution list
Content	All requirements/tasks/bugs	Curated tasks for the current cycle
Update Frequency	New items added anytime	Updated per iteration (1-4 weeks)
Use Cases	• Collecting market needs • Product roadmap planning	• Scheduling current work • Tracking daily progress

Six Task Types in Backlog

AngusTester's Backlog supports six task types, covering all team workflows:

1. Requirements (Customer Wishlist)

• What: Features customers want (e.g., "Users want faster app loading")
• Example:

  [High Priority] Search Response Optimization  
  - Goal: Load search results in <1 second  
  - Value: Increase user retention by 15%

2. Stories (User-Centric Descriptions)

• Feature: Written in "user story" format
• Template:

  As a [user role],  
  I want [specific feature],  
  So that [benefit].

• Example:

  As a shopping app user,
  I want to save frequently used shipping addresses,
  So I can select them quickly during checkout.

3. Tasks (Actionable Items)

• Feature: Assignable to individuals
• Example:
  • [Frontend] Design address management UI
  • [Backend] Develop address storage API

4. Bugs (Issue Tracking)

• Recording: Auto-captured or manually logged
• Key Fields:

5. API Tests (System Connection Checks)

• Focus: Ensuring APIs "communicate" correctly
• Example: Validate payment API stability under concurrent requests

6. Scenario Tests (End-to-End Validation)

• Feature: Simulates real user journeys
• Example:
  Test the full flow: "Product browsing → Cart → Checkout → Review"

AngusTester Tip: Use labels like #optimization or #hotfix for categorization

Backlog Maintenance Guide

Keeping your Backlog effective is like tending a garden:

3 Weekly Must-Dos

1. Add New Tasks
   • Log customer feedback immediately
   • AngusTester supports auto-creation via email/DingTalk
2. Update Priorities
   • Team review every Monday morning
   • Drag-and-drop sorting in AngusTester
3. Remove Obsolete Items
   • Clear outdated tasks during monthly retrospectives
   • Archive completed items to free up space

Iteration Planning Steps

Best Practice: Set up auto-reminders in AngusTester to ensure regular Backlog updates (TODO).

Backlog Key Features

Feature	Icon	Description	Use Case
Smart Sorting	📊	Auto-prioritizes based on value/effort	Quick decisions for 50+ tasks
Cross-Project View (TODO)	🔍	Consolidated Backlog visibility	Management oversight
Dependency Map	⛓️	Visualizes task relationships	Prevents delays from blockers
Progress Forecast	📈	Predicts completion based on historical velocity	Setting client expectations

Backlog Field Details

See Task Introduction → Field Information.