Hunter J. Marshall
← All portfolio work

Washington University · 2025 · University systems

RMS Fringe Benefits Phase III

Enhance RMS fringe benefits calculations to support promotions, non-inflationary salary increases, and more precise salary-cap adjustments.

Project Manager

A record of the 2025 project. Scope, schedules, and readiness plans below reflect that period; they are not a current status report.

My contribution

  • Led defect remediation and regression testing of fringe calculation logic.
  • Coordinated environment promotions and aligned rollout timing with the RMS UI upgrade window to minimize duplicate testing.
  • Managed stakeholders across finance, HR, and research administration.

Intended impact

Improves budgeting accuracy and reduces manual workarounds through more reliable fringe calculation logic.

Overview

Fringe Benefits Phase III refines RMS budget calculation methods—supporting promotions and non-inflationary increases, allowing precise adjustments to sponsor salary caps, and reducing manual updates required today. The work continues previous fringe rollouts and is delivered with a structured validation plan.

Status: Schedule aligned to the RMS UI Upgrade timeline to avoid change collisions and enable a single regression pass; contingency allows Fringe-only PROD in December if fully ready and the UI upgrade shifts.

In Scope

  • Budget calc updates for promotions/non-inflationary increases
  • Manual salary-cap adjustment capability (where needed)
  • Defect remediation and regression testing
  • Environment promotions (TEST → STAGE → PROD)

Out of Scope

  • Unrelated net-new features
  • Non-fringe functional redesigns

Objectives

  • Restore prior fringe functionality and close known gaps
  • Reduce manual workarounds via targeted calculation logic
  • Deliver a safe cutover aligned with the RMS UI Upgrade

Objectives summarized from kickoff materials.

Why It Matters

  • Improves budgeting accuracy and auditability
  • Minimizes late-cycle corrections and hotfixes
  • Provides clearer communications with fewer change collisions

Rationale per approved change request.

Timeline

  • • June 2025 - July 2025

Key Risks & Mitigations

  • Open defects (incl. showstopper) → prioritized burndown & exit criteria before PROD
  • Submission-cycle constraints → align to upgrade window; avoid close-in collisions

From the change request and approvals.

  • Environment churn → single regression pass; coordinated promotions
  • Stakeholder confidence → clearer comms via bundled release

Approach and rationale per change documentation.

Project Team Roles Managed

  • Project Manager (my role)
  • Business Alignment / Product Owner
  • Business Analyst / Calculation Analyst
  • Application Analyst / DevOps (environments & deployments)
  • Developers (InfoEd config/patches)
  • QA / UAT Testers
  • OCM / Training & Communications
← Explore more workDownload the full portfolio (PDF)

For Shayla and our children. Always on the same team.

A NOTE IN THE MARGIN

There’s a small word in my personal creed that matters to me: “yet.” I want to be able to say “I don’t know—yet,” and then do the work to learn.

— Hunter

YOU FOLLOWED YOUR CURIOSITY

A little more magic.

A few details from my Wizarding World profile. Every good study should have a secret or two.

HOUSE
RavenclawWit, learning, wisdom.
PATRONUS
Delicate Daredevil.
WAND
Apple woodUnicorn hair · 10¾ inches
Slightly yielding.

For the stories that keep our curiosity alive.