Quality Culture Assessment Worksheet
Metadata
| Field | Value |
|---|---|
| Worksheet title | Quality Culture Assessment Worksheet |
| Related chapter | Chapter 7 — Engineering Culture & DevOps Mindset |
| Part | Part I — Foundations of Modern Software Quality Engineering |
| MQE-BOK domain | Domain 1 — Foundations of Modern Software Quality Engineering |
| Difficulty | Foundation |
| Estimated time | 35–50 minutes |
| Version | 0.1.0 |
| Status | Draft |
Purpose
Help a delivery team discuss the behaviours and conditions that enable quality. The worksheet is a qualitative reflection and improvement tool; it is not a maturity model, performance rating, certification, or organisational score.
QE Capability Developed
Collaboration analysis, evidence-based improvement planning, quality-culture facilitation, and constructive risk communication.
Prerequisites
- Read Chapter 7 and review the Quality Culture Flywheel.
- Use an illustrative scenario, a safely anonymised team context, or the Northstar Claims scenario in Chapter 7.
Instructions
1. Set the discussion boundary
| Prompt | Your response |
|---|---|
| Team, service, or illustrative scenario | |
| Customer outcome to protect | |
| Recent decision, change, incident, or delivery challenge | |
| Participants or perspectives represented | |
| Missing perspective to acknowledge |
2. Assess qualitative evidence
Use Strong, Developing, or Needs Attention to prompt discussion. The label is not a score and should always be supported by observed evidence.
| Area | Qualitative view | Observed evidence | Risk if unchanged | Question to explore |
|---|---|---|---|---|
| Ownership | ||||
| Accountability and decision rights | ||||
| Collaboration across roles | ||||
| Psychological safety | ||||
| Feedback speed and usefulness | ||||
| Incident learning and follow-through | ||||
| Quality metrics | ||||
| Incentives and local optimisation | ||||
| Decision transparency | ||||
| Continuous improvement capacity |
3. Identify strengths, risks, and improvements
| Observed strength to preserve | Quality or delivery risk | Recommended improvement | Owner and collaborators | Evidence that progress is occurring |
|---|---|---|---|---|
4. Create a 90-day experiment plan
Choose no more than three improvements. Include one action for shared context, one for feedback or learning, and one for sustainable follow-through.
| Period | Improvement objective | Concrete action | Safeguard or dependency | Review evidence |
|---|---|---|---|---|
| Days 1–30 | ||||
| Days 31–60 | ||||
| Days 61–90 |
Expected Outputs
- qualitative culture evidence across ten areas;
- observed strengths and risks;
- three or fewer prioritised improvements; and
- a 90-day experiment plan with evidence and review points.
Portfolio Relevance
This is usually an internal team-learning artefact rather than a public portfolio item. A learner may create a fictional or strongly anonymised facilitation example to demonstrate Quality Engineering leadership. Do not publish colleague feedback, incident details, internal metrics, or employer-specific culture assessments.
Reflection Questions
- Which behaviour most slows the discovery or use of quality evidence?
- Which metric or incentive could reward activity while harming the customer outcome?
- Where is accountability unclear, and where is it mistakenly concentrated in one role?
- What evidence would show that an improvement changed team behaviour rather than only meeting attendance?
Completion Criteria
- Every qualitative assessment includes evidence rather than a score alone.
- At least one strength and one risk are identified.
- The improvement plan has no more than three actions.
- Each action has an owner, a review point, and evidence of progress.
- The assessment is not presented as a maturity rating or certification result.