Testers who analyze quality in every aspect of the team’s deliverables also have a responsibility to mitigate risks and practical issues that are bound to come up, and help the team succeed in their product as well as at being agile. Here are five such issues that testers can help the team alleviate or avoid.
Some teams only work with stories, but it can be difficult for a team new to agile to write stories that are easy to understand and provide value every time. An alternative is to add epics and tasks. Understanding the differences between each level and knowing what size story to use for each situation will improve the accuracy of your sprint planning.
Teams should be working toward a target velocity that is based on historical evidence. There may be times when this figure needs to be adjusted, but teams that understand their velocity know that it is a good indicator of what they are capable of achieving in a sustainable way, and this will increase confidence for the teams and stakeholders.
When one organization first shifted to agile, the team had trouble with maintaining the product backlog. No one could agree on priorities for items, they didn't know which item should be groomed next, and the backlog wasn't transparent to everyone. This team found a better method that works for them.
In this interview, Matt Heusser covers how most organizations test now, presents ways you can improve your company's approach to lean, and demonstrates lean tools that can help you understand software development and test flow in a different way.