| 1 |
Phase 1 – Intake |
Captures, reviews, and appropriately routes incoming Workday-related requests through the official intake channel. Ensures requests are complete, categorized correctly (Project, Change Request, or Service), assigned an owner, and structured appropriately (Parent vs Child) in TeamDynamix. |
View Article |
| 2 |
Phase 2 – Discovery |
Develops a clear understanding of the business problem before defining solutions. Includes stakeholder engagement, current-state review, fit/gap analysis, documentation of pain points, success criteria, and the Discovery Summary outcome used for downstream planning and prioritization. |
View Article |
| 3 |
Phase 3 – Prioritization |
Determines if and when the request should be worked based on impact, effort, risk, and capacity. Includes scoring, portfolio review, leadership decision coordination, and formal documentation of the prioritization outcome and next steps. |
View Article |
| 4 |
Phase 4 – Planning |
Translates an approved request into a structured, actionable plan. Confirms scope boundaries, stakeholder engagement readiness, sequencing, high-level timeline, dependencies, and whether the work will proceed as a Project or Change Request. Includes planning outcome documentation and readiness confirmation for Solution Design. |
View Article |
| 5 |
Phase 5 – Solution Design |
Defines the detailed functional approach before configuration work begins. Documents future-state process changes, Workday configuration requirements, security/reporting/downstream impacts, and obtains stakeholder validation. Prepares final design artifacts required for Ticket Submission to Workday Support Services. |
View Article |
| 6 |
Phase 6 – Ticket Submission |
Initiates Workday configuration work through Workday Support Services (WSS). Includes readiness checks, Jira creation and submission, documentation attachment, recording Jira references in TeamDynamix, and ongoing clarification coordination and progress tracking. |
View Article |
| 7 |
Phase 7 – Testing |
Validates that configuration meets business and functional requirements. Covers test planning, BPM functional testing, User Acceptance Testing (UAT) coordination, defect tracking and resolution, retesting, and readiness confirmation for Testing Completed. |
View Article |
| 8 |
Phase 8 – Testing Completed |
Formally confirms that all testing and approvals are complete, including UAT sign-off and defect closure validation. Confirms deployment readiness, coordinates training/communications handoffs if needed, and documents readiness to proceed to Deployment. |
View Article |
| 9 |
Phase 9 – Deployment |
Moves approved changes into the Production environment. Coordinates deployment timing and prerequisites with WSS, confirms go-live readiness, monitors deployment, performs initial production validation, and communicates deployment status and outcomes to stakeholders. |
View Article |
| 10 |
Phase 10 – Stabilization |
Ensures the solution functions as expected after go-live. Includes monitoring, issue triage, remediation coordination (including WSS involvement as needed), retesting, user clarification support, and documentation updates until closure readiness is confirmed. |
View Article |
| 11 |
Phase 11 – Closure |
Formally closes the request and captures completion artifacts. Confirms stabilization completion, compiles final documentation, captures metrics and lessons learned, archives artifacts for audit/reporting, and closes the TeamDynamix ticket with final stakeholder communication. |
View Article |