A. Sponsor and Executive Management only B. Project Manager and Technical Leads only C. Project Leader and Customer Representatives only D. The entire team

A. Everyone is expected to stand for the whole time, to keep the meeting short B. The meeting must be kept short and well structured C. The meeting should ensure that it is clear to all which team members are ...

A. All project stakeholders should attend requirements workshops B. Retrospectives are only run at the end of a project C. It is best if the Project Manager facilitates the project’s workshops D. An independent facilitator will manage the structure of ...

A. The team should plan to work a small amount of overtime regularly throughout the project B. The team should expect to work longer hours towards the end of the sprint (timebox), in order to deliver all that was committed ...

A. Get something “quick and dirty” delivered, to save time B. Get something simple released as quickly as possible C. Get something business-valuable delivered as quickly as possible, consistent with the right level of quality D. Get something delivered once ...

A. A big design upfront is always a good idea B. Just enough design up front gives a good foundation to start from and helps to mitigate risk, without wasting unnecessary time C. No design upfront is the best approach ...

A. The team should allow only senior managers to sign off deliverables B. The team should get acceptance of project deliverables from the appropriate stakeholders at least at the end of every timebox / iteration C. The team should get ...

A. The products produced by an Agile project should be cheaper than those produced by any other approach, but quality will suffer B. The products will be more expensive than by any other approach but will be top quality C. ...

A. Empower the team members, within appropriate limits B. Encourage an environment of competition and personal advantage C. Give clear directives to the team about what they should do and how D. Expect team members to be proactive and each ...

A. System documentation created at the end of each increment, at the start of the deployment B. User Stories held in a spreadsheet or specialist database, where full details of user conversations are recorded for future purposes, like handover to ...