Know what is in scope, what changed and what is built.
The scope baseline records what the programme agreed to deliver. Every change request carries its budget and timeline impact and an approver, and an approved change can create its cost entry in the budget.
Build objects move through six stages from functional specification to user acceptance test, with their owners and release references. The register uses the platform's words: WRICEF objects and transports on SAP, CEMLIs on Oracle E-Business Suite, user stories and deployments on Salesforce, stories and update sets on ServiceNow, customisations on NetSuite.
The scope baseline, change requests and every build object from design to UAT.
In the app, this module is these workspace tabs: Scope, Build objects.
What the module covers
A baseline you can point to
Scope items with their status, kept apart from change requests and from archived items.
Change requests with consequences
Each request states its budget and timeline impact and who approves it. Approving a change offers to record its cost against the budget.
Build objects by type
Six types, in the platform's own names: workflows, reports, interfaces, conversions, enhancements and forms on SAP; flows, Apex and data loads on Salesforce; SuiteScripts and saved searches on NetSuite. Each has its complexity and its functional and technical owners.
Six stages to done
Functional spec, technical spec, development, unit test, integration test and UAT, with a release reference for development, test and production. Switch between a table and a board.
How a programme uses it
Agree the baseline
Record the scope items the programme committed to at the end of design.
Assess each change
Raise a change request with its impact on budget and dates, and route it to the approver.
Move objects through the stages
Developers and leads update each build object as it passes a stage, so the remaining work is a count rather than a guess.
Where it helps most
System integrators
Show the client the stage of every build object instead of a percentage on a slide.
Capexo for system integratorsClient-side PMOs
Hold every change request to a written impact before it reaches the change board.
Capexo for client-side PMOs
Scope and build: common questions
Our platform does not call them WRICEF. Does that matter?
No. The register takes the words of the project's platform: WRICEF objects on SAP S/4HANA, CEMLIs on Oracle E-Business Suite, extensions and integrations on Oracle Fusion Cloud, integrations, reports and business processes on Workday, user stories on Salesforce, stories on ServiceNow and customisations on NetSuite. The six types and stages underneath are the same.
Can approved changes update the budget?
Yes. When a change request is approved, Capexo offers to create the matching cost entry, so the budget reflects the decision.
See this module with your programme in mind.
Tell us which application you are implementing and where the programme is today. We will show you how this module would hold your work.