January 2018
Beginner to intermediate
312 pages
7h 22m
English
Before attempting to solve a problem it’s important that we understand the problem correctly. Obviously, if our understanding of the problem is incomplete or distorted, then we won’t to be able to provide a useful solution. And sadly, of course, it’s the developers’ understanding, not the domain experts’ understanding, that gets released to production!
So how can we ensure that we, as developers, do understand the problem?
Some software development processes address this by using written specifications or requirements documents to try to capture all the details of a problem. Unfortunately, this approach often creates distance between the people who understand the problem best and the people who will implement ...
Read now
Unlock full access