Developers Deliver Value, Customers Dream

I read J.B.'s post recently and that combined with an internal conversation about a few issues at about the same time really helped to solidify something for me. That is the customer dreams and the developers implement.

The customer's job is to come up with concepts that will allow them to add value to their business. The technical details of the concept are not the concern of the customer and the customer shouldn't let the technical details interfere with The Vision. Then the customer articulates The Vision to the development team via Stories. So, there shouldn't be any technical detail in the stories, just the concepts that when combined as a whole will make The Vision a reality. Then the developers can put a cost on the stories. This feedback to the customer will help them determine which stories (and how many of the them) implemented in which order will give the business the quickest value.

In theory, a customer could come to a team of physicist and give them stories for a replicator. This is their Vision and they see value in having it implemented. If the have the resources to throw at this over the decades or centuries, then there may be value in persuing this. But the cost shouldn't be a factor when creating the vision.

Customers dream. We developers will do our best to make them come true...