Project Retrospectives

What is the main goal of a project retrospective?

• Assign new tasks
• Celebrate success only
• Reflect, learn, and improve
• Discuss budgets

When should an end-of-project retrospective be held?

• Before the project starts
• Immediately after project completion
• During sprint planning
• After final client payment

Why are weekly retrospectives important for remote teams?

• They track employee location
• They allow early issue resolution
• They allow all team perspectives to be discussed

• They help in budgeting

What atmosphere should retrospectives promote?

• Blame and finger-pointing
• Formal silence
• Safe and open discussion
• Strict performance reviews

Which format asks 'What should we Start, Stop, Continue'?

• Mad/Sad/Glad
• LLL
• Timeline Review
• Start/Stop/Continue

What does SMART stand for?

• Specific, Measurable, Achievable, Relevant, Time-bound
• Simple, Modern, Accurate, Reliable, Trackable
• Strategic, Managed, Agile, Reviewed, Targeted
• Short, Measured, Accepted, Realistic, Timed

What role does a Project Manager play in team retrospectives?

• Imposes their own opinions

• Encourages open communication

• Decides on action items

• Evaluates team performance

How many action items should ideally come out of a retro?

• 5–6 items
• 1 item max
• 2–3 focused items
• As many as possible

What is a key question asked during retrospectives?

• Who is to blame?
• What went well?
• What did the client say?
• Who worked the most hours?

What does the 'Mad/Sad/Glad' format help identify?

• Bug priorities
• Team workload
• Team morale and emotional impact
• Personal problems and possible solutions