A. Daily scrum

B. Sprint planning

C. Sprint review

D. Increment

A. Tailor to suit the project

B. Manage by exception

C. Ensure continued business justification

D. Focus on products

A. A 'one-team' culture in the project team is encouraged

B. The delivery team becomes more experienced at product handover

C. Releases can be used to replace management stages

D. Configuration management becomes less important

A. It is achieved by ensuring that the operational product has complete documentation

B. It is achieved by testing only a few features to deliver on time

C. It is based on the concept that people generally use a limited number of product features

D. It enables a more accurate final product to be produced

A. An 'agile sponsor'

B. A 'super product owner'

C. An 'executive sponsor'

D. A 'coach'

A. A minimum viable product

B. A measurement of lead times

C. A set of criteria to determine whether work can be started

D. A structured, timeboxed event

A. Team planning workshop

B. Project kickoff workshop

C. Project closure workshop

D. Agile enablement workshop

A. A low-level requirement

B. A fine-grained user story

C. A detailed feature

D. A high-level requirement

A. Providing access to Kanban or team boards

B. Defining Key Performance Indicators (KPIs)

C. Agreeing applicable Service Level Agreements (SLAs)

D. Establishing regular feedback loops

A. Prioritizing user stories

B. Identifying improvement opportunities

C. Updating project canvas

D. Defining acceptance criteria