EN
SAP S/4HANA Projects: Enhancing Learning Culture Through Regular Retrospectives
Sep 16, 2024
SAP S/4HANA transformation projects are not only complex but also tend to have a long duration. As a result, requirements, structures, processes, and practices can change during the project. To avoid being caught off guard, Sandra Kemm, Head of Project & Organizational Management at Natuvion, offers some tips on how to keep your project on track and successfully achieve your goals.
First and foremost, it’s crucial to regularly reflect on whether the chosen collaboration model still makes sense and whether the project team can work efficiently with it while maintaining transparency during the project's progress.
For this reason, we recommend moving away from one-time lessons learned sessions at the end of a project, instead establishing regular retrospectives in your project routine. It’s important to consider a few key points to ensure success. The team should recognize the value of retrospectives and prioritize them as a tool.
1. Setting the Focus
At the beginning of each retrospective, clearly communicate the specific topics you want to address. It shouldn’t be an all-encompassing project review. For example, "Today, we’ll focus on collaboration aspects like communication and reporting."
2. Frequency of Retrospectives
Weekly retrospectives can quickly lose value as there may not be enough time to implement the necessary actions resulting from them. Depending on your project meeting structure, we recommend using existing on-site meetings and conducting retrospectives every eight to twelve weeks. The duration depends on the size of the team. For very large teams, consider conducting retrospectives at different levels, such as with sub-project leaders or teams within the sub-projects.
3. Thorough Documentation
The outcomes of the retrospective should be documented in a way that is clear to the project team. This allows everyone to follow up on the discussed topics, even if they were unable to attend. However, this documentation should only be accessible to those who participated in the retrospective to maintain its integrity.
4. Enabling Follow-Up
Even more important is making the resulting actions from the retrospective transparent and ensuring their status is communicated and documented. Future retrospectives will only have the potential to provide valuable insights for project management if project members feel that the issues they raise are being addressed and, ideally, improved.
5. Variety Is Key
There are hundreds of ways to conduct a retrospective, and even more templates available. While you don’t need to reinvent the wheel each time, avoid asking the same basic questions every time to keep things engaging. For example, Retromat offers a variety of ideas.
Regular feedback from the project team gives project management the opportunity to adapt the collaboration model to the team’s needs, resulting in greater acceptance within the team. At the same time, it helps ensure that ineffective processes don’t go unnoticed.
Key Benefits of Regular Retrospectives:
-
Continuous improvement
-
Enhanced team engagement and cohesion
-
Establishment of a learning culture
This is how professional project management works!
Read our success story to discover how the project management team achieved a perfect landing for the go-live of the new SAP S/4HANA platform at EnBW ODR.
DownloadRelated News
Nov 18, 2024
Project closure: why a...
Initiating and executing a project requires a lot of...
Read more
Nov 11, 2024
Successful project...
Projects form the backbone of many companies’ activities,...
Read more
Oct 17, 2024
Carve-out with seamless...
Efficiency and close collaboration enabled Natuvion to...
Read more
Oct 14, 2024
Complex migration with...
Following several acquisitions, NRG Energy wanted to ensure...
Read more
Oct 4, 2024
OKR Framework: A Better Way...
Transformation projects usually involve a detailed...
Read more
Sep 30, 2024
Can that data be removed?
The volume of data in companies continues to grow, and...
Read more
Sep 23, 2024
Spoilt for choice
Choosing the right scenario for the transition remains a...
Read more