In the part 2 of "Why requirements engineering is still valuable in 2021 and beyond?" i spoke about problems and challenges for software projects.
This is final part of
"Why requirements engineering is still valuable 2021 and beyond?"
If you use agile and wish to have such state of project,
you must be ready for the change, some people afraid of the change, because they are used to bad working environment and constant stress and some people just only care about to push enough code that the final product wouldn’t crash during user experience. Such people usually work to the senior architect position and leave company or deprecate the project just because it does not suits current business needs ;)
Picture source: Scaling Software Agility Best Practices for Large Enterprises by Dean Leffingwell
If you consider all of things which I mentioned and referenced here and in the past 2 articles, you should think and make honest estimation about what you’re really getting from your current business process, if you not sure what to do next, contact external consultants or create a dedicated team for project analysis , but do anything to change the direction of your company!
I really hope, that you as a decision maker take all options in count, because it’s always bad when you know that project would fail and done nothing to fix it, so find a solution and fix it!
(Hint, Hint: use requirements engineering)