5. Some examples of actual use….
Greenfield work
Seeking additional
funding
A Product with Device
Heavy testing
Highly Automated
Product with higher
Agile Adoption
Technology infrastructure
movement Project
7. Should the ratio even matter in Agile Teams?
• Role Agnostic Agile Teams
• Developers Test and Automate & Develop
• Testers Develop and Test and Automate
• Based on Phase of the product adjust Backlogs
• Results from a Sprint in a Consumer Product:
• The developers picked up functional testing , Ran automation, Tester pair tested for some
time
• The test engineer picked up defects
• Impact: Burndown and backlogs became faster. More velocity, Better Engagement
• To achieve this invested in:
• Training and Skill Development
• Expectation Management
• Management Support
• Creating a phased approach as per matrix earlier to gradually adjust ratio
8. Top Insights
• Ratios for developer to test specialists can be higher in Agile
development as compared to a non agile project.
• It is possible to have a cross functional team with specializations but
not role descriptions – thus no defined Dev : Test Ratio
• It is possible to move across the ratio back and forth much easier in
Agile projects from 1:1 or 2:1 it is possible to move from this to a
ratio such as 4:1 or 8:1
• Focusing on this aspect can help speeding up Scrum/Agile adoption.
• Solutions that emerge to allow this to ratio adapt such as Crowd
testing, Dog Fooding can help improve product development