Our language betrays us when we talk about “The Business.” With these words we separate development decisions from the work they are automating. See below figure.
Even agile software development methodologies make this mistake. They may recommend a “customer” or a “product owner” who is supposed to decide what all of our customers want and prioritize the order of development.
But the most successful development occurs when developers talk directly to customers or are part of business teams. And those things called requirements? They are really candidate solutions; separating requirements from implementation is just another form of handover.