4 ms·
this is super valuable insight to me. I would agree with you, i have experience in how it is done in large complex organisations and i had awareness that in les
by MarkoSustic 2y ago
this is super valuable insight to me.
I would agree with you, i have experience in how it is done in large complex organisations and i had awareness that in less organised smaller orgs its not done with traceability etc.
One theme i notice is that people, especially creative people don't like doing it, but find it necessary as they see all the issues coming from not writing or having specs/reqs.
But this insight you gave is super useful for me.
Thank you!
- sloaken 2y agoOne last comment: When writing up requirements, be careful to not put implementation details as requirements. For example: let us say you are a IBM mainframe / COBOL. Putting in IBM and or COBOL as a requirement would restrict the development that might choice a raspberry Pi running Slackware and Java. And of course the reverse is true, despite being unlikely. There are probably some good books / online classes on the topic, worth a weekends time.