S/4HANA project management
One S/4HANA programme, one shared status
Steer requirements, tests and transports in Jira.
The challenge
The difficulty is rarely SAP, but the coordination
An S/4HANA conversion ties business units, SAP teams, development, testing, operations and external partners together for months or years. Each group works in its own tool.
Without shared steering, each group describes the same status differently, and nobody can say which description is valid.
Status gathered by hand
For every meeting, the status is collected again from Excel, Jira, SAP and email.
Dependencies surface late
What links the workstreams only shows shortly before the deadline.
Four meanings of done
Business, development, testing and operations each mean something different by “done”.
The approach
An agreed mapping, not necessarily one tool
Cross ALM sets up shared steering logic: which object lives where, and how its status can be recognised. One possible target picture connects seven stations:
RequirementEpicStoryChangeTest and approvalSAP transportRelease
Not every station has to sit in the same system. What matters is that the context stays visible to every role. Transport control from Jira is handled by CC5.
Services
Control for your S/4HANA programme
Project and programme structure
Set up workstreams, releases, milestones, roles and dependencies so they stay visible when things get tight.
SAP Activate in daily work
Shape project structure and working practice so the method does not run alongside the real work.
Jira and Confluence
Hold backlogs, tasks, decisions and project knowledge in Atlassian rather than in attachments and inboxes.
Change, test and release
Link project items with changes, tests and SAP transports so progress can be read from the item itself.
Reporting and steering
Draw status from the running process rather than compiling it again for every meeting.
Governance
Name responsibilities, approvals and quality criteria before the first conflict forces it.
Two brakes
What regularly slows programmes down
Two points are often planned too late in S/4HANA programmes:
Route back from maintenance to the projectRetrofit for parallel changesRole of SAP Cloud ALM in the programme
Retrofit: as long as a production fix and a project change work on the same objects, a rule is needed. SAP Cloud ALM takes over part of the programme steering, and which part is settled at the start.
From client projects
SAP projects in practice

Raw materials
5 days
to archive two SAP Solution Managers audit-proof and shut them down
Blog
Jira in SAP projects
The benefits Jira brings to project management in SAP projects.
Your contact
Personal support for your S/4HANA programme

Ali Hamoudi
Founder and CEO
Leads the strategic development of Cross ALM and bridges the SAP and Atlassian worlds so that business and IT work together better.
Currently: growing the Cross Connector product family and designing integration and transformation solutions for hybrid SAP and Atlassian landscapes, for example agile S/4HANA transitions.
In the first conversation you clarify
- how your workstreams are cut today
- where status is produced by hand
- how change, test and transport hang on the item
- what your reports should deliver automatically
Direct contact
Prefer to write or call right away?
Email: solutions@crossalm.com
Phone: +49 30 398 36 112
Approach
Three steps to shared steering
1 · Capture
Record workstreams, tools and the points where status is produced by hand.
2 · Map
Decide which object lives where, how it is linked and how its status can be recognised.
3 · Set up
Configure Jira, Confluence and the SAP connection, automate reports and enable teams.
FAQ
What to know about S/4HANA project management
Does the whole programme have to run in Jira?
No. What matters is an agreed mapping of which object lives where. Jira fits where project and development teams already work.
Does this fit SAP Activate?
Yes. Project structure and working practice are shaped so the method becomes part of daily work.
How do SAP transports get into the project context?
Through CC5. Transports can be controlled from Jira without rebuilding SAP governance.
What role does SAP Cloud ALM play?
SAP Cloud ALM takes over part of programme steering. Which part is settled at the start, so nothing is maintained twice.
From the end of SolMan in 2027 to an agentic tool chain for SAP landscapes
How SAP teams plan the move and connect SAP, Jira and ServiceNow into one tool chain.
Contact
Let’s talk about your project
Tell us briefly what it is about, and you will hear from us personally.

What happens when you get in touch:
- A consultant gets back to you and clarifies your requirements
- Together with you, we analyse your processes and systems
- You receive a proposal for the next steps
You are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationPrefer to get in touch directly? Email solutions@crossalm.com or call +49 30 398 36 112.









