Since we work under real conditions, buffers are nothing “evil”. We are allowed to use them up. This means that the project is successfully completed “on time” if the buffer is used up at the end. If a team uses up more buffer than it has contributed to the explicit buffer, this must be compensated for elsewhere.

Rarely will anyone allow themselves buffers in order to be comfortable and stress-free. Prime Directive: We always assume the best intention. Buffers are due to real working conditions and the nature of innovation. Therefore, you can’t just cut them away.

Delays in a process are always passed on to the successor, but delays are rarely passed on. Therefore, it should become a sport to achieve a “buffer regain” when my colleagues have taken longer than estimated. At least if the process is on the critical path.

The filling level of the shared coffee cash register is transparent to everyone and all levels do their part to ensure that it does not empty too quickly.

• The POT by creating optimal framework conditions for the affected processes (in Agile EPIC’s).
• Setting the right prio in the conclave.
• The team in the sprint by focusing on the relevant backlog elements and helping each other to deliver these tasks.
• The management in the shop floor meeting when the project requests help or needs resources.

We define ranges for the buffer status

• a green area: Dont’ worry be happy, progress is better than buffer consumption. If we are needed, we can support elsewhere.
• Yellow means we are on schedule, but a little catching up would give us reserve for the possible surprises in the project.
• Special situations need special means. Red means it probably won’t be good on its own. All levels sit down and discuss how to get it back on track before the milestone is imminent.