How much of the big picture must my team have?
I'm currently comanaging my first project - a fairly featured HRMS system - and have run into a bit of a bother.
We are an agile-ish firm and some of the higher ups believe that every programmer should get a holistic view of the application design, the argument being that eveyone works better when they have the big picture and know what they are working towards. Others believe that every programmer must be told only about those classes he is working on, the argument being that 1) the programmer makes no assumptions when he codes, and 2)the design concept remains secure.
I am managing a seven man team and of those there are a couple of potentially unethical guys. This has till date remained the only reason I have gone with the 'Blinkered View' camp. What does HN think?