Project planning · 8 min read
Divide an SAP project phase into sprints
Structure large project phases into manageable sprints for better visibility, regular feedback and visible progress.
Context
Why use sprints in SAP projects?
In complex SAP projects, a single phase can quickly become difficult to manage. Dividing it into sprints helps teams track progress and focus on clearly defined goals.
- Smaller work packages improve visibility.
- Results can be reviewed after each sprint.
- Changes can be incorporated more quickly.
- Visible progress helps the team stay focused.
Working frame
Before you start
- The phase exists in CUTO.
- The phase activities are defined.
- The team is assigned to the phase.
Step by step
From starting point to a structured flow
Select the phase
Open the relevant phase and select sprint planning from the phase menu.
Set the sprint duration
Define the standard duration, typically two to four weeks. CUTO uses it to determine the possible sprints for the phase.
Assign activities
Assign activities to the relevant sprints and review workload.
Check dependencies
Review warnings for activities whose dependencies require a different order.
Define sprint goals
Add a clear goal for each sprint as a shared point of focus.
From practice
Implementation notes
- Plan a 10–15% buffer for unforeseen work.
- Keep sprint planning to no more than two hours.
- Use retrospectives for continuous improvement.
- Account for public holidays and leave periods.
Your project