Development and Testing activities boards in Agile – what you think of it?

[Kristina]

Hi, guys,

I’d like to hear your opinion on the following topic: Separate Development and Testing Activities boards in Agile projects.

This topic recently came in my organization. The idea behind this is, that separate testing board would allow Test Manager  easier to track testers progress, allow to indicate possible lagging behind the schedule and identify if some additional resources are required.  Here we are talking about the projects where we have 5-6 scrum teams with at least one tester in each of them.

So what is your thoughts about separate testing board?

Has anyone of you had any experience of creating and managing such? Pros and cons having it?

What metrics you, as a Test Manager, usually monitor and report to the Project Manager in such a projects? To make it more interesting, lets assume that those 5-6 scrum teams sprints might not be synchronized.

 

 

[Archana]

You can refer to the Agile Testing Resources for some useful material on this.

Specifically, this whitepaper can be helpful among others

[sneha shinde]

In agile model the development and testing activities are very essentials in testing the software is developed in incremental, quick cycles. This outcomes in little incremental launches or releases with each launch expanding on past functionality you can also check here for more details : http://crbtech.in/Testing/agile-model-software-testing/

[Cliodhna]

Was reading through and thought our upcoming webinar ‘Should Developers be Responsible for Testing’ presented by Janna Loeffler might be of some interest…

Should Developers be Responsible for Testing?

[Author]

Posts