Sprint Planning是大多数敏捷团队所做的事情。但是，当每个团队都有不同的需求时，并不总是有一个“一种尺寸适合所有”的方法。结果，它并不总是清楚QA的作用应该是什么。QA应该是Sprint规划过程的一个组成部分吗？或者应该告诉测试人员来看看Jira Board并遵循截止日期？请继续阅读，了解QA的作用如何 - 并应适合Sprint规划过程。
First things first: Does QA even have a role in Sprint Planning? After all, the everyday answer at many companies may be “no.” But to have the best software development and Agile process possible, it should be “yes!”
QA only has a finite amount of testing time per sprint. So it’s a good idea to make sure Testers can provide full test coverage for all tickets in the timeline.
Top 5 Reasons to Involve QA in Sprint Planning
估计不仅仅是开发人员 - 或者至少他们不应该是。毕竟，对于工程师需要在Sprint中完成的每张票证，QA也必须有时间测试它。通过在每个Sprint中提供对票证的估计，测试人员可以帮助重量，其中特征和/或错误修复可以在时间轴中适用。要了解更多信息，请查看本指南QA Testing Estimation Techniques。
For example, imagine a ticket entitled, “Add embedded video player.” The summary might say something like, “Add a video player to screens that have audio clips.” That information could be clear enough to other roles, such as Project Managers. But Testers generally need more detailed acceptance criteria in order to make sure the feature is truly implemented as intended.
If you’re not familiar with acceptance criteria, essentially it’s a list of functionalities or other details that the feature should have. Some of the information Testers might need in the above scenario could include:
- Are the videos expected to be hosted on the company’s official YouTube, Vimeo, or somewhere else?
When QA is involved in Sprint Planning, Testers can quickly identify which tickets need more acceptance criteria. When this is done early on, Product Managers will have time to add the additional details. If QA isn’t aware of the missing info until the ticket is ready to test, the launch itself could be delayed.
3. Test Cases
4. Device/Browser Coverage
A big part of QA testing apps and websites is determining which browsers/devices should be tested. This can vary depending on the specific feature or bug fix being tested. For example, if there’s a new feature targeting people under 30, it’s less likely that it will be used on IE 11 (Internet Explorer). On the other hand, it will almost definitely be used on iOS 14.
When QA has a role in Sprint Planning, they can advocate for and plan specific device/browser coverage for each ticket in the sprint.
It’s a reality that even with excellent planning, sometimes a team can’t meet the original sprint deadline. Since QA is the last step in completing each ticket, it’s often the testing time that gets cut off at the end. Sprint Planning can be used to prioritize tickets and make backup plans in the event that not everything is completed in time. It’s important for Testers to be aware of which tickets are the most––and least––important.
上面的是很多原因的只有少数that it’s beneficial to give QA a role in Sprint Planning. But each reason is significant, even on its own––let alone when combined with the rest! There are many ways for QA to play a role in Sprint Planning. Each team can find the way that works best for them. But ideally, QA should always play some role in Sprint Planning––or you may end up with a sprint that’s not truly planned out at all.