FORGE SWAGE

Requirements structuring tool

FORGE SWAGE helps teams turn agreed initiative intent into structured requirements, making priorities, acceptance criteria, gaps and contradictions easier to review before design and delivery planning proceed.

Business analysts, project managers, programme managers, product owners, PMO leads, solution leads and delivery governance teams

PRINCE2, PM², MSP, Agile, Waterfall, Hybrid

Turn initiative intent into structured requirements with priorities, acceptance criteria, gaps, contradictions and traceability signals.

FORGE SWAGE is the requirements structuring component of the FORGE Logic™ ecosystem.

It is used once the initiative has moved beyond initial governance shaping and needs clearer requirements before solution design and delivery planning proceed.

SWAGE helps turn business intent, scope, stakeholder needs and governance context into structured requirements. Its purpose is not simply to list requirements, but to make them easier to prioritise, challenge, trace and use as evidence for design, planning and governance decisions.

Requirements often emerge from workshops, emails, legacy documents and stakeholder preferences without being shaped into a clear, challengeable structure.

That creates ambiguity. Priorities may be unclear, acceptance criteria may be missing, contradictions may be hidden and delivery teams may move into design or build before the requirement basis is strong enough.

SWAGE helps create a more disciplined requirements foundation.

SWAGE structures requirements from available initiative evidence.

It helps organise requirement statements, priorities, acceptance criteria, dependencies, conflicts, gaps and unresolved questions. It can draw on BILLET outputs, ASSAY findings, stakeholder inputs and other source material where available.

The aim is to make requirements more usable for design, planning, governance review and future traceability.

SWAGE produces a structured requirements register or requirements evidence base.

The output may include prioritised requirements, acceptance criteria, open questions, contradictions, dependencies, traceability signals and observations about requirement quality.

That evidence can feed PATTERN, ANVIL, TEMPER and the wider FORGE delivery intelligence layer.