LostDiscoveries

You can run your own waste workshop: https://github.com/professor/waste-workshop -- let me know if you need help running it or have feedback afterwards

Thanks for noticing my research. I appreciate it.

The casual graph is not from the research. It is very difficult to establish causality. It's reasonable to question any casual claims.

The waste taxonomy groups examples of wastes into categories. Team churn is an example of the knowledge loss waste.

Here's the original paper on research gate. Free to download: https://www.researchgate.net/publication/313360479_Software_...

I would recommend this free chapter from the book Rethinking Productivity in Software Engineering https://www.researchgate.net/publication/332916053_Removing_... which describes a workshop to identify and remove wastes. The whole book is open and fun to read.

As humans, our natural pattern matching abilities sometimes causes us to see things that aren't really there. It's a blind spot for us.

In this particular case, you now have research that backs up our understanding of software development waste. If you read the paper, you'll see examples of how our previous understanding of software development waste was flawed: https://www.researchgate.net/publication/313360479_Software_...

You can read the paper here: https://www.researchgate.net/publication/313360479_Software_...

You do not need an account, you can just download the PDF.