Quality Engineering Portfolio Evidence Map
Metadata
| Field | Value |
|---|---|
| Worksheet title | Quality Engineering Portfolio Evidence Map |
| Related chapters | Chapters 8 and 10 |
| Related project document | QA to Quality Engineering Transition Framework |
| Part | Part I — Foundations of Modern Software Quality Engineering |
| MQE-BOK domain | Domain 1 — Foundations of Modern Software Quality Engineering |
| Difficulty | Foundation |
| Estimated time | 20–30 minutes |
| Version | 0.1.0 |
| Status | Draft |
Purpose
Connect learning activity to demonstrable Quality Engineering capability. The map helps a learner plan and explain evidence; it does not require creating every future technical project now.
QE Capability Developed
Evidence curation, portfolio planning, reflective learning, and communication of engineering contribution.
Prerequisites
- Read the Portfolio Strategy section of the QA to Quality Engineering Transition Framework (not available in this preview).
- Optionally complete the competency self-assessment and personal transition plan.
Instructions
1. Map planned or existing evidence
Use the map for work that you can describe safely. An item does not need to be public to count as evidence; where work is confidential, record the problem, approach, decision, and outcome at an appropriate level of abstraction.
| Competency | Learning Activity | Artifact Produced | Repository or Portfolio Evidence | Capability Demonstrated | Improvement Needed |
|---|---|---|---|---|---|
2. Identify future evidence opportunities
Examples of future evidence may include:
- an automation framework improvement;
- an API quality suite;
- SQL validation or a data-integrity check;
- a CI pipeline contribution;
- a performance analysis;
- an observability investigation;
- an AI evaluation project;
- a risk-based quality strategy; or
- a Quality System Map.
Do not create these technical projects as part of this worksheet. Select only the next evidence opportunity that fits your current learning plan and context.
| Candidate evidence opportunity | Capability it could demonstrate | Context or problem to use | Safe first step | Feedback source |
|---|---|---|---|---|
3. Make the evidence explainable
For each priority artefact, prepare a concise explanation.
| Context | Risk or decision | Your contribution | Evidence and result | Limitation and learning |
|---|---|---|---|---|
Expected Outputs
- a map from learning activities to demonstrable capability;
- one or two prioritised future evidence opportunities; and
- concise, interview-ready explanations of selected artefacts.
Portfolio Relevance
This worksheet is a planning artefact. The evidence it maps may become Portfolio Candidates when it can be shared safely and explains context, risk, contribution, result, limitation, and learning. Never publish secrets, customer data, internal identifiers, private source code, or commercially sensitive details.
Reflection Questions
- Which artefact best demonstrates engineering reasoning rather than tool familiarity?
- Which capability claim has the weakest evidence today?
- What confidential detail must be removed or abstracted before an artefact can be shared?
- Which small next project would produce the highest-value evidence for your target capability?
Completion Criteria
- At least three learning activities or artefacts are mapped to capability.
- One or two future opportunities are prioritised without starting those projects here.
- Each selected artefact has an explainable context, risk, contribution, evidence, and limitation.
- Confidentiality and safe-sharing constraints are recorded.