4 ms·
Requirements (engineering) is the discipline that crosses the chasm between reality (needs/usage) and virtuality (software/development). Add the multitude of pa
by svilen_dobrev 5y ago
Requirements (engineering) is the discipline that crosses the chasm between reality (needs/usage) and virtuality (software/development). Add the multitude of parties involved, and the lost-in-translation stuff.
Hence, it's the most difficult thing. But noone ever points at it in schools or textbooks
- coldcode 5y agoPeople who talk about requirements "gathering" often fail to talk about requirements "changing" continuously. At my last job this was endemic, every VP and above wanted to be seen as contributing, so things changed on a daily basis in arbitrary ways, making development a minefield of eternal changes. Even waterfall would have been easier (where nothing is allowed to change), despite us doing "scrum" change was not tied to sprints but the hour hands of a clock. We still shipped things, but everything took forever and the end result was often a user unfriendly mess that cost way too much money and left everyone frazzled. Having requirements at the start of a project that rarely changed was a pipe dream. I also once worked at a place where a large project had a ship date before the requirements document ship date. Of course when it was done it did not match what was written down, and also wound up not matching the (internal) customers needs either, so it had to started over.
- datavirtue 5y agoThis waterfall myth has to go. Waterfall does not mean "requirements never change." Waterfall includes iteration. People continue to cast about flourishes of disdain toward both waterfall and agile...trapping us all in hell. Waterfall is not bad!! Learn about it.