Why do we do anything at all? What motivates us to get up in the morning, and come to work? When you think about it, the morning rituals we go through to arrive at a set location at a particular time, with a bunch of other people who feel just like we do (in their […]
by Bill Rinko-Gay This blog is a follow-on to the post entitled “Open Book Testing.” If you haven’t already, you may want to read that first. Once you have reviewed all your test stories it’s time to prepare to execute them. A well planned test execution, in conjunction with a well planned code implementation, helps […]
by Bill Rinko-Gay There are two components of quality software: building the right thing and building the thing right. One of the most difficult things to get right is knowing what the right thing is. In non-Agile methods this puts the focus on defining complete and detailed requirements. Experience shows that it is very difficult, […]
by Bill Rinko-Gay When I first started researching Agile Quality Assurance I was told it wasn’t necessary because Agile methods have quality built in. Agile teams developed processes such as Extreme Programming (XP) and Test Driven Development (TDD) to produce quality code in a short amount of time. Because these processes work well, it is […]
by Bill Rinko-Gay One of the advantages of Agile is the ability to deliver continuous improvements to your customer. If you have experience in traditional development paradigms you a release is usually a mixed bag filled with new functionality and new (and sometimes old) defects. This is frustrating for users and the development team. You […]
by Bill Rinko-Gay Now that your stories are chosen and the iteration has been kicked off, is there any reason not to have developers simply start in as quickly as they can on writing the code for the stories? I believe there are 3 reasons to set up a plan for delivering groups of stories […]