in reply to Re^3: Some reflections on the Brainbench Perl Test
in thread Some reflections on the Brainbench Perl Test
Re-read those questions and adjust them (to remove the "agility paradigm" bias), for (your perception of) a well-run, tight-knit, mature development shop using any particular development methodology (set of established and proven working practices), and, if you can get them too waste their time answering those questions, they'll likely score highly.
The primary goal of any development procedure: is having one.
The (slightly) secondary goal: is using it.
The tertiary (but still of Xtreme importance): is that methodology does not consume an overly substantial part of your budget, at the expense of your primary goal.
When the process outwieghts the product, you are measuring the wrong statistics.
There is no substitute for competent (not gifted or clever) programmers, who work hard, to achieve the primary goal.
Experts in secondary goals seek only to emphasis their expertise, and maximise their value, even to the deteriment of that primary goal: achieving a working solution to the primary problem description.
When the process become more important than than the goal--all is lost.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^5: Some reflections on the Brainbench Perl Test
by Your Mother (Archbishop) on Dec 15, 2008 at 02:13 UTC |