{"id":707,"date":"2023-09-11T10:27:00","date_gmt":"2023-09-11T09:27:00","guid":{"rendered":"http:\/\/localhost:8082\/?p=707"},"modified":"2024-11-02T23:42:45","modified_gmt":"2024-11-02T23:42:45","slug":"when-you-should-seriously-consider-software-requirements","status":"publish","type":"post","link":"http:\/\/localhost:8082\/2023\/09\/11\/when-you-should-seriously-consider-software-requirements\/","title":{"rendered":"When you should seriously consider software requirements"},"content":{"rendered":"\n

Whilst not every team needs software requirements, there are some that would really benefit. Developers who don’t speak to end users, are distanced from the business stakeholders, and who work in remote, outsourced and offshore teams are ideal candidates.<\/p>\n\n\n\n

Having a business analyst gather your software requirements, write user stories and validate their acceptance criteria, would really be most valuable in the following situations:<\/p>\n\n\n\n