tag:blogger.com,1999:blog-1092130830223846122.post7589592429757393222..comments2023-08-27T03:49:57.957-05:00Comments on Project Management: Why Quality Assurance ain’tMeadehttp://www.blogger.com/profile/17304954468231266190noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1092130830223846122.post-57661174304502806182009-12-18T05:12:56.440-05:002009-12-18T05:12:56.440-05:00I think this is a good point.
Sometimes you have ...I think this is a good point.<br /><br />Sometimes you have more folks in the PMO and QA than you have project managers!Titanium Consultinghttps://www.blogger.com/profile/04826644272933016225noreply@blogger.comtag:blogger.com,1999:blog-1092130830223846122.post-10716637936283934392009-11-24T06:36:21.675-05:002009-11-24T06:36:21.675-05:00Don't agree. I once fought my way from single ...Don't agree. I once fought my way from single QA person working half-time (myself) to about 15 people doing the job. The code quality hasn't changed much over the time. We just found more bugs by ourselves than letting our customers to find them.<br /><br />It was however mature product with tons of SLOC and no automated regression testing and that was probably the most time-consuming task of QA team.<br /><br />Now when we work in small team on a product being built from a scratch QA is never an excuse to deliver mediocre code. It isn't accepted to push to testing code which barely compiles. Actually it is expected to be really hard task to find any bug and when it happened lately finding bugs was too easy we treated it as a bit of emergency situation.<br /><br />Yet, I can't deny that what you write is true in some organizations. I can't say whether it is majority or not though.Pawel Brodzinskihttps://www.blogger.com/profile/04369257211504152485noreply@blogger.com