NEW
Font size
S
M
L
XL
WorksheetsProject Retrospectives
Total questions: 20
Worksheet time: 10mins
Name
Class
Date
1.
What is the main goal of a project retrospective?
a)
Assign new tasks
b)
Celebrate success only
c)
Reflect, learn, and improve
d)
Discuss budgets
2.
When should an end-of-project retrospective be held?
a)
Before the project starts
b)
Immediately after project completion
c)
During sprint planning
d)
After final client payment
3.
Why are weekly retrospectives important for remote teams?
a)
They track employee location
b)
They allow early issue resolution
c)
They allow all team perspectives to be discussed
d)
They help in budgeting
4.
What atmosphere should retrospectives promote?
a)
Blame and finger-pointing
b)
Formal silence
c)
Safe and open discussion
d)
Strict performance reviews
5.
Which format asks 'What should we Start, Stop, Continue'?
a)
Mad/Sad/Glad
b)
LLL
c)
Timeline Review
d)
Start/Stop/Continue
6.
What does SMART stand for?
a)
Specific, Measurable, Achievable, Relevant, Time-bound
b)
Simple, Modern, Accurate, Reliable, Trackable
c)
Strategic, Managed, Agile, Reviewed, Targeted
d)
Short, Measured, Accepted, Realistic, Timed
7.
What role does a Project Manager play in team retrospectives?
a)
Imposes their own opinions
b)
Encourages open communication
c)
Decides on action items
d)
Evaluates team performance
8.
How many action items should ideally come out of a retro?
a)
5–6 items
b)
1 item max
c)
2–3 focused items
d)
As many as possible
9.
What is a key question asked during retrospectives?
a)
Who is to blame?
b)
What went well?
c)
What did the client say?
d)
Who worked the most hours?
10.
What does the 'Mad/Sad/Glad' format help identify?
a)
Bug priorities
b)
Team workload
c)
Team morale and emotional impact
d)
Personal problems and possible solutions
11.
Why is follow-up after retrospectives important?
a)
To update software tools
b)
To adjust meeting times
c)
To track improvement and build trust
d)
To collect feedback forms
12.
What should you do at the end of a retrospective?
a)
Start a new sprint
b)
Summarize actions and encourage positivity for the next phase or new project
c)
Assign more work and add more layers of stress
d)
Evaluate performance
13.
Which format reflects on 'Liked, Learned, Lacked, Longed for'?
a)
4Ls
b)
Star Map
c)
Team Chart
d)
SMART Goals
14.
For remote teams, what makes retros more engaging?
a)
Longer sessions
b)
Visual tools and polls
c)
Multiple facilitators
d)
Surprise quizzes
15.
Why limit action items from a retrospective?
a)
To simplify reporting
b)
To avoid overloading the team
c)
To please managers
d)
To speed up delivery
16.
What is the first step in running a retrospective?
a)
Write a report
b)
Start assigning actions
c)
Set the stage
d)
Open JIRA
17.
What should be reviewed to gather data in a retrospective?
a)
Team bios
b)
Project timeline and key events
c)
Codebase only
d)
Meeting invites
18.
How long should a typical retrospective last?
a)
5 minutes
b)
30 min - 1 hour
c)
All day
d)
No time limit
19.
What is one benefit of using retrospective formats?
a)
Avoid team feedback
b)
Standardize discussion
c)
Avoid documentation
d)
Shorten sprints
20.
Why should retrospective notes be shared?
a)
To send to HR
b)
To keep everyone informed
c)
To add to invoices
d)
To close tickets
Reset
