If you found a major bug on the last day of a Sprint, what should you do? Can you change the length of the sprint which is already decided?
This question was asked me in an interview. What should be the expected answer to this question?
Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It only takes a minute to sign up.Sign up to join this community
No. We will not change the length of the sprint
Interviewing is a skill like anything else. You want to keep in mind that interviewers keep questions vague on purpose because they want to know how you think. An interview shouldn't just be you getting question after question and you providing answers. The best interviews are a conversation.
This question is a good opportunity for you to ask clarifying questions and get a conversation going.
It's also a good time to explain how you work and explain your own knowledge.
Keep in mind that sprint start/end dates are arbitrary; they provide a nice boundary around work. I've been on many teams where we had tickets left over and they just rolled over to the next sprint.
This isn't an exhaustive list. Hopefully, this gives you a good idea of how to answer it in the future.
As a QA, it is important to report the bug as soon as it is discovered. If a major bug is found on the last day of a Sprint, the following actions should be taken:
Prioritize the bug: Determine the severity of the bug and whether it affects the functionality of the application or not.
Notify the development team: Inform the development team immediately about the bug and the urgency to fix it.
Provide details about the bug: Supply the development team with as much detail about the bug as possible, including steps to reproduce the issue, and any relevant screenshots or videos.
Discuss the impact on the Sprint: Once the development team is aware of the bug, have a discussion about the impact of fixing the bug on the existing sprint plan.
Determine the best course of action: Based on the impact, determine the best course of action, which can be continuing the sprint with a reduced scope, extending the sprint length, or reassigning some work to another sprint.
Re-evaluate the sprint plan: If the sprint length is changed, the sprint plan should be re-evaluated, and the stakeholders should be informed of the revised timeline.
In conclusion, the goal is to balance the need to deliver a quality product with the constraints of the sprint timeline. Communication and collaboration between the QA and development team are key to finding the best solution.
I have been associated with an outsourced software testing company for more than nine years, and this is a crucial stage at the end of Sprint.
In case an issue is encountered on the last day of the sprint then, following actions can be performed as per the current QA processes we follow in our organization: