Another in the ongoing miniseries, Life/Death/Agility.
I've seen this argument online and heard it in conversation: the reason you can't use Agile on serious projects like the Shuttle is that there are hard requirements that can't be changed.
Apparently it's a principle of Agile that the developers can change requirements.
I can just see a team explaining to a NASA manager, "We understand you thought you had this requirement, but you have to get over it and embrace change: because of the Agileological refactorization/cohesion principle, we're going to have to make the heat-resistant tiles out of Charmin."
Gratification
-
*Some thoughts on developer experience.*
Years ago, I was introduced to a concept called *developer ergonomics*.
Despite the name, it's not about good ...
5 days ago
No comments:
Post a Comment