0
0
Software Engineeringknowledge~10 mins

Sprint retrospective in Software Engineering - Interactive Code Practice

Choose your learning style9 modes available
LearnWhyDeepVisualPracticeChallengeProjectRecallTime
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the sentence to describe the main purpose of a sprint retrospective.

Software Engineering
The sprint retrospective is a meeting where the team discusses what went well, what didn't, and [1] for the next sprint.
Drag options to blanks, or click blank then click option'
Asets deadlines
Bassigns tasks
Creviews code
Dplans improvements
Attempts:
3 left
💡 Hint
Common Mistakes
Confusing the retrospective with sprint planning.
Thinking the team assigns tasks during the retrospective.
2fill in blank
medium

Complete the sentence to identify who typically participates in a sprint retrospective.

Software Engineering
The sprint retrospective usually involves the development team, the Scrum Master, and the [1].
Drag options to blanks, or click blank then click option'
AProject Manager
BProduct Owner
CStakeholders
DQA Tester
Attempts:
3 left
💡 Hint
Common Mistakes
Confusing the Product Owner with the Project Manager.
Thinking stakeholders always attend retrospectives.
3fill in blank
hard

Fix the error in the statement about sprint retrospective timing.

Software Engineering
The sprint retrospective is held [1] the sprint review and before the next sprint planning.
Drag options to blanks, or click blank then click option'
Aafter
Bbefore
Cduring
Dinstead of
Attempts:
3 left
💡 Hint
Common Mistakes
Placing the retrospective before the sprint review.
Confusing the retrospective with sprint planning.
4fill in blank
hard

Fill both blanks to complete the description of sprint retrospective outcomes.

Software Engineering
During the sprint retrospective, the team identifies [1] to keep and [2] to improve.
Drag options to blanks, or click blank then click option'
Apractices
Bdeadlines
Cprocesses
Dtasks
Attempts:
3 left
💡 Hint
Common Mistakes
Mixing up tasks with practices or processes.
Thinking deadlines are discussed in retrospectives.
5fill in blank
hard

Fill all three blanks to complete the sprint retrospective summary code.

Software Engineering
summary = [1]([2]) for [3] in sprint_feedback if sprint_feedback[[3]] != ''
Drag options to blanks, or click blank then click option'
Alist
Bkey
Cfeedback
Dfilter
Attempts:
3 left
💡 Hint
Common Mistakes
Using 'list' instead of 'filter' for the first blank.
Confusing 'feedback' and 'key' variables.