Build objects are the things a programme designs, builds and tests on top of the standard software: workflows, reports, interfaces, conversions, extensions and forms. The build register tracks each one from functional specification to user acceptance. It sits under the Scope entry and is on every plan.
Your platform's name for them
The register, its tab and its forms use the words of the project's platform. On SAP S/4HANA it is the WRICEF registry: Workflows, Reports, Interfaces, Conversions, Enhancements and Forms. Elsewhere the register takes the platform's term:
- Oracle E-Business Suite: CEMLIs (configurations, extensions, modifications, localisations and integrations).
- Oracle Fusion Cloud and Infor CloudSuite: Extensions and integrations.
- Workday: Integrations, reports and business processes.
- Salesforce: User stories, with types such as Flows, Apex and components, and Data loads.
- ServiceNow: Stories, with types such as Flows and Import sets.
- Oracle NetSuite: Customisations, with types such as SuiteScripts, Saved searches and CSV imports.
- Microsoft Dynamics 365: Gaps and extensions.
- Other software: Build items.
Underneath, every platform has the same six object types and the same six stages, so the counts, the board and the test coverage work the same way. This article uses "object" for all of them.
How to add an object
- Open the register
In the project, select Scope, then the build tab: WRICEF on SAP, or your platform's term, such as User stories or CEMLIs.
- Start one
Select Create object on SAP, or the button that names your platform's term, such as Add a user story.
- Identity
Type the Title. Choose the Object type, the Workstream, the Complexity and the Priority. On SAP the types show their WRICEF letter (W: Workflow, R: Report, I: Interface, C: Conversion, E: Enhancement, F: Form). The Workstream list follows the platform: SAP modules then business streams on SAP S/4HANA, business streams on other platforms.
- Ownership
Add the Functional owner and Technical owner, and a Linked task from the plan if there is one.
- Save
Select the create button. The Object ID is created for you, with a code from your platform's term, such as RICEFW on SAP or US on Salesforce.
How to move an object through its lifecycle
- Open it
Select its row in the table or its card on the board.
- Set each stage
Under "Lifecycle status", set FS (Functional spec), TS (Technical spec), Dev (Development), UT (Unit test), IT (Integration test) and UAT (User acceptance).
- Record the release references
Add the reference for development, test and production. The section takes the platform's name: Transport requests on SAP, Deployments on Salesforce and NetSuite, Update sets on ServiceNow, Tenant migrations on Workday, Configuration packages on Oracle Fusion Cloud.
- Save
Select Save changes.
Each stage can be Not started, In progress, Reviewed, Code review, Approved, Completed, Passed or Failed. An object sits at the first stage that is not finished. FS, TS and Dev are finished when Approved or Completed. UT, IT and UAT are finished when Passed or Completed. When all six are finished, the object is Completed.
Reading the register
- The cards at the top count the total, Completed, In dev and Failed tests (any unit, integration or UAT failure).
- Search by object ID or title, and filter by type and workstream.
- Table shows Object ID, Title and type, Functional owner, FS, TS, Status, Complexity and Priority, a page at a time.
- Kanban shows one column per stage: FS, TS, Dev, UT, IT, UAT and Done.
- "By complexity" at the bottom shows how many objects are high, medium and low.
- Export downloads the filtered list as an Excel file, with every stage.
Good to know
- The FS and TS columns show the linked specification's status and a document icon. See Specifications for build objects.
- Once a specification is linked, its FS or TS stage follows the document and cannot be set by hand.
- Dragging cards between columns is not supported. Change the stage in the object's form.
- The Scope Agent can propose build objects from a statement of work.
- Build objects are one of the data sources for dashboards.
- If you cannot edit objects, the form opens read only and says so.
Who can do this
Admins, project managers, functional leads and technical leads can create and edit objects. Only admins and project managers can delete them. Consultants can link specifications to objects they own. Everyone on the project can view the register.