Web应用持续开发中，如何在VSTS Kanban整合测试团队工作？

Great question! Your approach of running parallel Kanban workflows—where the dev team works on the current iteration while the test team handles items from the previous iteration—is a really solid fit for aligning continuous development and testing. Let’s break down how to make this work in Azure DevOps (formerly VSTS), including whether separate teams are necessary.

Option 1: Separate Dev and Test Teams (Ideal for Larger, Distinct Teams) #

If your dev and test teams have unique workflows, permission needs, or reporting requirements, setting up separate teams is a clean, scalable solution:

• Create two dedicated teams in your VSTS project: Head to Project Settings > Teams > New Team, and set up "Development Team" and "Testing Team".
• Configure each team’s Kanban board:
  • For the Dev Team: Map the board to the current iteration, with columns like Backlog Item → In Development → Ready for Test → Done. Set WIP limits to keep development focused and avoid bottlenecks.
  • For the Test Team: Configure their board to pull items from the previous iteration marked as Ready for Test. Use testing-specific columns like Ready for Test → In Testing → Test Passed → Blocked → Ready for Release.
• Automate work item handoff: Use Azure DevOps rules to streamline the transition:
  • When a dev work item is marked Ready for Test, automatically move it to the Test Team’s backlog.
  • Link the original dev work item to a new test task (if your team splits testing into dedicated tasks).
  • Update the iteration path to the previous sprint, or use a filter to show only prior-iteration items on the test board.
• Pros: Full separation of workflows, permissions, and reporting. Each team can customize their board without impacting the other.
• Cons: Requires extra setup for cross-team tracking, and adds minor overhead for syncing between teams.

Option 2: Single Team with Dual Kanban Boards (Best for Smaller, Collaborative Teams) #

If your teams work closely and share a single backlog, you can skip separate teams and create two boards under one team:

• Create a second Kanban board: In your existing team’s settings, go to Boards > Boards > Create Board. Name it something clear like Test Board (Previous Iteration).
• Filter the test board dynamically: Edit the board’s query to show only work items where:
  • Iteration Path equals @CurrentIteration - 1 (this relative filter automatically pulls items from the prior sprint).
  • State is Ready for Test (or whatever your team uses to mark items ready for testing).
• Customize columns for each board: Keep your main dev board focused on current iteration development states, and the test board focused on testing-specific states.
• Pros: No extra team setup, work items stay in a single backlog, and cross-team sync is simpler.
• Cons: Less granular permission control (all team members can see both boards), so you’ll need to ensure everyone understands which board to use for which tasks.

Extra Tips to Make This Work Smoothly #

• Sync during iteration planning: In sprint planning, have the dev team outline current iteration work, while the test team reviews the previous iteration’s items to prioritize testing tasks.
• Add automation alerts: Set up notifications or auto-assignments when items move to Ready for Test to ensure the test team gets notified immediately.
• Build a shared dashboard: Create a team dashboard with widgets for both the dev current iteration progress and test previous iteration status, so everyone can see the big picture at a glance.
• Define clear state rules: Make sure your team agrees on exactly what each state means (e.g., Ready for Test = code reviewed, unit tests pass, documentation updated) to avoid handoff delays.

内容的提问来源于stack exchange，提问作者fbonds66