Agile Foundations

Agile development puts an emphasis on creating an environment that is based on empowered teams in order to encourage innovation and creativity

• True

• False

Which of the following is an Agile Manifesto value?

• Individuals and interactions over following the plan

• Working software over processes and tools

• Responding to change over comprehensive documentation

• Customer collaboration over contract negotiation

The acronym WIP stands for

• Worth in performance

• Waste in process

• Work in progress

• Work is progressing

In the Agile manifesto, what is valued more than processes and tools

• Customer collaboration

• Working software

• Individuals and Interactions

• Responding to change

Agile teams are:

• Self Organizing, Cross Functional

• Cross Productive, Self Organizing

• Self Destructive, Self motivating

• Non productive, Selfish

A team is using a Kanban board and notices that many items are stacking up in a certain stage of the development process. How should they initially react in order to best manage flow?

• Move items from design to delivery more slowly in order to spread out any potential problems

• Calculate the burn up rate.

• Make sure there are explicit work in progress (WIP) limits at each column/stage of the development process and then experiment with tuning those across iterations.

• Increase the number of feedback loops.

What is the significance of determining Definition of Done (Select all that apply)

• Determines the objective behind each sprint

• Determines the number of tasks being completed for each Backlog item

• Increases Transparency

• Increments delivered are more effective and potentially releasable

• Develops a common understanding amongst all the team members as to what all needs to be completed to mark every item complete.

Which of the following is not the part of Agile Model?

• Scrum

• Spiral

• Kanban

• Extreme Programming

Working Agreements are created during the first sprint and remains unchanged until the product release

• True

• False

If a requirement emerges once an Agile project is running, it should be:

• Automatically included in the work of the project

• Automatically excluded and left until a later project

• Assessed for importance and, if important to the business, included in the project, displacing less important requirements

• Put onto a list for consideration by the wider group of stakeholders after the project has been completed