I frequently get articles regarding the demise of Agile and I usually give them a few minutes of my morning time. Like many of you, I have a stake in development processes and protocols, and have great interest in new ideas. When it comes down to the details, I usually land on the same conclusion: it doesn’t matter which dev philosophy to which you adhere, as long as commit to one, communicate it well to your team, constantly evaluate its effectiveness, and adapt to changes in your business, team, and goals. To often I have been in organizations that strive to practice good development protocols instead of making good software. Ask first if you are delivering a good product and keeping your customer, team, and users happy. If the answer is “Yes”, then your dev tools are working, otherwise, your processes are not working. The last thing you wan’t hear from your dev leaders is, “this is the way we do things”. An owner wants to know that you have a good working process that produces good results. You can’t hang your hat on maintaining a process that produces trash. Figure out how to make it work. Figure out how to keep your team excited to work on it. The bottom line doesn’t care what you call it.

Inspired by this article:

https://medium.com/@neerupujari5/agile-is-dead-this-development-process-is-better-049cc1bb9c35