3

I need complete start to end scrum process for testing a change. From taking a bug/enhancement from the product backlog , getting a BRD/FSD, writing Test scenarios......to........logging bugs to Jira or what ever is the end.

3

Scrum does not define any processes for testing, its more about a general iterative software development workflow and describes communication points and artefacts.

The cycle of a Scrum sprint is that the team commits to a certain number of stories and at the end of their sprint. Those stories should meet the teams definition of done. Which should including testing practises, but the team should come up with what they need to bring the highest quality to make and keep their stakeholders happy. I would start with the most simplest DoD and add steps as your are running into issues.

Some things to keep in mind when defining a test process into the DoD:

Handling defects is a more complex topic and could be handled in different ways, either:

  1. Keep a zero bug policy. In the next sprint first fix all the defects, learn from them and lower the teams velocity accordingly.
  2. Plan in defects like any other story, since defects are just changes like any other feature, why would they be handled differently?

Keep in mind that not all defects are equal. Some might lower customer satisfactions, while others might be used as features by some clients. Be sure to prioritise defects in the same way as features. Thats why I like the number 2 better then the number 1, but don't let your bug-list grow out of control.

0

What you are asking for is a book full of knowledge. Here is a real world example from the International Scrum Institute to get the ball rolling.

Also, this question has been asked in other Stack sites.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.