Agile Team Tester Ratio _ Agility development

Uncle Bob in the programmer's professional literacy book talks about the best team 12 people, is basically a team, 1 coaches plus 11 football players.

The 12-person team consists of a project manager, 2 testers, 2 analysts, and 7 programmers. The analyst develops the requirements and writes the automated acceptance test script, and the tester writes the acceptance test script. Different perspectives are different, analysts focus on business value, testers focus on correctness. The analyst writes a successful road scene where testers focus on scenarios, boundaries, stress tests, and so on that may be wrong. The project manager tracks the progress of the team and ensures that the members understand the project schedule and priorities.

The number of agile teams is recommended for 6~10 individuals. Take the 10-person team, for example, to remove 1 po,1 scrum Master, and a 8-person development team to test. So what is the ratio of developers to testers? I used to bring a scrum team. Developers 6~7 people, testers 2 people. Exactly how much of a tester is appropriate. Development and testing ratio, Microsoft's is 1:1, some companies are 2:1. This rate depends on the project situation.

Participate in articles on the scrum Web site http://www.scrumcn.com/agile/scrum/4732.html

There are a number of factors that determine the tester ratio:

The quality standard of the product, for example, if related to life and property, test requirements on the current product testing tools and test conditions, is not in the TDD,CI test coverage of how many development team testing capacity and participation in the test

Elisabeth Hendrickson believes that agile teams can use fewer testers, but do more testing. In other words, developers need to be more involved in testing.

Uncle Bob in the programmer's professional literacy book, talking about professional developers to make their own error rate close to 0, that is, so that the Test team can not find bugs, this is a high demand, even professionals can not make no mistake. However, it can be seen that the requirements for developers to maintain automated testing is quite high, otherwise it is impossible to guarantee a very low error rate.