WorksheetsQuiz Session 1
Total questions: 20
Worksheet time: 10mins
Name
Class
Date
1.
1. How frequently should a team sync be organized?
a)
Daily
b)
Weekly
c)
Ad-hoc
d)
All of above
2.
2. What are the advantages of conducting daily team syncs in a Scrum environment?
a)
Reduces the need for communication
b)
Ensures frequent communication and quick identification of blockers
c)
Allows for detailed discussions on long-term goals
d)
Eliminates the need for iteration planning
3.
3. What are the potential disadvantages of daily team syncs if not managed effectively?
a)
They eliminate the need for other meetings
b)
They can become monotonous and lack engagement
c)
They reduce the need for team collaboration
d)
They ensure detailed discussions on project progress
4.
4. What is an anti-pattern that can negatively impact the effectiveness of a team sync?
a)
Team members attend and actively participate
b)
Team syncs focus on immediate issues and align daily tasks with iteration goals
c)
Individuals turn the meeting into a daily status report
d)
Product Owner gains insight into the progress of Iteration Goals
5.
5. What could be a reason for a team to organize weekly syncs in addition to daily syncs?
a)
To reduce the frequency of communication
b)
To provide a more comprehensive overview of progress
c)
To ensure daily updates are communicated
d)
To eliminate the need for iteration planning
6.
6. What is typically NOT a goal of the Iteration Review?
a)
To review the work completed during the iteration
b)
To gather feedback from stakeholders
c)
To discuss the team’s velocity
d)
To discuss impediments encountered during the iteration
7.
7. What is the primary purpose of the Iteration Planning meeting?
a)
To review the previous iteration's work
b)
To brainstorm new features
c)
To plan the tasks and goals for the upcoming iteration
d)
To discuss team conflicts
8.
8. When should the Iteration Review meeting be triggered?
a)
At the beginning of each iteration
b)
At the end of each iteration
c)
Midway through the iteration
d)
Only when requested by the Product Owner
9.
9. When should the Iteration Planning meeting be triggered?
a)
At the end of each iteration
b)
At the beginning of each new iteration
c)
Midway through the iteration
d)
Only when new features are added
10.
10. Apart from the Agile Team (PO, Agile Coach, Developers, QC, Design), who should join the Iteration Review and Planning meetings? (can select more than ONE option)
a)
DevOps
b)
Business team
c)
Product Management
d)
Only the Agile Team
11.
11. In Iteration Planning, which topics should be discussed? (can select more than ONE option)
a)
Analyze and estimate the Stories
b)
Demo completed stories and gather feedback
c)
Review progress of Iteration Goals
d)
Develop and commit to iteration goals
12.
12. Which of the following are preparations for Iteration Review? (can select more than ONE option)
a)
Invite Stakeholders who want to see the team's progress (e.g., members of other teams, business people)
b)
Update Team Backlog based on feedback from the Stories demoed.
c)
Move incomplete work to the backlog for prioritization in future Iterations.
d)
Reflect on unfinished Stories Identify impediments, risks, false assumptions, changing priorities, estimating inaccuracies, or over-commitment
e)
Make ready for demoing work delivered in Iteration
13.
13. Which of the following are post-event actions for Iteration Planning? (can select more than ONE option)
a)
Review, prioritize team backlog and refine stories to support feature releases and PI Objectives
b)
Share final Iteration Goals for all stakeholders
c)
Update the work management tool or team board to reflect the new iteration plan
d)
Update on changes to dependencies, risks, or impediments identified during the planning
14.
14. Which of the following are preparations for Iteration Review? (can select more than ONE option)
a)
Invite Stakeholders who want to see the team's progress (e.g., members of other teams, business people)
b)
Update Team Backlog based on feedback from the Stories demoed.
c)
Move incomplete work to the backlog for prioritization in future Iterations.
d)
Reflect on unfinished Stories Identify impediments, risks, false assumptions, changing priorities, estimating inaccuracies, or over-commitment
e)
Make ready for demoing work delivered in Iteration
15.
15. During an Iteration Planning meeting, the team discovers that a high-priority story has dependencies on another team’s work that is not yet completed. What should the team do?
a)
Ignore the dependencies and proceed with planning
b)
Remove the story from the current iteration and plan it for the next iteration
c)
Assign the story to a single team member to handle independently
d)
Raise the issue and plan to coordinate with the other team
16.
16. During an Iteration Planning meeting, the team realizes that they have overcommitted and won't be able to complete all the planned stories. What should the team do?
a)
Continue with the current plan and try to complete as much as possible
b)
Extend the iteration duration
c)
Re-prioritize the stories and adjust the iteration plan
d)
Split the stories among more team members
17.
17. During an Iteration Planning meeting, the team realizes they have overestimated the effort required for several user stories in the previous iteration. What should they do for the current iteration planning?
a)
Adjust the estimates based on previous experiences
b)
Continue with the same estimation approach
c)
Reduce the number of user stories planned
d)
Assign fewer tasks to each team member
18.
18. In an Iteration Review, the team receives feedback that a key feature they developed does not meet the stakeholders' needs. What should the team do in response to this feedback?
a)
Ignore the feedback and continue with the next iteration
b)
Schedule a follow-up meeting to understand the stakeholders' requirements better
c)
Remove the feature from the product
d)
Ask the stakeholders to adjust their expectations
19.
19. In an Iteration Review, the stakeholders express dissatisfaction with the value delivered despite the team completing all planned tasks. What should the team do to address this issue in future iterations?
a)
Increase the number of tasks planned for the next iteration
b)
Ignore the feedback and continue with the same approach
c)
Extend the iteration duration to complete more tasks
d)
Focus on high-value user stories and improve communication with stakeholders
20.
20. During an Iteration Review, the team finds that several tasks were not completed due to unforeseen dependencies on other teams. What should they do to prevent this in the next iteration?
a)
Ignore the dependencies and hope they are resolved
b)
Identify and plan for dependencies during Iteration Planning
c)
Assign all dependent tasks to one team member
d)
Avoid tasks with dependencies in the future
100 %
