From requirements to configuration.
Two approaches, with collaboration built into each.
- Drisdell effort
- Joint Business & Drisdell effort
With a legacy HCM solution
Requirements and gap analysis inform the workflow.
- Both surveys feed into the Business Processes Workflow.Joint effort
Business Requirements Preparatory Survey
DrisdellGAP Analysis Survey
- Drisdell
Business Processes Workflow (BPW)
- Drisdell
Functional Requirements Document (FRD)
Two-way collaboration with: BPW / FRD Review matrixJoint effort - Joint effort
Configuration Baseline Survey / Module Determination
- Drisdell
Cross Business Configuration Analysis
Two-way collaboration with: Configuration Sign-OffJoint effort
With a non-legacy HCM solution
Requirements are shaped through business engagement.
- Joint effort
Business Requirements Preparatory Survey
Two-way collaboration with: Initial Business EngagementJoint effort - Drisdell
Business Processes Workflow (BPW)
- Drisdell
Functional Requirements Document (FRD)
Two-way collaboration with: BPW / FRD Review matrixJoint effort - Joint effort
Configuration Baseline Survey / Product Determination
- Drisdell
Cross Business Configuration Analysis
Two-way collaboration with: Configuration Sign-OffJoint effort
Both paths converge · Drisdell effort
System Configuration in DEV
Two-way arrows mark collaboration and review alongside the main delivery path.