4 ms·
Poorly defined and incomplete functional requirements with mare hints of the expected non functional requirement Leads to: - Frustrated developers who thought
by canterburry 6y ago
Poorly defined and incomplete functional requirements with mare hints of the expected non functional requirement
Leads to:
- Frustrated developers who thought they were done and were doing good
- Frustrated QA engineers who can't certify the feature as written
- Frustrated product owners who were assured the feature was "done"
- Frustrated management who is told it will take longer than promised
- youeseh 6y agoDo you have a project manager / product owner on your team?
- canterburry 6y agoWe do, they are the ones writing the poor requirements.
- youeseh 6y agoDo your PMs have a background in the type of engineering that you do? It may be helpful to point out bad requirements whenever they're provided. Keep a copy of the bad requirements and why they're bad, so when they repeat their mistakes, you don't have to repeat yourself explaining why the requirement is bad.
- canterburry 6y agoI think driving towards the point of this thread, I could envision a JIRA plugin which helps writing complete and well defined stories of manageable size. It could simply be a template with appropriate sections, or a Q&A bot which drills down to the requirements.
- Ididntdothis 6y ago“Frustrated management who is told it will take longer than promised“ I can relate. And often management behaves like bystanders instead of fixing these problems.