Ulrich Junker<p>Nice critique of <a href="https://fediscience.org/tags/AgileMethods" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AgileMethods</span></a>, <a href="https://fediscience.org/tags/Scrum" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Scrum</span></a> and so on, with suggestions to give more autonomy to developers and to automize as many nasty things as possible. </p><p>Imho, there is only one receipt to success in <a href="https://fediscience.org/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SoftwareDevelopment</span></a>: pose the right questions until you get the right conceptual understanding of the problem to solve and do this problem analysis before doing too much coding. Without good analysis, your code will just be guesswork.</p><p><a href="https://youtube.com/watch?v=KJ5u_Kui1sU&si=your" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">youtube.com/watch?v=KJ5u_Kui1s</span><span class="invisible">U&si=your</span></a></p>