INTRODUCTION TO SOFTWARE ENGINEERING
AGILE SOFTWARE DEVELOPMENT
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
At the end of the last Sprint in a project or a release.
|
|
|
At the beginning of each Sprint.
|
|
|
At the end of each Sprint.
|
|
|
Only when the Scrum Team determines it needs one.
|
Detailed explanation-1: -Sprint Retrospectives are ideally held at the end of every Sprint. This gives the team a chance to review what they’ve accomplished in the recent Sprint and look for ways to improve their process and outcomes.
Detailed explanation-2: -The ScrumMaster can facilitate this sprint retrospective meeting by asking everyone to just shout out ideas during the scrum. The ScrumMaster can go around the room asking each person to identify any one thing to start, stop or continue.
Detailed explanation-3: -The purpose of a Sprint Retrospective is to identify potential pitfalls and mistakes, evaluate the past working cycle and define actions that may improve things. A Sprint Retrospective is like a safe space for people to share honest feedback. It is an opportunity to focus on inspection and adaptation.