|
|
|
|
|
|
by kevinmchugh
698 days ago
|
|
|
I think there's domains where rigorously establishing requirements ahead of time is necessary and creates better outcomes than shipping quickly and iterating. Especially safety-critical domains. If your product can kill someone (either on failure or success), defining expectations, behaviors, and specifications ahead of time is responsible. I really like this article, about the space shuttle dev teams: https://www.fastcompany.com/28121/they-write-right-stuff |
|
|