We really don't *have* any documentation people at this point. Our only full-time external Doc guy died last year, and the only person left really doing internal documentation was umbran, who got laid off last week. (Yes, I suspect we're going to regret that particular decision.)
But yes, QA is fully engaged in the entire process. It's all being laid out by a small committee of the heads of Dev and QA, and their common boss, the VP of Engineering. The theory (based what seems to be the consensus among the more plausible Agile sources) is that all features really need to be treated as a collaborative process between Dev and QA from the start, and we're trying to take that principle fully seriously. QA starts developing the test plans while Dev is designing the feature, and we start testing the feature in the automated testbed as soon as it's checked in...
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Date: 2007-01-23 12:32 am (UTC)But yes, QA is fully engaged in the entire process. It's all being laid out by a small committee of the heads of Dev and QA, and their common boss, the VP of Engineering. The theory (based what seems to be the consensus among the more plausible Agile sources) is that all features really need to be treated as a collaborative process between Dev and QA from the start, and we're trying to take that principle fully seriously. QA starts developing the test plans while Dev is designing the feature, and we start testing the feature in the automated testbed as soon as it's checked in...