A. Team skills matrix
B. Delegation poker
C. Personas
D. Magic estimation
A. To build, measure, learn from your experiences
B. To fail fast, if you are going to fail
C. To use empiricism, based on knowledge that comes from experience
D. To create a minimum viable product to manage uncertainty
A. It contains sufficient granularity to allow work to start
B. Its purpose is to document technical requirements
C. It should appear at the top of a product backlog
D. It can be broken down into user stories
A. It is delivered by a temporary team
B. It is executed by program management
C. It requires a specific dedicated project manager
D. It is delivered by an established team
A. It reduces the planning of dependencies between projects
B. It reduces testing in order to meet deadlines
C. It encourages the customer to raise new ideas
D. It minimizes the time needed to train a new team member
A. As an opportunity
B. As an outcome
C. As a goal
D. As a vision
A. Definition of Done
B. Project backlog
C. Risk management approach
D. Agilometer
A. Manage by exception
B. Manage by stages
C. Tailor to suit the project
D. Define roles, responsibilities, and relationships
A. Defining Key Performance Indicators (KPIs)
B. Establishing regular feedback loops
C. Providing access to Kanban or team boards
D. Agreeing applicable Service Level Agreements (SLAs)
A. Lack of clear processes
B. The use of a flexible framework
C. The use of different terminology
D. Lack of guidance at project level
A. A fine-grained user story
B. A high-level requirement
C. A detailed feature
D. A low-level requirement
A. To provide a forecast for the project's viability
B. To identify and assess opportunities and threats
C. To establish accountability for the project
D. To identify the user needs and requirements
A. By ensuring control through lots of short stages during innovative projects
B. By prioritizing quality criteria to focus the project on the delivery of value
C. By continual customer involvement to obtain feedback during the project
D. By using the Agilometer to assess risks associated with the agile way of working
A. Plans
B. Issues
C. Quality
D. Risk
