Plan my session
Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.
Session: Goal Question Metric
The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.
Method session with 3-6. The plan uses the existing method logic and the runsheet.
RunsheetUse the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.
The session works directly toward GQM-Tabelle. After the session, the artifact should be shareable, reviewable, or reusable.
- 1
Phase 1: Clarify goals
30 minFor each goal, add detail in Basili's goal template: object, purpose, quality aspect, viewpoint, context. Example: reduce Mean Time to Restore for Service X from the Operations team perspective in production. Hint: If a goal falls apart during clarification, split it instead of keeping it vague. Vague goals create vague metrics.
FacilitatorGQM-Tabelle - 2
Phase 2: Derive probing questions
45 minFor each goal, formulate 3-6 questions that must be answered to assess progress. Questions must be answerable with evidence, not opinion. Hint: If a question is not answerable without assumptions, it is too abstract. Example instead of Are we fast enough: How long does a typical restore take in P95?
FacilitatorMetrik-Steckbriefe - 3
Phase 3: Metrics per question
45 minFor each question name 1-2 metrics that answer it. For each metric document data source, calculation, aggregation, cadence, and owner. Hint: No metric should appear in two questions without justification. Duplicated metrics usually indicate a too broad question.
FacilitatorGQM-Tabelle - 4
Phase 4: Clean existing set
30 minRun all existing metrics through the GQM grid. Mark metrics without a question as Orphan and set a deadline for deactivation or attachment. Hint: Do not tolerate orphan metrics silently. They are the main source of metric sprawl and conflicting reports.
FacilitatorMetrik-Steckbriefe - 5
Phase 5: Briefs and cadence
30 minCreate a brief for each metric with definition, source, calculation, thresholds, and owner. Define review cadence (for example monthly, quarterly). Hint: Without a metric brief, a metric is just a number on a dashboard. It becomes necessary as soon as there is a disagreement about meaning.
OwnerGQM-Tabelle - 6
Publish artifact
10 minCheck the artifact for completeness, define location, set version or status, and name review recipients.
OwnerGQM-Tabelle
Session Brief
For invitations, boards, tickets, PR descriptions, or workshop notes.
session-brief.md
Session Brief: Goal Question Metric
Goal
Artifact: GQM-Tabelle
Working Question
Which questions must we be able to answer to know whether we are reaching our goal, and which metric answers each question?
Context
Current goals in short form; existing dashboards and reports with rough coverage; known metric pain points (for example contradictory figures); list of available data sources.
Setup
- Format: Method session
- Duration: 2-3 h
- Mode: Workshop
- Participants: A measurement program owner (Engineering Manager, Product Lead, or Data Lead); 2-4 people who produce and consume the data; a Data Analyst for source and calculation questions.
- Owner: A measurement program owner (Engineering Manager, Product Lead, or Data Lead)
- Participation mode: Team round, shared work and alignment
- Outcome logic: Finish artifact
Participation Logic
Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.
Outcome Logic
The session works directly toward GQM-Tabelle. After the session, the artifact should be shareable, reviewable, or reusable.
Input
GQM table (Goal, Question, Metric, source, owner, cadence); current team metric inventory; template for metric briefs; whiteboard or Miro board.
Preparation
Prepare the table in three sections: Goals at top, then Questions, then Metrics. Set the rule: no metric without question, no question without goal. Add a separate Orphan Metrics section for items without anchor connection.
Agenda
-
Phase 1: Clarify goals (30 min) Owner: Facilitator Action: For each goal, add detail in Basili's goal template: object, purpose, quality aspect, viewpoint, context. Example: reduce Mean Time to Restore for Service X from the Operations team perspective in production. Hint: If a goal falls apart during clarification, split it instead of keeping it vague. Vague goals create vague metrics. Output: GQM-Tabelle
-
Phase 2: Derive probing questions (45 min) Owner: Facilitator Action: For each goal, formulate 3-6 questions that must be answered to assess progress. Questions must be answerable with evidence, not opinion. Hint: If a question is not answerable without assumptions, it is too abstract. Example instead of Are we fast enough: How long does a typical restore take in P95? Output: Metrik-Steckbriefe
-
Phase 3: Metrics per question (45 min) Owner: Facilitator Action: For each question name 1-2 metrics that answer it. For each metric document data source, calculation, aggregation, cadence, and owner. Hint: No metric should appear in two questions without justification. Duplicated metrics usually indicate a too broad question. Output: GQM-Tabelle
-
Phase 4: Clean existing set (30 min) Owner: Facilitator Action: Run all existing metrics through the GQM grid. Mark metrics without a question as Orphan and set a deadline for deactivation or attachment. Hint: Do not tolerate orphan metrics silently. They are the main source of metric sprawl and conflicting reports. Output: Metrik-Steckbriefe
-
Phase 5: Briefs and cadence (30 min) Owner: Owner Action: Create a brief for each metric with definition, source, calculation, thresholds, and owner. Define review cadence (for example monthly, quarterly). Hint: Without a metric brief, a metric is just a number on a dashboard. It becomes necessary as soon as there is a disagreement about meaning. Output: GQM-Tabelle
-
Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: GQM-Tabelle
Closeout
- Update result artifact: GQM-Tabelle
- Define location, version, and review recipients.
- Define owner, next step, and review date.
Work artifact
Pre-filled starting point based on the matching template.
work-artifact.md
GQM-Tabelle: Goal Question Metric
Working Question
Which questions must we be able to answer to know whether we are reaching our goal, and which metric answers each question?
Context
Current goals in short form; existing dashboards and reports with rough coverage; known metric pain points (for example contradictory figures); list of available data sources.
Participants
- Owner: A measurement program owner (Engineering Manager, Product Lead, or Data Lead)
- Participants: A measurement program owner (Engineering Manager, Product Lead, or Data Lead); 2-4 people who produce and consume the data; a Data Analyst for source and calculation questions.
Input
GQM table (Goal, Question, Metric, source, owner, cadence); current team metric inventory; template for metric briefs; whiteboard or Miro board.
Template
Goal Question Metric Working Template
Goal
Derives metrics from goals and probing questions.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- GQM table:
- Metric profiles:
Assumptions and open questions
- ...
Decision / next step
Owner, date, and success signal.
Completion Check
- GQM-Tabelle is complete enough for review:
- Location:
- Version / status:
- Review by:
- Next step:
Next Step
- Review result
- Mark open questions
- Schedule review or decision
Goal Question Metric Working Template
View templateCompact working template for Goal Question Metric with context, input, output artifacts, and next step.markdown
goal-question-metric-working-template.md
Compact working template for Goal Question Metric with context, input, output artifacts, and next step.
Goal Question Metric Working Template
Goal
Derives metrics from goals and probing questions.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- GQM table:
- Metric profiles:
Assumptions and open questions
- ...
Decision / next step
Owner, date, and success signal.
- Working question, owner, and target artifact are visible.
- The result fits GQM-Tabelle.
- Semiannual snapshot with date. Changes to metric definitions with rationale in edit log; do not overwrite older definitions. Keep deactivated metrics with status retired and date.
- Open questions are noted as follow-ups.
- The next review or decision point is scheduled.