features. Most teams felt there was flexibility to increase the story points based on higher efforts needed by QA to accomplish items such as compatibility testing and automation work. This was identified and discussed during estimation. Some groups are also using the squad approach. Many teams take on work outside of just QA. Discussed the pros/cons of adding stories into the sprint to cover no sprint activities such as training and other work or just reducing the capacity of the person thereby reducing the velocity. Key items that helped with estimation Involvement in the analysis prior to estimation (story time) Early prototypes providing a better feel for what they would be getting Up front risk assessment Well defined stories and acceptance criteria Understanding resource time (days off/work on other projects or non QA work) Issues that impact estimation Stories added after the sprint starts change requests – Lack of action being taken on retrospective feedback Incomplete details in stories One company (3 people in this group) kept a spreadsheet to track time for resources to understand estimates but this was done outside of tooling manual effort – The rest focus on team velocity. Automation was briefly discussed the teams varied some included within sprint others a – – sprint behind but seems overall the preference was to move the work within the sprint. –
features. Most teams felt there was flexibility to increase the story points based on higher efforts needed by QA to accomplish items such as compatibility testing and automation work. This was identified and discussed during estimation. Some groups are also using the squad approach. Many teams take on work outside of just QA. Discussed the pros/cons of adding stories into the sprint to cover no sprint activities such as training and other work or just reducing the capacity of the person thereby reducing the velocity. Key items that helped with estimation Involvement in the analysis prior to estimation (story time) Early prototypes providing a better feel for what they would be getting Up front risk assessment Well defined stories and acceptance criteria Understanding resource time (days off/work on other projects or non QA work) Issues that impact estimation Stories added after the sprint starts – change requests Lack of action being taken on retrospective feedback Incomplete details in stories One company (3 people in this group) kept a spreadsheet to track time for resources to understand estimates but this was done outside of tooling – manual effort The rest focus on team velocity. Automation was briefly discussed – the teams varied – some included within sprint others a sprint behind – but seems overall the preference was to move the work within the sprint.
Agile%20Testing%20Estimation%20Group%20Discussion%20Nov%202015.docx