SCRUM and TFS
My company is using TFS (Team Foundation Server) 2012 to build their releases in Sprints. We are also using it to track bugs as well. I am wondering how QA fits into the process. So far, we have manual scripts created in Test Manager and we plan on having Sprints once a week. Should a Task be created for QA for each Sprint? Does QA work from the task or from the Backlog items/Bugs? Should we create a separate project for QA?
If anyone here is familiar with SCRUM, please tell me how your shop scheduled QA within it.
In my old shop QA did not have our own project, but then again, we did not use TFS. Our developers would create tasks based on the user stories, and once ready to test we would move it to the QA side of the board and mark it in testing. If I was doing something outside the tasks while waiting for the developers, say writing test cases, I would put that on the board as a task, but would not open a ticket. Where I am now, we are agile, but use the Kanban method, not sprints. We use TFS and the CTO will create a new iteration path for the latest version and this is where all the bugs/enhancements go. We also create our test cases in test manager and then attach them to the task we are working on and these also end up in the iteration we are working in. We work from the tasks and the bug backlog. Mainly the bugs come from the latest release we are working on, but we do also have bugs come in from the customers. Depending on the severity, we will patch the release or add the fix to the latest release. We also use share point and it is there where QA has its own space to add things, like test cases, release notes etc.
This is how the way should be i mean when its about designing the correct strategy quite necessarily things are being developed so an a proper software can be given to it for doing better and at the same time how well it goes.
Most Scrum shops like the idea of BDD (Behavior driven development) and TDD (Test Driven Development), and Continuous integration.
Originally Posted by swtester99
I would say try to establish those 2 practices as quickly as possible. Even if it means implementing it in meat space (using people instead of automation). There are ways to put manual blocks into most CI systems and throw people instead of automation at the problem.