Capex Projects Will Be Defined As Epics The Epic Name Will Be The Project Name As Per The Crb Sheet

Capex Projects will be defined as Epics. The Epic name will be the project name as per the crb sheet hyphenated with the project code from Caseport, if it is sbc approved. SBAs must create an epic hypothesis statement for each of the project they are working on from their area. TPM will update the description within the EPIC along with the priority, risk, Business value, start and target dates in consultation with the SBA. The status, area and iteration of epics will be updated by the TPM in consultation with the SBA. The SBAs will attach the epic hypothesis, rfp and requirements document to the EPIC. Milestones until contract will be added as Features. SBC, RFP, DBC and Contracts will be added as features hyphenated by the Project name. During DBC and implementation, if the SBA identifies any interfaces or enhancements which needs to be tracked internally, it must be created as a feature. The feature will be supported by BRDs. Milestone document preparation, review, submission, and approvals will be created as user stories. For enhancements and interfaces, the features must be broken down in to user stories which can be delivered within 1 sprint. The SBA must ensure that user stories are updated with description, acceptance criteria and priority. For development activities, tasks must be created within the user story as following. Requirement Walkthrough, Development, Testing, UAT sign-off and Production CR. The requirement walkthrough status will be updated by the SBA once the walkthrough is provided to Dev team. The dev team will update the development task. The SBA will update the Testing task. The Project manager will update the UAT and Production

15.07.2025 12:03