• Português
  • 简体中文
  • 繁體中文
  • Deutsch
  • English
  • Español
  • Français
  • 日本語
  • Latviešu
  • Lietuvių
  • Русский

Submitted Conference Content

Full name

Kris Philippaerts

Job Agile Coach
email kris [at] ilean [dot] be
Company iLean
City (Country) Gent (Belgium)
Time 1h
Type of Conference Workshop / 40 attendees
Level Sensitized

The multi-level feedback cycle


Hi, I'm Kris and I'm an Agile Coach and Trainer at iLean. I assist organizations in adopting an agile culture and in implementing agile and lean techniques such as Scrum and Kanban. I love communicating with different people and I'm capable of adjusting my communication style to different audiences. During the years, I developed a vast experience in organisatorial coaching. Together with my technical roots, this gives me the ability to understand both management and team members, and help them communicate with each other more effectively. Next to organisatorial coaching, I'm also a passionate Agile trainer and I often facilitate workshops and sessions on Agile Conferences. During my trainings and workshops, I always aim to find a good match between the conceptual ideals and the not-so-ideal reality. I use my extensive coaching experience to pervade my trainings with hands-on examples and loads of tips and tricks.


For most Scrum and Agile adepts, Deming's PDCA cycle (or feedback cycles in general) are as common as a daily cup of coffee. It becomes a second nature for most of us: inspect and adapt, inspect and adapt, inspect and adapt... However, in reality these feedback cycles can be seen as multi-level communication flows with different types of information that cycle around in different cycles: - Vision and long-term goals - Short term functionalities - Planning and budget - Implementation processes and quality - Team dynamics In order to run your feedback cycles effectively, you must run your PDCA on all of these, from start to end, from P to A. In this session, we will take a deeper look how Scrum implements these cycles by matching them with the different Scrum Rituals and Artefacts. This way, we will identify where Scrum does and does not provide the necessary links to ensure a closed PDCA cycle on all levels. For the missing links, we will try to harvest ideas and practices to reinforce your Scrum implementation.

Benefits for the attendees

- Understand the actual intention of the different Scrum Meetings and Artefacts - Understand where Scrum has no direct answers and how to solve this for your team - Understand how to keep different types of information from polluting each others feedback loops

Go to the submission page!