What is used to provide a simple medium for gathering basic information about stories,
recording high-level requirements, developing work estimates, and defining acceptance
tests?
A.
Story card
B.
Burndown chart
C.
Retrospective
D.
Storyboard
Story card
Which answer best describes Wide Band Delphi (e. g. Planning Poker) estimating?
A.
Team members provide story estimates individually and discuss their reasoning until a consensus on the estimate is reached.
B.
Team performance on prior projects is analyzed, and actual hours and durations are
used to determine estimates for similar user stories.
C.
Team members apply relative sizing to each task, and story points are triangulated
based on the other stories in the Sprint Backlog.
D.
Team members assign a realistic and a pessimistic estimate to each story, and points
are assigned based on the calculated average.
Team members provide story estimates individually and discuss their reasoning until a consensus on the estimate is reached.
User stories are temporary artifacts. They are considered relevant until the:
A.
Team completes them.
B.
End of the project.
C.
Release is complete.
D.
End of the sprint.
Team completes them.
For a critical project, a new team has been formed from various departments. The project
manager should start team building by:
A.
Creating a project charter, documenting roles and responsibilities of each member, and
sending it to the team members.
B.
Taking the team offsite for icebreaker sessions and other activities to ensure team
members get to know each other.
C.
Assembling the team and discussing roles and responsibilities of each member on the
team.
D.
Assembling the team and asking the members to achieve a milestone in a small
iteration.
Assembling the team and discussing roles and responsibilities of each member on the
team.
The most appropriate model for a geographically distributed project team is one in which
the team is distributed across:
A.
relatively few locations, with each location team comprised of a complete development
group developing decoupled subsystems.
B.
locations in the same time zone, working on the same systems while leveraging rich
communication channels.
C.
relatively few locations, and tasks are divided along functional lines with design in one
location, coding in another, and testing in another.
D.
many locations, with relatively few people at each location developing and testing
decoupled subsystems.
relatively few locations, with each location team comprised of a complete development
group developing decoupled subsystems.
Page 5 out of 42 Pages |
Previous |