23 ms·
OneNote for us. I feel like something too formal would add too much bureaucracy to requirements which are often a creative exercise in communication. For exampl
by quickthrower2 5y ago
OneNote for us. I feel like something too formal would add too much bureaucracy to requirements which are often a creative exercise in communication. For example sometimes you need a diagram, a face to face chat, a story etc. to get the ideas across. Getting ideas and concepts across > getting every requirement set in stone for us.
- geoduck14 5y agoI agree with the creative exercise component. Do you have a check list to make sure everything is collected? How well does this scale up?
- quickthrower2 5y agoBy the time a JIRA ticket is created that ticket should have a bullet point list of what is required. But it doesn't really go into minute detail, so we rely on programmers to ask questions, QA / demos etc. to catch that level.