A practical framework for planning Product & Engineering work.
This categorization based on two axes makes all the sense, very well demonstrated in with planning horizons and time allocation.
Thank you, Luca!
Thank you Peter I am really glad you liked it!
It is a top-notch observation and interpretation. You deserve all the credits you got from me, Luca!
I'll keep looking for ways to promote this idea in the community.
I see in twitter that someone public about this newsletter, I like it and I started to read from the started
Thank you Mitchell! Really happy about it
I just bought the Kindle ebook of the Phoenix Project. :)
Super happy to hear! Let me know what you think about it 😊👏
and that must be why every once in a while you hear Luca & Co negotiate about percentages :)
ahah exactly, pointing knives at each other 🔪
I understand the 50/30/20, but could you explain further how you actually implemented these cycles? Did you do two tactical cycles followed by one operational cycle? Something else?
This categorization based on two axes makes all the sense, very well demonstrated in with planning horizons and time allocation.
Thank you, Luca!
Thank you Peter I am really glad you liked it!
It is a top-notch observation and interpretation. You deserve all the credits you got from me, Luca!
I'll keep looking for ways to promote this idea in the community.
I see in twitter that someone public about this newsletter, I like it and I started to read from the started
Thank you Mitchell! Really happy about it
I just bought the Kindle ebook of the Phoenix Project. :)
Super happy to hear! Let me know what you think about it 😊👏
and that must be why every once in a while you hear Luca & Co negotiate about percentages :)
ahah exactly, pointing knives at each other 🔪
I understand the 50/30/20, but could you explain further how you actually implemented these cycles? Did you do two tactical cycles followed by one operational cycle? Something else?