CST CST Definition of Done & Team Self-Organization 2

Question 1

What is the primary characteristic of a self-organizing Scrum Team?

Accepted Answer

Developers decide internally how best to accomplish Sprint Backlog work

Answer

The team selects its own Scrum Master each Sprint

Answer

The team chooses which Product Backlog items to prioritize

Answer

All team roles can be rotated between members each Sprint

Question 2

Which management practice most inhibits team self-organization?

Accepted Answer

Assigning tasks directly to individual Developers rather than letting the team self-assign

Answer

Providing teams with a clear Sprint Goal

Answer

Conducting regular Sprint Reviews with stakeholders

Answer

Sharing a Definition of Done across teams

Question 3

In a self-organizing Scrum Team, how are technical decisions about implementation made?

Accepted Answer

By the Developers based on their collective expertise

Answer

By the Product Owner based on business priorities

Answer

By the Scrum Master to ensure process compliance

Answer

By an external architecture review committee

Question 4

A self-managing team disagrees on a technical approach and is stuck. What is the Scrum Master's appropriate response?

Accepted Answer

Facilitate a structured discussion that helps the team reach their own decision

Answer

Make the technical decision to unblock the team immediately

Answer

Escalate the decision to the Product Owner

Answer

Tell the team to revisit the issue in the next Sprint

Question 5

Which of the following best describes a cross-functional Scrum Team?

Accepted Answer

A team that has all the skills necessary to create value each Sprint without external dependencies

Answer

A team with members from multiple departments reporting to different managers

Answer

A team that permanently handles both development and operations work

Answer

A team where specialists each own a distinct technical layer of the product

Question 6

Why does Scrum prescribe a maximum team size of 10 people?

Accepted Answer

Teams larger than 10 require too much coordination, reducing agility and communication quality

Answer

Larger teams create too many artifacts and documentation overhead

Answer

Scrum events cannot be completed in prescribed timeboxes with larger teams

Answer

Larger teams increase licensing costs for agile tooling