This is an interesting article that was passed to me by a friend, thanks Mel! The article is based around the handling of Bugs in Agile Development. This has made me think about the way that my own team handle our Bugs. As QA and Scrum Master for my Scrum Team i am always on the look out to improve my skills in QA. Ill be taking some of the points contained in this article into account when performing QA on our team.
An important one is “Done means implemented, tested, integrated, explored, and ready to ship or deploy. Done doesn’t just mean coded, Done means finished, complete, ready, polished." This doesn’t only mean that the software works, looks good and performs the way it should, the software should be fully QA’d and known bugs fixed.