Fun Retro
Fun Retro Scrum Quiz
Test your knowledge on Scrum practices and agile methodologies with our engaging Fun Retro quiz! Perfect for team members, Scrum Masters, or anyone interested in agile frameworks, this quiz challenges you with 12 thought-provoking questions.
- Explore various aspects of Scrum
- Challenge your understanding of user stories and team dynamics
- Boost your agile knowledge in a fun way
According to the Scrum Guide, when is the sprint goal set?
At the end of the sprint planning
During the retrospective
At the beginning of the sprint planning
No goal is set
How many story points is the difference between what is planned in a sprint and our velocity?
0, we are perfect
7
11
20
What is the correct order of meetings during a sprint according to the Scrum Guide? (excepting dailies)
Planning, Retro, Refinement, Sprint Review
Retro, Refinement, Sprint Review, Planning
Planning, Refinement, Sprint Review, Retro
Refinement, Planning, Sprint Review, Retro
The best agile framework is:
Scrum
Kanban
Scrumban
All of them are shit, let's work waterfall
The combination that best fits the team
Lean
Extreme programming
Who is responsible for reaching a conclusion on a decision register?
PM
SM
The team
Vio, definitely Vio
One of the architects
Who can +2 an API change? (check all that apply)
A product architect if there is already a +1 from an architect
An architect if there is already a +1 from another architect
An architect if there is already a +1 from a product architect
A product architect if there is already a +1 from another product architect
How many foremen/forewomen are in the team?
3
4
5
6
How many times did we start working on web until now?
1
2
3
Too many to count
A well-written user story is: (check all that apply)
Complex
Independent
Negotiable
Big
Valuable
Uncertain
Estimatable
Small
Vague
Testable
According to our definition of done, a story is done when: (check all that apply)
Acceptance criteria is satisfied
Affected areas are tested
It is documented
A patch is released with the content
Release note is set correctly
It is covered with tests
Cherry-picks are done accordingly
Feedback from clients is positive
The correct way of fixing a client critical bug on an already released version is:
Fix only on the released version
Fix only on master
Fix on master and all relevant branches is merged, then validated by the QA
Fix on master is merged, validated by the QA, then patch requested for all relevant versions
Fix on released version is merged, validated by the QA, then patch requested for master and other versions
Order of priorities on Trader support is (without feature support):
Reopened bugs for the team, questions, bugs by bug score
Questions, reopened bugs for the team, bugs by bug score
Bugs according to bug score, questions, reopened bugs for the team
If no bugs, celebrate, get wasted and wake up from your dream
{"name":"Fun Retro", "url":"https://www.quiz-maker.com/QPREVIEW","txt":"Test your knowledge on Scrum practices and agile methodologies with our engaging Fun Retro quiz! Perfect for team members, Scrum Masters, or anyone interested in agile frameworks, this quiz challenges you with 12 thought-provoking questions.Explore various aspects of ScrumChallenge your understanding of user stories and team dynamicsBoost your agile knowledge in a fun way","img":"https:/images/course7.png"}