Clear questions and runnable code get the best and fastest answer |
|
PerlMonks |
Re^4: Beyond Agile: Subsidiarity as a Team and Software Design Principleby mr_mischief (Monsignor) |
on Jul 24, 2015 at 17:13 UTC ( [id://1136209]=note: print w/replies, xml ) | Need Help?? |
In many cases requirements won't change between beginning on a particular release and the release date, but in many cases they will. Either way, from one release to the next things almost always change. Otherwise, why release again? You actually get fewer of these changes per release if you release more often. That minimizes scope creep during the release. Also, people who think a UI is not part of the requirements obviously are not responsible for UI or UX development.
In Section
Meditations
|
|