Bad advice for analysts: how to write unclear requirements
-
-
20 min
- Your team repeatedly returns an increment that you have assigned to them
- When the team have started working on the increment, it's been realized that devs compeleted it in a one way, but QAs verified in another. As result, your Customer wasn't happy.
- The time spent on explanations for your team fexceeds the time spent on the requirements writting.
Let me share with you with some tools that help me reducing a big number of such cases in my daily work.