In Agile projects, how are planning outputs shared with stakeholders?

A.

Using the most highly visible method possible

B.

On a need-to-know basis depending on role

C.

According to the project communications plan

D.

Through a series of stakeholder meetings

When developing user stories, user expectations are best captured in what form?

A.

Acceptance tests

B.

Entrance criteria

C.

Done criteria

D.

Go and no-go limits

Which term best describes an Agile project's approach to risk analysis?

A.

Regression

B.

Pareto

C.

Qualitative

D.

Monte Carlo

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

A.

Increase empowerment and enjoyment for the team.

B.

Identify the most important issues for the sponsors.

C.

Provide an open forum for team member complaints.

D.

Allow the team to get ahead on release planning.

What is the first thing that a team should do to estimate user stories for a project?

A.

Sort the user stories according to priority.

B.

Schedule a team meeting to understand them.

C.

Define the story points measure.

D.

Estimate through function point analysis.

Risk exposure is the:

A.

Funds set aside to contain the risk.

B.

Probability a risk will occur.

C.

Amount of money the risk will cost if it occurs.

D.

Amount of damage to the project if the risk occurs.

In Agile risk management, a risk burndown chart is best used to:

A.

Qualitatively analyze the probability of a risk occurring.

B.

Track progress on risk reduction of technical risks.

C.

Document the external risks that could impact the project.

D.

Illustrate the project risk profile and new and changing risks.

What are the primary outputs of a release planning session?

A.

Release vision, assumptions, action items, and iteration goals

B.

Prioritized Product Backlog, risks, action items, and release goals

C.

Estimated iteration velocities, risks, action items, and Release Backlog

D.

Risks, action items, dependencies, and Release Backlog

A user story says that a product must be very fast. During the demo, the Product Owner is
dissatisfied with the speed of the product. The most likely reason that this occurred is
because the user story was:

A.

Too large.

B.

Not estimated correctly.

C.

Not testable.

D.

Not descriptive of the value.

What is a high-level representation of the features or themes that are to be delivered in
each release?

A.

Release plan

B.

Product roadmap

C.

Iteration plan

D.

Product Backlog