This article explains how to complete the BPM–HCM Project or Change Request form in TeamDynamix, including which fields are completed by the BPM-HCM team versus the requestor. It documents required fields, conditional submitter questions, and internal data standards that support automation and reporting. Accurate completion is required to ensure reliable workflows, reporting, and governance.
This article provides a comprehensive framework for evaluating and prioritizing HCM change requests and projects using a standardized 5×5 Impact–Effort Priority Matrix. It outlines how projects enter the review pipeline, how Impact and Effort scores are initially assigned by the BPM team, and how these scores are validated through joint review with functional area directors and HCM leadership. The KBA includes detailed scoring criteria, matrix placement logic, and clearly defined priority zones—
This article defines the BPM-HCM Discovery phase and provides a repeatable method for planning, conducting stakeholder interviews, documenting findings, and guiding group analysis. It includes responsibilities, meeting and interview expectations, required discovery artifacts, and how to translate outcomes into an executive recommendation. Use this standard to ensure discovery is evidence-based, compliant, and ready for governance review.
This article outlines how BPM evaluates and prioritizes requests through five phases of review and analysis, supported by Fit/Gap Analysis, Workday data review, Visio process mapping, and Impact–Effort scoring. Together, these methods create a transparent, evidence-based framework for project prioritization and execution.
This article outlines the standards and resources used by the BPM team during the discovery phase of a project. It provides guidance on documenting current state processes, capturing stakeholder input, and creating foundational deliverables such as the Basic Narrative Document, Discovery Workbook, Context Diagram, and RACI Matrix. These discovery outputs ensure process clarity, stakeholder alignment, and a strong foundation for subsequent optimization and prioritization efforts.
This article provides guidance for developing and validating process design recommendations. It ensures the BPM team produces clear, functional, and approved documentation before initiating configuration through a Change Request.
This article outlines BPM’s process for translating validated recommendations into actionable Change Requests. It ensures each submission is complete, traceable, and ready for WSS configuration and testing.
This article explains BPM’s Configuration & Testing process, including how to manage testing coordination through TDX, communicate with testers and requesters, and leverage the existing UAT framework. It ensures that all configurations are validated, defects are resolved, and readiness for deployment is fully documented before go-live.
This article describes BPM’s go-live process, including final validation, communication, and post-deployment monitoring. It ensures all changes are effectively implemented and communicated to the campus community.
This article defines BPM’s post-implementation review process, ensuring completed projects are validated, lessons are captured, and documentation is preserved for future process improvements.