2 ms·
There's two sides to requirements. There's the functional "what is required to fulfil the user's need?" part which is very much in the product owner's domain, b
by onion2k 6y ago
There's two sides to requirements. There's the functional "what is required to fulfil the user's need?" part which is very much in the product owner's domain, but there's also the non-functional requirements like "The feature must not compromise security" and "Performance metrics can't fall below X". Those parts are defined by the engineering team.
Building the right thing is product, building it the right way is engineering, and they both feed in to defining the requirements for a feature.
- Natsu 6y agoIt seems to me like you basically need a programmer who has experience doing the actual job to specify what's needed. I've seen things get morphed from what the users need to what management wants and end up badly misaligned. You're also right that there's a gulf between what users ask for and what can be sensibly implemented due to security, etc. considerations. E.G. wanting SSL to just work and ignore all cert changes magically just isn't ever going to be secure.