In Part 1 of this three-part series, I discussed some key remaining problems with the software-development lifecycle (SDLC) as teams now typically realize it—in particular, those problems relating to the profession of User Experience. In that article, I pointed out how the analysis of problems generally leads to our learning the lessons on which we ultimately base our solutions.
Now, in Part 2, I’ll explore the key lessons that I’ve learned through the efforts of my company Ax-Stream to improve the SDLC, then set out the basis of the proposed solutions that I’ll present in Part 3.
In discussing how to improve the SDLC, I’ll employ the perennial comparison between large software-engineering projects and civil-engineering projects. People often draw this comparison because both types of projects are typically novel, complex, expensive, time consuming, critically important, and involve significant risk. However, unlike software-engineering projects, civil-engineering projects usually tend to proceed as expected and come in roughly on time and on budget. Read More