FuseBase Demo Organization
Copy to my workspace

T60 Automation build backlog review

Automation build backlog review

An automation team reviewing a build backlog

Cobalt Labs Sprint planning: Fri Sep 25, 2026 1 item failed client validation Client-visible

What Northbeam AI Advisory built for Cobalt Labs this sprint, what needs Anna Kerr's approval and what we propose to pull into the next sprint. Backlog as of Wednesday, Sep 23, 2026.

Work items, Cobalt Labs portal5all statuses, this backlog
Done or accepted2Dependency vulnerability patch, Audit trail export
Awaiting client validation1Truncated sample labels, failed retest
Security items in flight3patch, audit log retention, secrets vault

Sample template: the firm, people, clients and figures are fictional, and the embedded view holds synthetic sample records.

Live example from the Dashboards app, shown with Pinebrook Solar's demo data.

Prioritization rules

RuleDefinitionThis sprint
Security firstUrgent or High priority Security items go before other types at the same priorityDependency vulnerability patch shipped ahead of the audit log retention work
Client-facing bugs before featuresA Bug affecting the client's day-to-day use outranks a new Feature at the same priorityTruncated sample labels outranked the audit trail export, which shipped anyway once ready
Debt needs a named triggerDebt items only enter a sprint when tied to a release risk or a client complaint, not on their ownNo Debt items are in this backlog
Client validation before DoneA build cannot move to Done until the named client owner accepts it, except emergency hotfixesApplies to all three remaining open items

Backlog

Sorted by most recently updated. Card colour follows Type; Priority and Client owner are visible on each card so you can see what needs Anna Kerr's attention without opening it.

Before you share this page with a client

The embedded Delivery table lists work items for every client we build for, not only Cobalt Labs. Before sending this page, switch the embed to a saved view filtered to Cobalt Labs, or share a copy of this page with that filter applied.

Build status this sprint

ItemTypeStatusTechnical ownerValidation result
Dependency vulnerability patchSecurityDoneOwen BrooksAccepted
Audit trail CSV exportFeatureDoneLeo HartAccepted
Truncated sample labelsBugClient validationOwen BrooksFailed
Secrets moved to vaultSecurityCode reviewDan WellsNot tested
Audit log retentionSecurityBacklogLeo HartNot tested
How a build moves, and where a human signs off
flowchart LR
    Backlog --> Ready --> InDev["In development"] --> CodeReview["Code review"]
    CodeReview -->|Tech lead approves| ClientValidation["Client validation"]
    ClientValidation -->|Anna Kerr accepts| Done
    ClientValidation -->|Fails| InDev
    CodeReview -->|Blocked| Blocked
    Blocked -.->|Unblocked| InDev

Human approval points

Two people sign off before anything ships to Cobalt Labs. A tech lead reviews the code before a card can leave Code review. Anna Kerr, the client owner, validates the result in her own environment before a card can move to Done. Security items also need a documented acceptance note, which is why they show a Validation result of Accepted rather than a plain Passed.

Truncated sample labels failed client retest

Barcode labels with sample IDs longer than 12 characters still truncate on Cobalt Labs' older label printer model. Owner: Owen Brooks. Cause under review: a driver setting specific to that printer model, not the label template itself. If not resolved before the next inspection cycle, lab staff will keep hand writing overflow IDs on affected samples.

Next sprint

Proposed for the next sprint
Diagnose the label printer driver setting and retest with Anna Kerr's team
Complete code review on Secrets moved to vault and document the rotation runbook
Pull Audit log retention into Ready once the storage cost approval clears
✓Confirm Anna Kerr's acceptance note is filed for both Done items
How to use this template

Duplicate this page once per client per sprint. Replace these values; if a required value is missing, show Needs review instead of guessing.

VariableMeaningRequired
{{client.name}}Client whose backlog this review coversRequired
{{sprint.review_date}}Date of the sprint planning or review sessionRequired
{{item.status}}Current pipeline status of each work itemRequired
{{item.validation_result}}Client validation result for items not yet DoneRequired when status is Client validation or later
{{client.approver_name}}Named client owner who validates and accepts buildsRequired
{{item.blocker}}What is blocking a Blocked item and who owns clearing itRequired when status is Blocked

Never move a card to Done without the named client approver's acceptance recorded, except a documented emergency hotfix.