Quality of product and process is the responsibility of everyone on the
team. It is the result of discipline, communication, and the use of good
engineering practices.

An impediment is any technical, personal, or organizational issue
that inhibits progress being made on delivering product to the
customer. Impediments are inevitable. It is always the responsibility
of the team to expose impediments as they arise rather than burying
them, hoping they will go away. The team is responsible for resolving
impediments that lie within its “span of influence” (within which it can
effect change). The Team Agility Coach, acting on behalf of the team,
elevates all other impediments to management to be addressed. The
and other management agree to help.

In both object-oriented and procedural code, assessing the quality of
software can be difficult. Oftentimes, it involves a conversation among
the development team as they think together about the code.

Resources related to quality

Acceptance Test-Driven Development (Article)
Acceptance Test-Driven Development: A Quick Introduction (Blog Entry)
Are We Using Automated Acceptance Tests? (Article)
Do We Have So Much Technical Debt That We Need to Pay Some Down Before Proceeding? (Article)
Guardrails (Article)
How Is Integration Across Teams Being Handled? (Article)
How Will We Create Visibility Throughout the Program? (Article)
How Will We Make Visible Our Work at the Program Level? (Article)
Impediments to Progress and Quality (Article)
Improve the Efficiency of the Technology Group (Article)
Issues With Quality (Article)
Product Demonstration and Review - Plan (Article)
Product Planning and Review - Conduct (Article)
Recommended Resources - Facilitation (Article)
Scrum of Scrums (Article)
To What Extent Will Test-First Methods Be Used? (Article)
To What Extent Will We Automate Tests? (Article)
Types of Tests for Code (Article)
What Test Harness for Acceptance Tests Will Be Used? (Article)