← Table of Contents · Page 739 of 868
PROFESSIONAL PRACTICE AND COLLABORATION
Part 14 of 14
KEY TERMS REVIEW
Governance team: the team that owns rules about permissions, data, and approvals.
Observability team: the team that owns tracing systems and dashboards.
Design-decision document: a short record of why a choice was made.
Postmortem: a blame-free written review of an incident.
Changelog: a list of changes between versions of a tool.
CHECK YOUR UNDERSTANDING
• Why get governance sign-off before writing code?
◦ Answer: Because rebuilding after a late rejection costs far more, and early review treats the team's concerns as design input.
• What are the four parts of the design-decision template?
◦ Answer: Problem, Alternatives Considered, Chosen Approach, and Reasoning.
• What makes a postmortem blame-free?
◦ Answer: It focuses on what happened and how to prevent it, not on punishing a person.
• Why use a fixed weekly schedule for reading updates?
◦ Answer: A fixed schedule makes the habit reliable, whereas reading whenever you remember leads to gaps.
• What three parts make a good status update?
◦ Answer: What is done, what is next, and what is blocking progress.
Advertisement
Read Aloud:
0:00 / 0:00