|Do you know where your variables are?|
Sundial, I like your writing, and he who writes well, demonstrably thinks well.
And I appreciate a proper requirements cycle, but I must concur with chromatic here. Design first with all its attendant paraphernalia (artifacts which often obscure the fact that implementation is design) is often too brittle.
As the sages of the middle way opine, you are, in this post at least, heading too far to one side of the game.
give me one or two scribblers who can understand business needs, design and implementation, and I'll be in Scotland long before the project managed, designed, and handed off to in shore/offshore coders group has found out how little the design had to do with meeting the requirements
I'ved tried the design first way. with ten pms to two developers. I was the implementer. We could have saved so many cycles if we had fired 9 pms, and had me collect the requirements. In that case. ymmv.
Furthermore, a wiki is a tool like any other. wikis don't kill projects. people kill projects.
update: design prayerful-gnalia. where is the qualia?