STAGES DISCOVERY REQUIREMENTS DESIGN BUILD AND TEST (SPRINT DEVELOPMENT) CUTOVER AND TRANSITION TO OPERATIONS
STEPS INTAKE TRIAGE ANALYSIS VALIDATE SPRINT PLANNING READY / TO DO WORK IN PROGRESS READY FOR TESTING TESTING READY FOR PROD CUTOVER COMPLETE
Project born activities: - Request and incident - Initial Review and - Story is reviewed for Backlog Grooming - Assignment of stories to - Solution is developed - Story is assigned to a - External testing - Review of all story Deployment to PROD - Production validation
- Project items queue management Confirmation of Request completeness and sprints - Customizations are tester coordinated by a BA technical build details (smoke testin, visual spot
- Review stories and - Facilitate production
- Roadmap - Assignment of tickets / - Draft story is updated accuracy (in Draft Status) - Assignment of stories to evaluated for immediate - External story testers - All testing is executed with development team check, etc.)
verify requirements with cutover activities
- Internal Scope emails to analysts for with details - Finalize request details developers based on and long term impacts to are identified and as per QA scripts or - Architectural review and - Update of original
BA and technical teams
Gathering information to review - Define the acceptance resource capacity platform integrations notified of testing need directions in the story alignment (epic review, requestor tickets ( update
- Alignment with existing - If requirements are
define the who, what, criteria for the user story, and QA scripts platform and product request, incident, idea,
- Define resolution if requirements and epics complete story status is - Technical team to - External system - All testing results,
ACTIVITIES when, and why that will be tested and alignment, project and etc.)
possible updated to Ready confirm solution design integration unit testing is - External IT teams are internal or external,
reviewed for accuracy ops scope alignment)
*Request sources: - Reassignment to ops and completeness. Sprint Planning and approach (engage in completed by technical coordinated with system Successful or failed, are - Contact the original
- Incidents teams (TCS, SN, etc.) - Architectural team discussions as team integration testing to be outlined clearly in - Validation of rollback or requestor if appropriate
- Enhancement requests - Technical scoping the story's work notes failed production plan with the update of the
- Review for duplication assessment to validate required) - Peer review and unit
- Management emails exercise to determine the (include screenshots and deployment's success
of effort technical aspects level of effort required testing is assigned - Final code review
- Org. unit leaders - Story status updated to details, ticket info if
- Other - Communication to - Selected stories are are - QA test scripts are applicable) - Update set contents
request originator Backlog assigned to a release developed as required review
STAGE GATING
- Update of requirements - Story is updated with - Story is evaluated by - Story is reviewed by - Acceptance Criteria - Solution approach - Passed peer review - Story assigned to an - Story passes internal - Story reviewed for - Actual production - All related tickets must
into the Digital Identity requirements and Architect Lead BA to confirm defined defined - Passed all unit testing internal tester and external testing architectural alignment cutover completed be updated and
requirements matrix stakeholder expectations - ServiceNow story completeness - Story is valiated by the - Finalized architectural - Testing requirements - Test results are clearly - Code review complete - Change notifications confirmed to be resolved
REQUIREMENTS - QA scripts complete, or fulfilled
- Document captured - Link story to applicable created in Draft - Story and tehcnical technical team alignment (e.g. longevity with the acceptance are advised to the noted with details in the - Story status is set to sent, if applicable
TO MOVE requirements epics decisions are evaluated and viabiliy of solution) external tester(s), where story - If applicable transfer
- Correlate story number - Story weight is defined, criteria, updated in the Production
FORWARD - Assign business owner - If change management with requirements in the by Architect based on level of effort - Story has been assigned story applicable - Story status is set to maintenance to
is required move to requirements matrix - Story status is set to a development resource - Story status is set to Ready for Production operations
- Advise requestor that a - Story priority is defined, - Roadblocks removed
story has been created Analysis Backlog assigned to a spint and a - Story status is set to Testing - Story status is set to
- Story status is set to Complete
- Update requirements - If applicable, identify release Work in Progress Ready for Testing
matrix stakeholders impacted by - Story status is set to
the story / requirements Ready
INTERNAL STAKEHOLDERS
1 3 3 4 5 5 3 4 4 5 1 5
BUSINESS ANALYST
LEAD, BUSINESS ANALYST
PROJECT MANAGER
DEVELOPMENT TEAM
ARCHITECT
ORG. CHANGE MANAGER
INTERNAL TESTER(S)
EXTERNAL TESTER(S)
