11 ms·
A lot of the Toyota methodologies ended up in various agile software practices. Not so much operations of a live system, but development practices. For example,
by stubish 3y ago
A lot of the Toyota methodologies ended up in various agile software practices. Not so much operations of a live system, but development practices. For example, all your teams push their changes to an integration branch which is automatically deployed to staging systems for testing and automatically deployed to production. And when a failure is found, that pipeline gets shut down until the problem is solved. And all eyes are looking at that problem, rather than tapping away in their own world ignoring the 'somebody else's problem'. Nobody is pushing new code unrelated to fixing the problem, making the testing and deployment of an update slower. And in theory, improves your uptime because the quality of code ending up on production is better, and when that fails, fixes will end up on production faster.
- rtpg 3y agoThat's interesting, I had never considered "main branch is red" as a similar fail state to the Toyota case, but I totally agree with that comparison!