Every now and then a new software development process pops up, the waterfall model, Scrum, SAFe, XP, and so on. These development processes usually contain some interesting ideas that are worth looking into, but they are not generally applicable and should be view more as tips and tricks rather than a law.
I think strictly applying one of these processes is surely going to hurt your organization, they will not be a perfect fit and you'll end up with unnecessary meetings, unclear roles, the wrong tools, and probably many other headaches.
Letting the process naturally develop will yield a better result more in line with the environment it exists in. If this fails the solution is likely not to forcefully introduce an existing software development process but to sharpen your organization by giving successful people more influence and not so successful people less influence.
May the code be with you
No comments:
Post a Comment