Principles as discussed are great! But what really should be considered is to let go of the misguided ambition to scale. Chop up your big product in a suite of very loosely couples Apps.
Hi Rene, In LeSS, we usually prefer NOT splitting up a big product into smaller ones as it leads to a lot of sub-optimalizations and significant less customer-focus. In fact, from a LeSS perspective most products probably ought to be looked at broader, not smaller. The Product chapter in the LeSS books talks about this concept in depth.
@@LeSSWorks Interesting. Of course I will have a look at that Chapter. I agree with the sub-optimalizations remark. But not with less customer-focus. Having sub-optimalizations however is a small price to pay to to get the product in managable chunks of atomic functionality and build teams around that. With event driven systems and micro services we can manage that. But it depedends on the system at hand for sure.
@@deruytervideos (Bas here). Splitting a product in "manageable pieces" has been the promise for years. And, I've come to see it as a misguided approach. Narrowing team's scope to a subsystem or micro-service isn't going to do the larger product any good. I assume it is a longer discussion than ought to be done in TH-cam comments, though the Product section of the LeSS book is a good start. Perhaps a more in-depth in person discussion at some point :)
@@LeSSWorks Hi Bas, of course you are right 'it is a longer discussion than ought to be done in TH-cam comments' :). And I look forward to a more in-depth in person discussion at some point. Feel free to send me a message. Looking forward to it.
@@LeSSWorks I have to clarify that my suite of apps suggestion bears in mind an almost green field situation. In a system full of legacy, this becomes problematic. And then I like the requirements area concept.
Great video, I look forward to learning the LeSS organizational design framework from study and empirical learning. Exciting.
Fingers crossed for Less and its practitioners all over the world! IT needs you! 😎
Done.
Great video Craig!
Very nice!
Principles as discussed are great! But what really should be considered is to let go of the misguided ambition to scale. Chop up your big product in a suite of very loosely couples Apps.
Hi Rene,
In LeSS, we usually prefer NOT splitting up a big product into smaller ones as it leads to a lot of sub-optimalizations and significant less customer-focus. In fact, from a LeSS perspective most products probably ought to be looked at broader, not smaller. The Product chapter in the LeSS books talks about this concept in depth.
@@LeSSWorks Interesting. Of course I will have a look at that Chapter. I agree with the sub-optimalizations remark. But not with less customer-focus.
Having sub-optimalizations however is a small price to pay to to get the product in managable chunks of atomic functionality and build teams around that. With event driven systems and micro services we can manage that.
But it depedends on the system at hand for sure.
@@deruytervideos (Bas here). Splitting a product in "manageable pieces" has been the promise for years. And, I've come to see it as a misguided approach. Narrowing team's scope to a subsystem or micro-service isn't going to do the larger product any good. I assume it is a longer discussion than ought to be done in TH-cam comments, though the Product section of the LeSS book is a good start. Perhaps a more in-depth in person discussion at some point :)
@@LeSSWorks Hi Bas, of course you are right 'it is a longer discussion than ought to be done in TH-cam comments' :). And I look forward to a more in-depth in person discussion at some point. Feel free to send me a message. Looking forward to it.
@@LeSSWorks I have to clarify that my suite of apps suggestion bears in mind an almost green field situation. In a system full of legacy, this becomes problematic. And then I like the requirements area concept.
Not good n clear explanation. Wastage of time.