Quality Assurance

The Quality Assurance team helps the organization deliver software that behaves as intended and remains dependable as it changes. It designs and performs checks that reveal defects, confusing behavior, missing requirements, and unintended side effects. The team works with delivery groups to clarify what good results should look like before work is considered complete. It uses a combination of exploratory testing, repeatable checks, and automated verification where that provides lasting value. The team pays attention to customer journeys as well as individual technical components. It helps identify risks that may not be visible from a developer’s perspective alone. Its findings give other teams information they can use to improve a change before it reaches users. The team also contributes to better testing practices and more consistent quality standards across the organization. It must make its feedback timely enough to support delivery rather than becoming a late-stage checkpoint. Its success is measured by useful learning, reduced escaped defects, and increased confidence in each release.

Guess the Team Type

Check one:

• ☐ Stream-aligned
• ☐ Enabling
• ☐ Complicated-subsystem
• ☐ Platform

Guess the Interaction Pattern

Check one:

• ☐ Collaboration
• ☐ X-as-a-Service
• ☐ Facilitating

Teams Supported by Quality Assurance

Check each team that you agree should be supported by Quality Assurance. Strike through, or place an X, for those that have agreed to provide your team support.

• ☐ DevOps Engineering
• ☐ Storefront Development
• ☐ Cyber Security
• ☐ Finance Support
• ☐ Database
• ☐ Infrastructure
• ☐ Product Catalog Dev
• ☐ Bakery Development

Manager Notes

Record any of your decisions here as needed...