Reading “A Tale of Two Transformations”

I studied Software Engineering, esp., focusing on methodologies from requirement engineering to design methods. I practiced a lot of The Process. After graduating, I worked at a company where several documents were required to change one line of code. I became a software process assessor. Shortly after, I went back school to study tools like compilers. Instead of following The Process, I spent time writing academic papers. A few year passed and I was back to work at startup where I would be told what to do that day in the morning. I thought I was following “agile software development”. Now I think I was wrong.

This book made me realize that I hadn’t fully understood “agile software development” . Needless to say, I didn’t have any idea of “lean product development”.

It will take time to finish this book but I want to quote something to think over and over again:

One was all about standardizing process, measuring variation, and doing continual improvement, whereas the other was all about accelerating learning to accomplish new things effectively. (In "Lean" terms, this was the difference between Lean operations and Lean product development.)

Q. what about DevOps or on-call engineering? Two different things mixed into one?

To build a top-performing software development organization we need to deal with people, process, and tools.

Good to see these three dimensions! However, it was first time to see “approaches to Lean/Agile transformation”:

It's the Microsoft team model. The basic idea is a team of peers, all sharing a common goal of shipping a quality product.
MSF stands for Microsoft Solutions Framework (here)
One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.