Hi Damon, During the design phase I conduct reviews regularly with the leads from Development, QA and (System) Architecture and this has been very successful so far. I'm also the reviewer for the QA test plans.
Before my arrival (the IxD position is brand new at this company) a very large number of bugs were being reported by QA that are now hammered out in the design phase. Those bugs created a lot of tension in the team as the Developers would close these bugs with the remark that "it works as designed", which is accurate but not good, and then QA would have to escalate to the PM to intervene and round and round they went. All 3 of the leads - QA, Development, Architecture - have expressed how much they love the reviews. To quote the Architecture lead: "I'm ecstatic we're working through this on paper first." Carrie On Mon, Oct 27, 2008 at 10:36 AM, Damon Dimmick <[EMAIL PROTECTED]> wrote: > I was wondering if anyone else has had experience with this kind of > structure, and if so, what challenges, results, and tips can you share? > We're sort of excited about the idea on our end, as our initial forays > into this model have really helped projects move along faster and with > better results. Being a small/midsized team, we don't have a large QA > department, so this allocation of resources seems to fill a lot of gaps. ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
