Requirements and Bridging the Silos (Part 3 of 3)
by Andrew Hayward
The first and second parts of Mr. Andrew Hayward’s three part series on Requirements and Bridging the Silosdescribed how, in larger development efforts, the division of resources into roles often reduces the effectiveness of communication and hinders understanding of requirements (see part 1 of Requirements and Bridging the Silos) and how to increase the understanding of project requirements within and between the testing and implementation silos (see part 2 of Requirements and Bridging the Silos).
The final installment continues with some examples of how silos have hindered communication and, therefore, understanding of requirements, and the solutions these organizations applied to resolve these problems. Following this is a list of eight best practices to bridge the silos in your organization.
| Attachment | Size |
|---|---|
| Requirements_and_Bridging_the_Silos_(Part_3_of_3).pdf | 153.38 KB |

How does an assembly line work?
Yes, I know someone inserts the widgets into each item as it floats gently by, but further to that I have no clue about the manufacturing process. The main adverse consequence of silo-based functioning seems to be that what got built is not what was required or even specified - does a classic assembly-line process have some kind of feedback / review built into it? And how would such feedback / review be analogous to what happens in software development?