Tag Info

What value is "yesterday, today, blocking" to this team of testers? Presumably they have similar scrums where they present the same information to the functional team they are assigned to. So you may be asking them to repeat what they have just said, or will soon say. Perhaps you instead want to focus your meeting on "what is important for other testers ...

I wrote something recently that might help you out concerning using QA resources in an agile team. In essence, what you need to do is allow for your team to provide continuous feedback by making sure development is able to be continuously integrated and deployed to an environment where QA can run their test cases. You may have heard of a "Daily Build" ...

Tracebility matrix is a tool. It doesn't have any inheritent value, but it might be easiest way of mapping certain kind of relations between tests and requirements. As with any other tool, if it seems to work well, use it. If something else fits better, use that. If the tool nearly fits your need, modify it to give what information you need. If testing is ...

There are several factors that allows our testers to manually test effectively during a sprint cycle: Small, functionally testable stories Build/deployment automation: to me, this is the most important, builds need to be automated tested and deployed quickly if they are going to be manually tested quickly. Test automation: automating the checks supply fast ...

Even though an answer was already accepted I felt to offer another perspective: You should not run a scrum for the testers only. Effective scrum teams rely on their ability to self govern and self organize. So each team will handle things in their own way. If a tester has an issue, he/she should bring it to the scrum master and work it out in the team. ...

Given that a scrum meeting should be really quick, how much support will this actually give the testers ! Why are you calling it a scrum, can't it just be a meeting ? Also, if you are 'managing' the testers then it seems to more of a meeting than a self-organized scrum.... Not saying your idea is wrong, not sure that calling it a scrum is the best ...

I have never seen such a matrix and never heard of it before :-(. Your goal: Which requirements is almost never tested, and which is tested extremely often? can be achived by agile/technical means: Using Behavior driven development bdd as automated test for a userstory to verify that it is complete and still working. There are code coverage tools ...

A simple test strategy can only guarantee a simple assessment of quality. According to James Bach: The purpose of a test strategy is to clarify the major tasks and challenges of the test project. You can (and probably should) expand "tasks and challenges" to mean "goals, activities, deliverables, constraints, risks, and dependencies." Given that, your ...

As Suchit said, it depends a lot on the nature of the update. I've seen a one-line code change trigger a full regression because that one line happened to be in one of the core calculation engines. My suggestion for any development process, whether agile or not, is to have multiple suites of automated regression tests running on at minimum a daily basis. ...

It really depends on what the small update is. It might be a small change but it affects a lot of parts of the system e.g. Updating something in the db. The testing shouldn't be tied to whether it is a small update or a big one, however defined. It should be tied to how much you think is the effect of the given update. A small but critical update may ...

I would have a look at Kanban, great article here: http://agilesysadmin.net/kanban_sysadmin I have worked with a devops team run by Stephen Nelson-Smith (I was running the test team and we had lots of things we wanted the ops team to do for us, ranging from setting up test infrastructure to deploying applications on servers, etc) and I have to say that it ...