Retrospectives provide an opportunity for the team to:
A.
Reflect at the end of every iteration and identify improvements that will increase the
quality of the product.
B.
Participate in a mandatory meeting to share status updates across the team and to
ensure that everyone is on track.
C.
Understand from the management if the project is achieving the Scope, Quality, Cost,
and Schedule goals.
D.
Set goals at the beginning of the iteration and identify requirements that can be
delivered in that iteration.
Reflect at the end of every iteration and identify improvements that will increase the
quality of the product.
For the best results in an Agile project, customers should:
A.
set priorities and identify product features.
B.
interview new team members for fit.
C.
approve development plans and tasks.
D.
set sprint and release schedules.
set priorities and identify product features.
A project team estimates that they should complete 30 story points in the current iteration.
Partway through the iteration they realize that they will complete 50 story points at their
current rate. The team should:
A.
Shorten the iteration to meet the estimated velocity.
B.
Continue to work with the estimated velocity.
C.
Increase their estimated velocity.
D.
Release members to meet the estimated velocity.
Release members to meet the estimated velocity.
What key benefits might stakeholders realize from an Agile approach?
A.
The ability to bypass the change-management process, inserting new requirements and
changes directly into the team as they meet daily
B.
The early and continuous delivery of valuable software, providing increased visibility and
the opportunity for more frequent adjustments
C.
Increased access to the project and less reliance on formal reports and status meetings
to better understand the current work and the risks the team is accepting
D.
The team’s flexibility to make changes mid-iteration as business needs or priorities
change, increasing the ability of the team to meet project commitments
The early and continuous delivery of valuable software, providing increased visibility and
the opportunity for more frequent adjustments
The velocity chart, storyboard, burndown chart, and impediment list are often
communicated using:
A.
Status reports.
B.
Information radiators.
C.
Portfolio presentations.
D.
Project data packages.
Information radiators.
Page 4 out of 42 Pages |
Previous |