Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

My favorite variant on this is combining "agile" with no design or requirements up-front with a rigid change request process at the end.

The thing is, a certain measure of "change control" was always a good idea, even in an "agile" environment. My (admittedly subjective) take is that getting away from change control contributed to everyone's mindset shifting to where "changes are free".



Well, in the project I saw this happen on they also stopped the requirements gathering process for an agile process where they promised to implement changes when it didn't match the process well, so it was kind of a bait-and-switch technique.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: