1. Upload Usecase Diagram
Click to upload or drag and drop
PNG, JPG, GIF, PDF (max. 10MB)
Avoid content with personal or sensitive information.
2. AI Analysis & Generation
Context Insights
Click to upload or drag and drop
SVG, PNG, JPG (max. 5MB)
Preview Test Cases Generated (0)
Under construction
We're building this page right now.
Test planning and management workflows are on the way — check back soon.
Oops!
Please select a project to view work items.
Pick a project from the dropdown above, then choose an iteration to load the sprint backlog.
Azure DevOps project dna-mops-QC — repositories: dna-aita, dna-automation-test, dna-security-monitor, dna-tamp, dna-tdbank. Cycle time is measured from PR open to merge.
AI Configuration
Choose the AI provider and model used for test case generation.
Swimlane view — Pairing Model + Injection Model, with Leave / Boost / Survival exceptions
Reading the percentages → Every % below describes a QC's capacity (share of their own working time), not the project's total workload. Example: "Shadow 50% on this project" means the Shadow QC spends half of their working time here — it does not mean half the project workload is covered.
The default state. Async-first — no extra meetings beyond sprint ceremonies. During pilot weeks, QC Lead coaches and observes. After pilot, QC Lead only steps in when a QC pair asks for help; the model runs by itself.
Capacity Allocation
Anchor A · Shadow B
Anchor B · Shadow A
Swimlane Diagram
How to read the diagram below: each horizontal row is one role; each rounded box is one action that role performs. Columns group into three test phases — Test Planning → Test Execution → Test Closure — shown as headers above the lanes. Start at the black dot on the left and follow the arrows right; the cycle ends at the donut dot on the right. Dashed-outline boxes mark pilot-phase only activities that go away after the pilot.
Optional, not a flow step · At sprint end, each QC may also spend a few minutes updating the project README with new system changes, gotchas, and test-scope notes (~15 min Anchor, ~10 min Shadow). This is encouraged for knowledge continuity but it's not required and not shown as a box in the diagram.
| Ceremony | When | Anchor QC | Shadow QC — pilot phase | Shadow QC — post-pilot |
|---|---|---|---|---|
| Grooming (optional · per project) | Sprint start | Required | Required (learn priority and refinement) | Optional |
| Sprint Planning | Sprint start | Required | Required (learn scope) | Required (partial attendance) |
| Daily Standup | Daily | Required | 1–2 per sprint | Optional |
| Sprint Review / Demo | Sprint end | Required | Skip | Required (partial attendance) to demo the feature(s) he tested in Sprint |
| Sprint Retrospective | Sprint end | Required | Skip | Optional |
Temporary support for a critical release. Start this when: PM flags an upcoming release (1 sprint ahead) OR QC Lead spots it on the priority matrix. Max 1–4 weeks. A clear end date is required before starting. The higher-priority project comes first.
Capacity Allocation
Anchor A · Boost focus
Shadow A · Boost help
Swimlane Diagram
How to read the diagram below: each horizontal row is one role; each rounded box is one action that role performs. Columns group into three boost phases — Boost Activation → Boost Execution → Boost Closure — shown as headers above the lanes. Start at the black dot on the left and follow the arrows right; the cycle ends at the donut dot on the right.
Multi-project crisis intervention. Start this when there are 2+ critical projects over capacity in the same window. Injection QC acts as a temporary shadow — not a permanent role. An end date is required.
Capacity Allocation
Anchor A · Crisis owner
Anchor B · Shadow recalled
Temp shadow on A
Swimlane Diagram
How to read the diagram below: each horizontal row is one role; each rounded box is one action that role performs. Columns group into three survival phases — Survival Activation → Survival Execution → Survival Closure — shown as headers above the lanes. Start at the black dot on the left and follow the arrows right; the cycle ends at the donut dot on the right.
Skill-based, task-scoped help. Each task = 2–8h. Anchor QC owns the result. Injection QC only owns the task output and leaves when done. A request needs 3 fields: skill needed / task and expected output / deadline.
Capacity Allocation
Anchor A · Shadow B
Anchor B · Shadow A
Task-based on A or B
Swimlane Diagram
How to read the diagram below: each horizontal row is one role; each rounded box is one action that role performs. Columns group into three phases — Injection Request → Injection Execution → Injection Closure — shown as headers above the lanes. Start at the black dot on the left and follow the arrows right; the cycle ends at the donut dot on the right.
Anchor-on-leave coverage protocol. When a QC is on leave, every project where they are Anchor follows this protocol. If they are also Shadow on another project, the Anchor there simply uses 100% of their own capacity alone (handled by the normal Pairing Model).
Capacity Allocation
Anchor A · On leave
Anchor B · Shadow A
Temp shadow on A
Swimlane Diagram
How to read the diagram below: each horizontal row is one role; each rounded box is one action that role performs. Columns group into three phases — Pre-leave Handoff → During Leave → On Return — shown as headers above the lanes. Start at the black dot on the left and follow the arrows right; the cycle ends at the donut dot on the right.
Current workload across the QC roster. Period defaults to this calendar month.
Forward-looking capacity per QC, based on historical throughput. Workload data isn't shown because future sprints don't exist in ADO yet.