先試後買

A. That any team member can do any of the tasks in the sprint

B. That the team has team members in each of the Scrum roles

C. That together the team members have all stalls necessary

D. That the team makes their own decisions on how they work

A. One who wants to explore how other project tackled similar issues and improved processes

B. One who wants to listen to everything and choose what he takes away from the retrospective

C. One who wants to participate in and learn everything discussed in the retrospective

D. One who wants to relax and be a tourist during the retrospective

A. Sprint Planning

B. Backlog Maintenance

C. Sprint Review

D. Sprint Retrospective

E. Daily Scrum

F. Sprint

A. The Developers

B. The Scrum Master

C. The Product Owner

A. Because small teams usually have Developers with similar backgrounds and technical capabilities which speeds up communication

B. Because small teams are less likely to form sub-groups everyone's contribution is more visible and coordinating is easier

C. Because small teams can switch between different projects each sprint more easily, which helps add the most business value

A. Splitting the User Story into separate CRUD operations

B. Splitting the User Story into Epics

C. Do not split. The User Story is small enough

D. Splitting the User Story into tasks

A. Present Rate of Return

B. Estimated Rate of Return

C. Net Rate of Return

D. Internal Rate of Return

A. Deliverables are improved progressively by time-boxing non-essential work

B. Continuous feedback is provided through the Groom Prioritized Product Backlog process

C. The Conduct Daily Standup process leads to greater levels of motivation among team members.

D. Emphasis on risk mitigation and detailed planning ensures a customer-oriented framework.