Quiz — Chapter 40: Knowledge Transfer and Mentoring

Question 1

According to the chapter, what percentage of the mainframe workforce is eligible for retirement within the next five years?

A) Approximately 15% B) Approximately 25% C) Approximately 40% D) Approximately 60%

Answer: C

Explanation: Section 40.1 states that approximately 40% of the mainframe workforce is eligible for retirement within the next five years. Combined with the fact that the pipeline of new talent replaces fewer than 20% of anticipated retirements, this creates the knowledge crisis described throughout the chapter.

Question 2

Which of the following is the BEST example of tacit knowledge as described in this chapter?

A) The JCL parameters for a batch job B) The DB2 table structure of the claims database C) Knowing which IBM support engineer to request for a specific type of problem D) The contents of the operations runbook

Answer: C

Explanation: Section 40.1 defines tacit knowledge as expertise that lives in a person's head — intuition, judgment, and contextual understanding from years of experience. Knowing which IBM support engineer to request is relationship knowledge that cannot be captured in documentation and exists only in the experienced professional's memory. Options A, B, and D are all forms of explicit knowledge that can be written down.

Question 3

What is the fundamental reason that "documentation alone fails" as a knowledge transfer strategy?

A) Documentation is too expensive to produce B) Senior professionals refuse to write documentation C) Expert knowledge includes tacit elements that cannot be fully articulated in writing D) Modern tools make documentation obsolete

Answer: C

Explanation: Section 40.2 explains, referencing Michael Polanyi's observation that "we can know more than we can tell," that expert knowledge includes tacit elements — judgment, intuition, pattern recognition, contextual understanding — that cannot be fully captured in written documentation. Documentation is necessary but fundamentally insufficient for transferring the full range of expert knowledge.

Question 4

In the knowledge spectrum described in Section 40.2, which of the following is positioned furthest toward the "fully tacit" end?

A) Architecture documents B) Troubleshooting heuristics C) Judgment under pressure D) Code

Answer: C

Explanation: The knowledge spectrum in Section 40.2 places "judgment under pressure" and "gut feel about system health" at the fully tacit end of the spectrum. Troubleshooting heuristics are partially explicit (they can be discussed but not fully documented). Architecture documents and code are fully explicit. Judgment under pressure encompasses the most deeply embedded form of expert knowledge.

Question 5

According to the chapter, what is the single most effective method for transferring tacit technical knowledge?

A) Written documentation B) Recorded video sessions C) Pair programming D) Formal classroom training

Answer: C

Explanation: Section 40.3 explicitly states that "pair programming — where two developers work together at one workstation, one driving and one observing/advising — is the single most effective method for transferring tacit technical knowledge." This is because it allows the junior developer to absorb the reasoning behind decisions, not just the outcomes, in the context of real work.

Question 6

What is the recommended session length for mainframe pair programming sessions focused on knowledge transfer?

A) 30 minutes to 1 hour B) 2 to 4 hours C) Full day (8 hours) D) No specific recommendation — as long as needed

Answer: B

Explanation: Section 40.3 recommends pair programming sessions of 2–4 hours, noting that longer sessions cause fatigue and shorter sessions do not allow enough depth. The sessions should include role rotation, with the senior developer driving first while explaining their thought process, then switching so the junior developer drives while the senior developer guides.

Question 7

Yuki Tanaka's "Knowledge Tapes" program at SecureFirst Insurance involves:

A) Transcribing all COBOL code into modern languages B) Recording senior professionals explaining systems, business rules, and edge cases C) Creating video tutorials for new hires on basic mainframe operations D) Taping actual production support calls for training purposes

Answer: B

Explanation: Section 40.3 describes Yuki Tanaka's Knowledge Tapes as a program where senior developers spend an hour recording explanations of specific topics — system walkthroughs, business rules, edge cases, and historical context. Carlos's 90-minute recording on the insurance rating engine was viewed 47 times and became the most accessed resource in their internal knowledge base.

Question 8

According to the chapter, what are the three characteristics of documentation that actually works for knowledge transfer?

A) Brevity, accuracy, visual appeal B) Capturing the "why," maintained as part of work, and discoverable C) Comprehensive, reviewed annually, and stored in the code repository D) Written by architects, reviewed by developers, and approved by management

Answer: B

Explanation: Section 40.4 identifies three characteristics: (1) it captures the "why" — the reasoning behind decisions, not just the decisions themselves; (2) it is maintained as part of the work, not as a separate activity; and (3) it is discoverable through consistent structure, clear naming, and searchable repositories. These three characteristics distinguish effective documentation from the documentation that "most organizations produce and nobody reads."

Question 9

What is the primary advantage of retroactive ADRs (Architecture Decision Records written for past decisions)?

