First outcomes of MarsLander simulation at NXP Semiconductors
The Results and Lesson’s from our new MarsLander simulation.
This week a team of NXP specialists experienced our new Simulation. Organized by ATOS, we facilitated this one day workshop about ‘Making your ITSM teams more Agile and Lean’. We are working on a detailed case description, but in the meantime we like to share with you the first outcomes.
More to come…
The key lessons from this workshop:
- Make sure you integrate testing in your team. Focus on quality at the source and first time right. Reducing rework, non-added-value activities and frustration in the team.
- Create autonomous teams. Train the employees to be able to do their work as a team. Minimize hand-overs to other teams, this will lead to waste and decrease of flow. Celebrate success.
- Create a the right metrics and kpi’s to monitor the performance of the teams. This will help to govern your work, motivate the teams and know what brings value and what not.
- Visualize the work as much as possible. Make a clear Kanban board showing the different types of work. IT Projects, planned work (Applications and Problems), unplanned work (Issues, errors) and Improvement activities.
- Set priorities in the context of the work and not based on tables and flow-charts. During standups, discuss with the product owner (or service owner) and the team why we should do some of the work earlier than other? By sharing the why, the team will understand, and much more involved in the process to solve it on time. They become more the owners of the issues.
- We have to learn how to work with the different learning styles. One round went well and we were all motivated, then the next round it went not so well and we experienced the frustration in the team. Dealing with uncertainty, stimulate to experiment, make small steps and celebrate are crucial aspects to keep motivating the team.
- Product Owners are important roles in the Service Teams. The need to help the teams to be able to plan, execute and test the work they are doing. Share the goals, the value and expected outcomes. But also take responsibility to give the team space to experiment and learn. It’s about investing in the future.
- Give teams enough time to learn and experiment. Continual Improvement is only possible if we empower teams to organize and improve their own work. This requires effort, time and commitment.