Build the right product with results-driven development
When developing a product, it’s important to ensure that you’re not only building things the right way, but that you’re building the right product. These two goals don’t have to be mutually exclusive.
In this post, I’ll detail two development processes: test-driven development and results-driven development. These concepts, when used together, can achieve both goals.
What is test-driven development?
In 2002, Kent Beck, the creator of extreme programming (XP), released the book, Test-Driven Development: By Example. The concept was simple: In order to start writing code, you must first write a test that defines what success looks like for a given requirement. You then run the test, but because you haven't written any code yet, the test fails. It's at that point you start developing just enough code to pass the test.
... read the whole story at www.devbridge.com.