The purpose of a project burndown chart is to:

• A.Identify and communicate upcoming milestones.
• B.Display the level of effort and resources utilized.
• C.Identify dependencies between sprints or iterations.
• D.Display the remaining work across time.

Comment: *

Name: *

Email: *

Verification: *

The Sprint retrospective:

• A.Is conducted to provide the sponsor with key information on team progress
• B.Is held at the end of each release
• C.Is optional
• D.Is intended to promote continuous process improvements

Comment: *

Name: *

Email: *

Verification: *

Which one is NOT a Pillar of Scrum?

• A.Transparency
• B.Empiricism
• C.Adaption
• D.Inspection

Comment: *

Name: *

Email: *

Verification: *

Bugs reported by the customer that have slipped by all software quality processes are represented in this metric.

• A.Technical debt
• B.Risk burndown
• C.Code quality
• D.Escaped defects

Comment: *

Name: *

Email: *

Verification: *

When facilitated and managed well, the primary benefits of a project retrospective should be to:

• A.Identify the most important issues for the sponsors.
• B.Allow the team to get ahead on release planning.
• C.Provide an open forum for team member complaints.
• D.Increase empowerment and enjoyment for the team.

Comment: *

Name: *

Email: *

Verification: *