Corporate Memory – Fighting Rework with a Simple Principle and a Practical Implementation

Abstract

Can we avoid the many minor misunderstandings that generate a lot of rework? Can new tools, and changing a few old habits, create more flow in the development work with a less annoying rework? - We have become used to the meetings and communications required to fix the misunderstandings between different stakeholders and the following rework. Increased number of stakeholders and complexity, in general, means that many projects are reporting a state of meeting suffocation where they are making unsatisfying little progress due to many meetings. One valuable principle that deals with the problem is “Corporate Memory” from Expectations Engineering, which will be briefly described, including the benefit it will bring. To demonstrate the principle in practice, this paper will show an implementation in the IS department of Grundfos. While this is a great example based on a software DevOps environment, it still serves as a general example for implementation in all other available settings.