What are the major properties of a cross-functional Agile team?
A. The team is able to commit to the completion of the project deliverables within the schedule and cost
baselines.
B. The team has all the required skills needed to collectively accept ownership of completing the next
increment.
C. Each team member has all the knowledge and experience needed to achieve the project objectives.
D. The team is comprised of specialized individuals dedicated to particular activities, who work
independently to minimize interaction and maximize overall product value. - ANS_B. The team has all
the required skills needed to collectively accept ownership of completing the next increment.
Which of the following is an Agile tool for empirical and value-based measurements of project results
Your Answer: Correct
A. Network Diagram
B. Burn Down Chart
C. Affinity Diagram
D. Monte Carlo Simulation - ANS_B. Burn Down Chart
Which of the following is a goal of a Retrospective?
A. Refinement of Backlog items in preparation for the next increment
B. Prepare documentation for release increment
C. Discuss team interactions and how the team can improve collaboration.
D. Demonstrate the sprint's new features and functionality - ANS_C. Discuss team interactions and how
the team can improve collaboration.
, Scaling Agile, through frameworks and approaches such as Scaled Agile Framework (SAFe), Large Scaled
Scrum (LSS), and Scrum of Scrums (SoS) is used to
A. Migrate Agile teams to function in larger, more predictive life cycles
B. Provide guidance for initiatives that require the collaboration of multiple Agile team
C. Improve the accountability of the Agile team and its leadership
D. Allow the Agile team to grow in size, yet retain the transparency, collaboration, and efficiency of the
smaller Agile team - ANS_B. Provide guidance for initiatives that require the collaboration of multiple
Agile team
By changing or removing organizational impediments from becoming bottlenecks that might prevent the
team from quickly delivering valuable products or services, the project manager is operating as a
A. Servant Leader
B. Transformational Leader
C. Transactional Leader
D. Situational Leader - ANS_A. Servant Leader
Kanban differs from Scrum in that
A. Kanban is centered around time-boxed project increments, where Scrum is a continuous 'just in time'
system where the next work item is pulled from an organized list of tasks .
B. Kanban is more closely related to a predictive life cycle, as it is change averse, while Scrum is change
driven.
C. Kanban was conceived in Lean manufacturing's "Just in Time" process for continuous delivery, while
Scrum is an Agile framework developed to deliver incremental value in a series of sprints.
D. Kanban is of value only in manufacturing environments, while Scrum is of value only in software
development projects. - ANS_C. Kanban was conceived in Lean manufacturing's "Just in Time" process
for continuous delivery, while Scrum is an Agile framework developed to deliver incremental value in a
series of sprints.
The introduction of a new corporate system will involve similar work at each branch location. This type
of project life cycle makes sense in completing the rollout to all locations
A. The team is able to commit to the completion of the project deliverables within the schedule and cost
baselines.
B. The team has all the required skills needed to collectively accept ownership of completing the next
increment.
C. Each team member has all the knowledge and experience needed to achieve the project objectives.
D. The team is comprised of specialized individuals dedicated to particular activities, who work
independently to minimize interaction and maximize overall product value. - ANS_B. The team has all
the required skills needed to collectively accept ownership of completing the next increment.
Which of the following is an Agile tool for empirical and value-based measurements of project results
Your Answer: Correct
A. Network Diagram
B. Burn Down Chart
C. Affinity Diagram
D. Monte Carlo Simulation - ANS_B. Burn Down Chart
Which of the following is a goal of a Retrospective?
A. Refinement of Backlog items in preparation for the next increment
B. Prepare documentation for release increment
C. Discuss team interactions and how the team can improve collaboration.
D. Demonstrate the sprint's new features and functionality - ANS_C. Discuss team interactions and how
the team can improve collaboration.
, Scaling Agile, through frameworks and approaches such as Scaled Agile Framework (SAFe), Large Scaled
Scrum (LSS), and Scrum of Scrums (SoS) is used to
A. Migrate Agile teams to function in larger, more predictive life cycles
B. Provide guidance for initiatives that require the collaboration of multiple Agile team
C. Improve the accountability of the Agile team and its leadership
D. Allow the Agile team to grow in size, yet retain the transparency, collaboration, and efficiency of the
smaller Agile team - ANS_B. Provide guidance for initiatives that require the collaboration of multiple
Agile team
By changing or removing organizational impediments from becoming bottlenecks that might prevent the
team from quickly delivering valuable products or services, the project manager is operating as a
A. Servant Leader
B. Transformational Leader
C. Transactional Leader
D. Situational Leader - ANS_A. Servant Leader
Kanban differs from Scrum in that
A. Kanban is centered around time-boxed project increments, where Scrum is a continuous 'just in time'
system where the next work item is pulled from an organized list of tasks .
B. Kanban is more closely related to a predictive life cycle, as it is change averse, while Scrum is change
driven.
C. Kanban was conceived in Lean manufacturing's "Just in Time" process for continuous delivery, while
Scrum is an Agile framework developed to deliver incremental value in a series of sprints.
D. Kanban is of value only in manufacturing environments, while Scrum is of value only in software
development projects. - ANS_C. Kanban was conceived in Lean manufacturing's "Just in Time" process
for continuous delivery, while Scrum is an Agile framework developed to deliver incremental value in a
series of sprints.
The introduction of a new corporate system will involve similar work at each branch location. This type
of project life cycle makes sense in completing the rollout to all locations
