I'm often asked how to integrate QA into sprints, especially for teams transitioning to Agile and have limited QA people (eg., 1 QA for 10 developers).
JIT (just-in-time) QA is one good way to do this. The QA acts as a consultant for the team/s and is brought in early into the process, as early as the planning stage. This also develops a QA mindset among the developers themselves as they begin programming while mindful of bugs to anticipate ("Begin with the end in mind!").
Here's how Atlassian does JIT QA: http://blogs.atlassian.com/2013/12/jira-qa-process/
Monday, February 17, 2014
Subscribe to:
Posts (Atom)
-
How bad UX design could lead to security holes (BPI Express Online Case Study) Like most banks in the Philippines, the Bank of the Philip... -
Scrum and Agile are suddenly popular in Asia, and because a lot of companies take on outsourced projects, they usually have virtual teams, w...
-
The photo shows a detail of the Red Route for the Clemson bus. I added the numbered blue circles to correspond to my comments. Center...