[Home] [By Thread] [By Date] [Recent Entries]
In my limited experience, the person with best grasp of the project and the problem itself, is the main developer. You don't fully understand the problem until you are in the middle of developing the solution, making you best placed in that regard. And when you present the options to the decision-maker you give them the implications of each, in order that they make the right decision (so you tailor the implications accordingly :) Often the BAs and PMs are just go-betweens, relaying information between customers and developers without adding much value inbetween. Some even have the cheek to put the devs directly in touch with the customer, and only speak to the devs when they need to report progress to the management (where the specialise in taking credit during the good times and offloading blame during the bad). Letting them make decisions would be dangerous. 2008/10/16 Len Bullard <len.bullard@u...>: > I didn't say "blind", Mike. I said, "Not their shot to call". I also said > they should inform the business manager about performance and I consider > improvements to design a performance issue. It is the data designers > obligation to inform. It is not their right to determine. > -- Andrew Welch http://andrewjwelch.com Kernow: http://kernowforsaxon.sf.net/
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |

Cart



