A. It should be encouraged to celebrate success only when the project is over B. It should be encouraged to celebrate even small successes immediately C. It should not celebrate success, as this wastes project budget D. It should not ...

A. Occasional early deliveries, if the business is prepared to accept lower quality B. A regular pattern of delivery of developer-focused products C. A regular pattern of delivery of business-valued increments D. An irregular and unpredictable delivery of products

A. Should have no control over its progress B. Should be able to demonstrate control of its progress C. Is always out of control D. Is controlled by the velocity of the most junior team member

A. Plans should never be changed B. It is normal to need to plan and re-plan as the project progresses C. Plans should only be changed with full approval of all stakeholders D. Plans are not required as Agile is ...

A. It allows the team to take a necessary break from work B. It gives management information to use in team members’ performance reviews C. It allows learning which can be used to improve team performance during the project D. ...

A. The energy level and velocity of the team B. The remaining work (effort, points) to complete before the iteration (timebox) end C. The number of hours worked by each team member during the iteration (timebox) D. The rate of ...

A. If the team members work long hours regularly they will get used to it, and be able to sustain it B. A 40 hour week is only for the weaker members of the team. Others can do more. C. ...

A. Courage to change and adapt B. Trust of fellow team members to do the work C. Responsiveness to change D. All of these

A. People are more important than contracts B. Working software should have priority over comprehensive documentation C. Plans should have priority over ability to respond D. Contracts should be negotiated which allow control over the people

A. Directive B. Assertive C. Facilitative D. Feature-based