By relying on customers to give them a list of user stories, use cases, or other relevant information, software delivery teams are asking their customers to design a solution. But business users aren’t software designers. If the customers define the scope, the project doesn’t benefit from the knowledge of the people in the delivery team. This results in software that does what the customer asked but not what they really wanted.
- Chapter 2. Key process patterns
- from Specification by Example: How Successful Teams Deliver the Right Software
- Publisher: Manning Publications
- Released: June 2011
Absolutely agree with this. As a developer this drove, is driving and will drive me nuts countless times ..
Share this highlighthttp://www.safaribooksonline.com/a/specification-by-example/49938/