Development > Bridging the Gap Between Requirements and Solutions
In software development projects, writing the code is the easy part. However, defining and communicating what needs to be built continues to be a challenge. Customers, business analysts, testers, and developers all speak a different language. All interact with the same system, but each has a very different view into how it works. Often times, this difference in viewpoint causes a communication breakdown that results in a failed development effort. The goal of this talk is to show the ways we’ve been able to lessen the communication impedance between requirements and development, such as prototyping, 3 amigos, DSL/executable requirements, and acceptance test driven development.