This set builds vocabulary for collaborative team documentation and knowledge sharing.
0 / 5 completed
1 / 5
At standup, a dev mentions the shared, collaboratively editable page where the team documents a technical design before implementation begins. What type of tool is this?
A team wiki like Confluence provides shared, collaboratively editable pages for documenting things like technical designs, meeting notes, or onboarding guides, keeping institutional knowledge centralized and searchable rather than scattered across private files. This shared documentation supports team-wide visibility and historical reference. It's a standard tool for maintaining living documentation alongside a codebase.
2 / 5
During a design review, the team wants to see who changed a specific section of a design doc and when, to understand how a decision evolved. Which feature supports this?
Page version history tracks every edit made to a document over time, letting the team see who changed what and when, and revert to a prior version if needed. This transparency helps reconstruct how a decision evolved through discussion and revision. It mirrors the value of commit history in version control applied to prose documentation.
3 / 5
In a code review, a dev links a design document directly to its corresponding Jira epic so context stays connected across tools. What does this integration support?
Linking a documentation page to its corresponding epic or ticket preserves traceability, letting anyone reviewing the work trace from the high-level design rationale to the specific tracked implementation tasks and back. This connective tissue between tools prevents context from becoming siloed. Many teams rely on this kind of integration between a wiki and an issue tracker as a standard workflow.
4 / 5
An incident report shows a team implemented a feature based on an outdated design doc that had been superseded by a newer decision documented elsewhere. What practice would prevent this?
When a design decision changes, clearly marking the old document as deprecated and pointing to the current authoritative version prevents someone from later acting on stale information. Leaving outdated docs indistinguishable from current ones is a common source of confusion in team wikis over time. This upkeep practice is essential for keeping a growing documentation base trustworthy.
5 / 5
During a PR review, a teammate asks why the team documents design decisions in a shared wiki instead of just discussing them verbally or in chat. What is the reasoning?
A verbal or chat-based discussion is ephemeral and hard to search or reference later, while a documented decision in a shared wiki remains accessible, versioned, and discoverable for anyone who joins the project later or simply forgot the details. This persistence is especially valuable for onboarding and long-term institutional memory. Written documentation complements, rather than replaces, real-time discussion.