|
|
|
|
|
by crdoconnor
2821 days ago
|
|
>If that is the case, surely we can find better ways to uncover the requirements, and better tooling will help solve the problem. Experience tells me that people don’t know everything beforehand. This is highly context dependent. In some domains the business basically just needs to throw random things at the wall and see what sticks because nobody can know what they really "need" until it's tested in front of a customer. In other domains they have an incredibly detailed view of the behavior that they need. In some businesses they're in a weird situation of just not being very good at figuring out what they need and an improved process would save tons of time and money. In others nobody even thinks about any of this because their requirements are so simple and obvious nobody needs to. Iterative development is a lot of the time but it's not a panacea and it's not a replacement for fixing a broken requirements process when it's needed. |
|