Backlog Refinement for Automation: Routing Qualified Work Between Citizen Developers and Expert Teams

Backlog refinement, in the Problem-First methodology, is the final qualification gate: once a candidate has passed problem definition, root-cause analysis, and pattern matching, refinement decides whether it should be built by a trained business analyst or power user with a low-code tool, or whether it genuinely requires specialist developers - RPA architects, AI engineers, integration specialists. Getting this routing wrong in either direction is costly, which is why it deserves the same deliberate qualification as the earlier gates rather than being left to whichever team happens to have capacity that week.

The Cost of Getting Routing Wrong

• Sending specialist-scope work to a citizen developer produces a fragile automation that breaks in production - often on exactly the exception paths a citizen developer wasn't equipped to anticipate - and damages business confidence in the whole program when it fails.
• Sending citizen-developer-scope work to an expert team wastes an organization's most expensive, most constrained capacity on routine configuration work that a trained power user could have handled, and creates unnecessary dependency on a scarce resource.
• Either mistake distorts a CoE's throughput numbers - specialist teams look slower than they are because they're absorbing simple work; citizen-developer queues look riskier than they should because they're absorbing complex work.

What Signals Point to Citizen-Developer Scope?

• Low-code BPM orchestration with a small number of well-defined steps and approval paths.
• Configuration within an already-approved low-code platform (e.g., Power Platform) rather than custom code or novel integration work.
• Few or well-documented exception paths, with clear escalation rules that don't require deep system expertise to implement.
• A process owner who can articulate the rules completely and consistently - ambiguity in the rules themselves is a signal to route toward a more experienced builder, regardless of technical complexity.

What Signals Point to Expert-Team Scope?

• Custom API integration work, especially against systems without well-documented interfaces.
• High exception density or judgment-heavy branches that require careful design, not just configuration.
• Anything touching sensitive data, regulated processes, or systems where an error carries meaningful compliance or financial risk.
• Novel AI agent development rather than assembly from existing, well-understood components.

Refinement Feeds Directly Into Documentation

The refinement decision isn't just a routing label - it shapes which documents a candidate needs and who receives them. A citizen-developer-scope candidate may need only a lightweight PDD and configuration notes; an expert-scope candidate typically generates the full SDD stack (L1 through L3) because it requires architectural review and a detailed implementation guide. See Automating PDD/SDD Generation for how that documentation is produced automatically once refinement has determined the scope.

Frequently Asked Questions