5 ms·

For those unfamiliar with “Three Ways”, I was just introduced to the concept in the book “The Phoenix Project” which was in reference to the book “The Goal”. E

For those unfamiliar with “Three Ways”, I was just introduced to the concept in the book “The Phoenix Project” which was in reference to the book “The Goal”. Excited to read this article and after briefly skimming, didn’t see any immediate reference so figured I’d leave webcrumbs here. The Goal: https://a.co/dUDdGQ6 https://a.co/dUDdGQ6 Phoenix Project: https://www.google.com/search?q=phonix+prijext&ie=UTF-8&oe=UTF-8&hl=en-us&client=safari https://www.google.com/search?q=phonix+prijext&ie=UTF-8&oe=U...

fossuser 6y ago
The Phoenix Project was great, I’d recommend its sibling book The Dev Ops Handbook, and the more recent The Unicorn Project (the same narrative story focused on the dev side).
- deleted 6y ago
  [deleted]
- technoplato 6y ago
  Thanks for the recommendation will check it out
poulsbohemian 6y ago
I stopped reading The Phoenix Project about halfway through... just read The Goal - it's better written and was the original source for the core ideas. Or, said another way, if you've already read any of Goldratt's books, you know the core ideas of the Phoenix Project. Are there other books that could more directly speak to implementation details, sure, probably.
- TeeMassive 6y ago
  I didn't read The Goal but one of the key point of the Phoenix Project is that the same principles that make a factory efficient (or inefficient) are exactly the same for software and IT.
  - kesor 6y ago
    That is general hand-wavy-way to say that things can be improved, in general. The Goal actually specifies which misconceptions we have in many cases that leads to solutions that seem reasonable but are completely wrong! Without spoiling the whole book, but do look for the explanation in there for "statistical fluctuations" and "dependant events". And then the Goal make you the reader come up with a solution that fits the factory environment (with the stat.fluctuations and dependant events) like a glove. A solution that creates a sort of a miracle for that time and place. Other Goldratt books give more example, and more teachings, on how to look at practices everyone is doing wrong and appraising those using common sense. A favorite saying by Goldratt is that "common sense is not very common". So just "solving problems" in an IT environment in most cases will lead to the wrong solutions, just because many people assume that solution X is the best solution without even looking at the problem THEY have. (GitFlow I am looking at you!)
kesor 6y ago
If anyone thinks that The Phoenix Project is horrible, then you have seen nothing before you read The Unicorn Project. This new book is a whole new level of disgusting. Goldratt's books are pure gems, most of them I have read several times over the years just to remind myself each time that I have not understood something properly the last time I read it.
- technoplato 6y ago
  Seems to be a pretty vitriolic viewpoint could you please provide some examples of why you think that?

fossuser 6y ago

The Phoenix Project was great, I’d recommend its sibling book The Dev Ops Handbook, and the more recent The Unicorn Project (the same narrative story focused on the dev side).

deleted 6y ago
[deleted]
technoplato 6y ago
Thanks for the recommendation will check it out

poulsbohemian 6y ago

I stopped reading The Phoenix Project about halfway through... just read The Goal - it's better written and was the original source for the core ideas. Or, said another way, if you've already read any of Goldratt's books, you know the core ideas of the Phoenix Project. Are there other books that could more directly speak to implementation details, sure, probably.

TeeMassive 6y ago
I didn't read The Goal but one of the key point of the Phoenix Project is that the same principles that make a factory efficient (or inefficient) are exactly the same for software and IT.
- kesor 6y ago
  That is general hand-wavy-way to say that things can be improved, in general. The Goal actually specifies which misconceptions we have in many cases that leads to solutions that seem reasonable but are completely wrong! Without spoiling the whole book, but do look for the explanation in there for "statistical fluctuations" and "dependant events". And then the Goal make you the reader come up with a solution that fits the factory environment (with the stat.fluctuations and dependant events) like a glove. A solution that creates a sort of a miracle for that time and place. Other Goldratt books give more example, and more teachings, on how to look at practices everyone is doing wrong and appraising those using common sense. A favorite saying by Goldratt is that "common sense is not very common". So just "solving problems" in an IT environment in most cases will lead to the wrong solutions, just because many people assume that solution X is the best solution without even looking at the problem THEY have. (GitFlow I am looking at you!)

kesor 6y ago

If anyone thinks that The Phoenix Project is horrible, then you have seen nothing before you read The Unicorn Project. This new book is a whole new level of disgusting. Goldratt's books are pure gems, most of them I have read several times over the years just to remind myself each time that I have not understood something properly the last time I read it.

technoplato 6y ago
Seems to be a pretty vitriolic viewpoint could you please provide some examples of why you think that?