Requirements gathering – As simple as it seems?
From initial discussions to the eventual end product, requirements can shift tremendously. The scope of a project can go from 0 to 100 in very short order.
Discuss why you think this occurs. Is it down to lack of technological understanding on the part of clients or stakeholders? Is it the dreaded scope creep as stakeholders discover they can have more than they first envisioned through the design and prototyping stages? Communication deficiencies?
How does a software engineer (or their team) account for or mitigate the possibility of expanded scope in the midst of design and development? What happens if they don’t?