One of the traditional battles between PM and PD is how much to implement of a particular feature. This dichotomy has one central false assumption: If you do less, it means you are releasing with less quality.
We are in the middle of a refactor and redesign of one our products. To be more predictable, and reduce the risk, the squad is applying the following principles to the project. They won’t be new for many of you, but it’s healthy to remind them.
At Ontruck, we spend less time on the Design and Build phase. And we spend more time on Research and Scope. Why do we work like this? Does this produce better outcomes?
We have developed a product process we follow on every new feature or project. We have iterated over this process for many months and it has been used by both senior and junior people.