A) They satisfy audit requirements B) They capture decision-making context that would otherwise be lost when the decision-maker retires C) They are easier to write than forward-looking ADRs D) They help standardize future decision-making processes

Answer: B

Explanation: Section 40.4 emphasizes that retroactive ADRs capture the reasoning behind historical decisions that currently exists only in senior professionals' memories. Marcus's example of writing ADRs for thirty past decisions illustrates this: "Some of them, I'm the only person alive who knows the reasoning." Without these retroactive ADRs, the context behind critical design decisions would be permanently lost upon retirement.

Question 10

What is "reverse mentoring" and why is it valuable in the mainframe context?

A) Mentoring that flows from managers to individual contributors, reversing the usual direction B) Junior professionals mentoring senior professionals in modern technologies, building mutual respect C) Senior professionals deliberately making mistakes for juniors to correct, reversing the teaching dynamic D) Mentoring relationships that move from informal to formal, reversing the typical progression

Answer: B

Explanation: Section 40.5 describes reverse mentoring as junior professionals mentoring senior professionals — particularly in modern technologies like Git, CI/CD, cloud, and automated testing. It is valuable because it builds mutual respect across generations, demonstrates that learning flows in both directions, and helps senior professionals understand the perspectives of younger colleagues. Kai Nakamura's reverse mentoring of Marcus Whitfield on Git and CI/CD is the chapter's primary example.

Question 11

When Diane Kowalski at Pinnacle Health restructured her team from two separate groups into three cross-generational teams, what was the initial result?

A) Immediate productivity improvement B) A chaotic first month, followed by natural knowledge transfer by the third month C) Several resignations from senior developers who resisted the change D) No measurable impact for the first year

Answer: B

Explanation: Section 40.5 quotes Diane describing the transition: "The first month was chaotic. By the third month, the knowledge transfer was happening naturally — the senior developers were explaining business logic while the newer developers were teaching them about API design. By the sixth month, every team was more capable than either of the original teams." This illustrates that cross-generational teams require patience through an initial adjustment period.

Question 12

In Marcus's knowledge transfer plan, how does he categorize his knowledge items?

A) Technical, Business, Organizational B) Easy, Medium, Hard C) Critical, Important, Useful D) Urgent, Non-urgent, Optional

Answer: C

Explanation: Section 40.7 describes Marcus's three-tier categorization: CRITICAL (17 items — system will fail or produce wrong results without this knowledge), IMPORTANT (31 items — significant efficiency loss or increased risk), and USEFUL (24 items — helpful but not essential). This prioritization ensures the most essential knowledge is transferred first.

Question 13

How long does Marcus's knowledge transfer plan span, and what are its five phases?

A) 12 months: Document, Train, Test, Transfer, Exit B) 24 months: Inventory, Critical Transfer, Important Transfer, Validation, Graceful Exit C) 18 months: Assessment, Planning, Execution, Review, Completion D) 36 months: Preparation, Documentation, Mentoring, Transition, Retirement

Answer: B

Explanation: Section 40.7 lays out Marcus's 24-month plan in five phases: Phase 1 — Inventory (months 1–2), Phase 2 — Critical Knowledge Transfer (months 3–10), Phase 3 — Important Knowledge Transfer (months 8–18), Phase 4 — Useful Knowledge and Validation (months 18–22), and Phase 5 — Graceful Exit (months 22–24). The two-year timeline reflects the chapter's assertion that this is the minimum for comprehensive knowledge transfer from a deeply experienced professional.

Question 14

What does the chapter identify as the key element that distinguishes a "Community of Practice" from a regular team meeting?

A) Communities of Practice are always virtual B) They are organized around a shared domain of interest with rotating presentations and practical focus C) They require management approval for every session D) They are limited to senior professionals only

Answer: B

Explanation: Section 40.6 describes Communities of Practice as groups organized around a shared domain of interest (a technology, practice, or cross-cutting concern) that meet regularly with rotating presentations, practical focus on real problems, and documented outcomes. Unlike regular team meetings, CoPs cross team boundaries and focus on knowledge sharing rather than operational coordination.

Question 15

In the emotional closing of Section 40.7, what does Marcus realize about his thirty-eight years of work when he creates his "Things I Know That Nobody Else Knows" list?

A) That he should have retired sooner B) That documentation is sufficient to capture everything he knows C) That his knowledge is not just information but represents the work of his life — and he wants to ensure it is not lost D) That the system should be replaced rather than maintained

Answer: C

Explanation: Section 40.7 captures Marcus's realization: "This system, these programs, these processes — they're not just code. They're the work of my life. Thirty-eight years of decisions, compromises, late nights, and small victories. When I walk out that door, a part of me stays in this system. And I want to make sure it's not lost." This emotional dimension — recognizing that knowledge transfer is about honoring a career, not just extracting information — is central to the chapter's closing message.