A ScrumMaster:
A.
prioritizes the work for each iteration.
B.
directs the activities of the team.
C.
provides leadership, guidance, and coaching.
D.
manages the project scope and budget.
provides leadership, guidance, and coaching.
Which management style does Agile advocate?
A.
Task
B.
Team
C.
Product
D.
Performance
Team
What is one of the benefits of incremental delivery?
A.
Value is delivered more quickly, as software can be released after every iteration.
B.
More customers can be handled simultaneously, as each regularly receives a delivery.
C.
Fewer bugs are introduced, as code is delivered to users more frequently.
D.
Costs are reduced, as less verification is required to regression test each iteration.
Value is delivered more quickly, as software can be released after every iteration.
During iteration planning, the team is discussing the design for a user story. A team
member states that a design document should be started since the system is complex in
nature. Another team member responds that in Agile there is no documentation. How
should the ScrumMaster respond?
A.
Agree that documentation should be avoided, since it slows the progress of the team.
B.
Explain that interactions are valued over documentation, but documentation is not
forbidden.
C.
Ask the manager if the technical processes mandate that designs be documented.
D.
Ask the Product Owner if it is acceptable for the resources to spend time on
documentation.
Explain that interactions are valued over documentation, but documentation is not
forbidden.
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
Using the most highly visible method possible
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
Acceptance tests
Which term best describes an Agile project's approach to risk analysis?
A.
Regression
B.
Pareto
C.
Qualitative
D.
Monte Carlo
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.
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.
Define the story points measure.
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.
Funds set aside to contain the risk.
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.
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
Risks, action items, dependencies, and Release Backlog
Page 4 out of 18 Pages |
Previous |