INTRODUCTION TO SOFTWARE ENGINEERING
AGILE SOFTWARE DEVELOPMENT
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
Once, at the beginning of the project
|
|
|
Once, at the end of the project
|
|
|
Every Sprint
|
|
|
Every release cycle
|
Detailed explanation-1: -A backlog grooming session should ideally take place at least once every sprint. If you’re running a fortnightly sprint cycle this means at least 1 backlog grooming session per sprint.
Detailed explanation-2: -The general consensus around the ideal length for a backlog grooming session is between 45 minutes to 1 hour. Efficiency is key with grooming sessions. You need to keep things moving along and ensure conversations stay on track. Some teams decide to assign time limits to each user story to keep things moving.
Detailed explanation-3: -It is good to conduct backlog grooming sessions two to three days before sprint cycle completion. The reasons to do so include: It helps track the team’s progress to see if they would need another sprint cycle to complete what they are already working on. Prepare the team for the upcoming sprint cycle in advance.
Detailed explanation-4: -A crucial guideline in Scrum is that five to ten percent of every Sprint must be dedicated to Backlog Refinement.