Agile Project Management Continuous Improvement Process 2

Question 1

In a Scrum team, which event is primarily dedicated to inspecting and adapting the team's process for continuous improvement?

Accepted Answer

Sprint Retrospective

Answer

Sprint Review

Answer

Daily Scrum

Answer

Sprint Planning

Question 2

A team repeatedly identifies the same impediment across retrospectives but never resolves it. What is the most likely root cause?

Accepted Answer

Improvement actions are not tracked or owned

Answer

The retrospective is too short

Answer

The team has too many members

Answer

The Sprint length is wrong

Question 3

What does the Japanese term 'Kaizen' represent in Agile continuous improvement?

Accepted Answer

Small, incremental ongoing improvements

Answer

Large, infrequent transformations

Answer

Eliminating all team meetings

Answer

Fixed annual process reviews

Question 4

Which metric is most useful for a team trying to improve its predictability over time?

Accepted Answer

Velocity trend across Sprints

Answer

Lines of code written

Answer

Number of meetings held

Answer

Total hours logged

Question 5

A facilitator notices the same loud voices dominate every retrospective. Which technique best surfaces quieter perspectives?

Accepted Answer

Use silent writing or anonymous input first

Answer

Let the loudest person summarize

Answer

Skip the retrospective entirely

Answer

Have only the Scrum Master speak

Question 6

In the PDCA (Plan-Do-Check-Act) cycle, what happens in the 'Check' phase?

Accepted Answer

Measuring results against expectations

Answer

Implementing the change

Answer

Defining the improvement goal

Answer

Standardizing the new process

Question 7

Why should a team limit the number of improvement actions it commits to per Sprint?

Accepted Answer

To ensure actions are realistically completed

Answer

To reduce documentation

Answer

Because retrospectives are optional

Answer

To avoid talking to stakeholders