PRINCE2 PRINCE2-Agile-Foundation PRINCE2 Agile Foundation Exam Exam Practice Test

As disruptive

As something to be avoided

As a necessity

As inevitable

It states that deadlines should not be moved

It has distinct goals for each stage of development

It is a behavior that involves making things transparent

It promotes the use of experiments carried out in a scientific way

It allows change to be handled dynamically

It is achieved by keeping the delivery teams stable

It helps with planning dependencies within a project

It ensures that the level of quality is protected

Controlling a stage

Managing product delivery

Managing a stage boundary

Directing a project

Receiving emailed diagrams to encourage discussion

Conducting online surveys to obtain a range of opinions

Meeting face-to-face to encourage an exchange of views

Discussing over the telephone to gather feedback quickly from stakeholders

An epic

Acceptance criteria

Definition of ‘ready’

Effort actually expended

It focuses on the prioritization and decomposition of requirements

It integrates releases within management stages

It is supported by the ‘inspect and adapt’ concept

It provides guidance on mapping PRINCE2 roles to an agile environment

Customer subject matter expert and the supplier representative

The team manager and the senior supplier

The project manager and the project board

The team quality assurance and project support

Using visualization to display information

Using meeting minutes to share decisions

Using social media to reach more people

Using email to document discussions

By ensuring control through lots of short stages during innovative projects

By using the Agilometer to assess risks associated with the agile way of working

By continual customer involvement to obtain feedback during the project

By prioritizing quality criteria to focus the project on the delivery of value

It enables the faster delivery of changes

It supports regulatory compliance checking

It enables a phased Waterfall approach

It supports management by exception

Because it explains how a small company can grow using traditional technologies

Because it is designed to manage projects, delivering products in timeboxes

Because it enables agile to be used in challenging and uncertain situations

Because running a project and setting up a new business are the same

By allowing a lot of detail at the start

By avoiding too much detail at the start

By requiring details at the start

By preventing the analysis of details at the start