{"id":370,"date":"2024-04-08T10:52:02","date_gmt":"2024-04-08T09:52:02","guid":{"rendered":"http:\/\/localhost:8082\/?p=370"},"modified":"2024-07-05T13:56:06","modified_gmt":"2024-07-05T12:56:06","slug":"better-software-requirements","status":"publish","type":"post","link":"http:\/\/localhost:8082\/2024\/04\/08\/better-software-requirements\/","title":{"rendered":"Better Software Requirements"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

Better Software Requirements<\/a>: A handbook for software development teams and their managers, was released this week after being in draft for nearly 12 months. A Kindle version should follow in due course.<\/p>\n\n\n\n

When software development works best, why software development fails, what a failing project looks like, and what developers actually need are covered.<\/p>\n\n\n\n

It\u2019s waterfall and agile agnostic (mostly), free to access, advert-free and with no implied sales hooks \u2013 just good advice written from the perspective of the individual software developer.<\/p>\n\n\n\n

My aim is for development teams, and their managers, to read and adopt the handbook<\/strong><\/em>. For each team that does, I will be happy to respond to any questions and feedback received from the trenches, including making rolling updates to the handbook.<\/p>\n\n\n\n

Here\u2019s a few tasty quotes:<\/p>\n\n\n\n