Document Driven Development
This time I do it differently.
Instead of building a feature than asking for a feedback, I write a documentation about it and how a customer can use it. And if they approve, I will develop it.
I only see advantages to this approach:
- I engage with the customer and keep pulse beating.
- The documentation (a boring part) will be ready after development.
- Expectations are already aligned.
I donโt know to build features blindly by guessing.