Finance Workstream

People & team

Resource overview, workload distribution and team allocation across waves
👥

Team roster

All assignees active on Finance deliverables — headcount by sub-team and wave.

○ Planned — data source TBD
📊

Workload per person

Open items per assignee, broken down by design / build / test phase and status.

● In scope — derive from JIRA export
📌

Capacity heatmap

Week-by-week target dates vs. team capacity — identify crunch periods early.

○ Planned — requires resource calendar

Coming soon

This view will be populated once team and resource data is connected.
Workload by assignee can already be derived from the current JIRA export.

Finance Workstream

Finance plan

Programme timeline, milestones and key dates for the Finance workstream
🕐

Wave timeline

Go-live targets and key gate dates for Wave 1 through Wave 4 — Global and Local.

● In scope — dates from project plan
✅

Milestone tracker

Design freeze, SIT entry, UAT sign-off and cutover milestones with RAG status.

○ Planned — requires milestone data source
🚨

Risk & issues

Key risks, blockers and dependencies flagged across sub-teams with owners and dates.

○ Planned — RAID log integration

Coming soon

Connect a milestones spreadsheet or RAID log to populate this view.
Wave timelines can be auto-derived from the target dates already in the project plan.

SAP S/4HANA · Finance Workstream

Delivery Status Report

RICEFW & Configuration tracking across waves — Financial Accounting, Tax & Treasury
Developed by Alexander
Reporting date —

Phase completion by wave unit test

Share of items at each phase that are completed (Complete/Closed) and in signoff/review, per wave segment, within the current sub-team & filter selection. Test figures reflect unit testing only — SIT inputs are tracked separately and generated apart from this report.

Design status breakdown column J

Distribution of design progress across the current selection. Percentages exclude cancelled items.

Tip: click a status to filter the item detail table below.

Item detail

JIRA issue key (links to Jira), description, status, planned dates and assignee. Design-complete items show a deliverable document link where available. Click a column header to sort.

JIRA ID ↕ Description ↕ Wave ↕ Design ↕ Build ↕ Test ↕ Design plan ↕ Assignee ↕ Deliverable ↕

Highlights & exceptions

Risk flags within the current selection that need attention.

Overdue phases
A phase whose planned date has passed but isn't Complete/Closed. Sorted by phase (design → build → test), then wave priority (Global Wave 1 first, then Local, then later waves).
0
Out-of-sequence delivery
Build or test has started, but design is still New — work proceeding ahead of an unstarted design.
0
Design plan later than build/test
Design is planned to finish after the build and/or test target date, while design itself is not yet Complete or Closed — the downstream phase is scheduled before its own design is due.
0
Unscheduled items
Any phase marked Unscheduled, or with no planned target dates set.
0

Breakdown by wave & sub team

Completion = design, build and test all Complete or Closed, as a share of non-cancelled items.

Cancelled items excluded from completion %. Footer/total rows auto-removed on import. Magnum × Accenture — Project Opus · interactive status report
Finance Workstream

Test prep & execution

SIT, UAT and regression tracking across waves — Finance scope
📝

Test scenario status

Test scripts prepared, executed and signed off — by wave segment and sub-team.

○ Planned — SIT tracker integration
🐛

Defect tracker

Open defects by priority and age — P1/P2 flagged, linked to JIRA issues.

○ Planned — JIRA defect filter
✅

Sign-off progress

SIT-1, SIT-2 and UAT sign-off completion rate — by area and responsible owner.

● In scope — derive from current status fields

Coming soon

Connect a SIT tracker or JIRA test-issue filter to populate this view.
Sign-off progress can already be derived from Design/Build/Test statuses in the current data.