A. Collective B. Collaborative C. Connective D. Contemplative

A. May have B. Major C. Must Have D. Mandatory

A. Has no control over the prioritization of delivered features B. Has total control over the prioritization of features C. Collaborates with the developers over prioritization of features, but the developers have the final decision D. Collaborates with the developers ...

A. To produce working product of the right quality, early and incrementally B. To produce working product after documentation has been signed off C. To produce simple prototypes early, but no finished product until the end of the project D. ...

A. Do no documentation because it is a waste of time B. Do sufficient documentation to prove you have done a good job C. Do the necessary documentation to support the development and use of the product D. Do more ...

A. The Agile Leader might lose their job, as the team is doing all the work B. If the team fails, the Agile leader will not get a performance bonus C. The Agile Leader has less direct control over the ...

A. No design upfront B. Big design upfront C. Just enough design upfront D. Use a previous design – it will be “good enough”

A. It creates a better relationship between the developers and customer representatives B. Many projects are evolutionary, and a better solution emerges this way C. It is time-consuming to analyse everything at the beginning of a project D. It prevents ...

A. Teams work less well when it rains B. Keeping metrics of earlier work to help with future estimates C. Retrospectives should include less important topics, such as the weather, as ice-breakers D. Estimating is as futile as predicting the ...