Default Milestones Timeframes

This article outlines the typical milestones and timelines for Change Requests and Projects. Use these as planning estimates for visibility, tracking, and expectation setting.

Change Requests (Small Enhancements or Configuration Updates)

These typically don’t need full discovery or stakeholder engagement, but they should follow a consistent structure for visibility and tracking.

Milestone Description Typical Duration
Request Intake & Review Review the request, clarify scope, confirm feasibility, and determine routing (whether configuration, report, or business process). 1–3 business days
Requirements Confirmation Validate requirements with requester or functional lead (if needed). 2–5 business days
Configuration or Development Complete system configuration or report changes; document any system impacts. 5–10 business days
Peer Review / Internal Testing Conduct internal validation or peer review (User Solutions, BPM, or equivalent team). 2–3 business days
User Testing (UAT) Requester or designated functional tester verifies outcome in sandbox/test tenant. 3–5 business days
Approval & Migration Obtain final approval from requester or functional lead; submit Jira/WSS change ticket for production move. 2–5 business days
Post-Implementation Review Verify successful migration, update knowledge base (if applicable), and close the request. 2–3 business days

⏱ Typical Timeline: 2–4 weeks total

Projects (Full Discovery and Implementation Initiatives)

For large-scale efforts involving cross-functional teams, discovery, documentation, and phased implementation.

Milestone Description Typical Duration
Project Initiation / Intake Collect background, define the problem statement, identify stakeholders, and confirm project type (process, configuration, report). 1–2 weeks
Discovery & Current State Analysis Conduct discovery meetings, review current processes, gather data, and document pain points. 2–4 weeks
Future State Design & Mapping Create process maps, SOPs, or flowcharts for the proposed future state. Identify changes needed in Workday or related systems. 2–3 weeks
Requirements & Solution Design Draft requirements, confirm feasibility with technical/configuration teams, and finalize design documentation. 2–4 weeks
Configuration / Build Implement changes in the sandbox or test environment, create supporting materials, and prepare for testing. 3–6 weeks
Testing & Validation (UAT) Conduct internal and end-user testing; log issues and iterate as needed. 2–3 weeks
Stakeholder Review & Approval Present solution to stakeholders for sign-off and readiness for production migration. 1–2 weeks
Production Migration & Communication Submit Jira/WSS tickets, coordinate release timing, and issue campus communications or KBAs. 1–2 weeks
Post-Implementation Review & Optimization Confirm successful implementation, collect feedback, document lessons learned, and close the project. 1–2 weeks

⏱ Typical Timeline: 8–16 weeks total (depending on scope)

Print Article