A Year in Development: Nordvik Region and Hansa Mutual

All courses / AI Developer / Module 7 / Chapter 31

Learning objectives

After the lesson the participant can:

• Explain the four conclusions of the year and the events that support each
• Compare the two organisations by frame of legitimacy, rhythm, route to representatives, ceilings, drills and open items
• Review how evidence ages and expiries changed levels of delegation during the year
• Draft a ledger of commitments and plan a quarterly drill with the tools off

Key concepts

The first honest numbers were lower

The 42 per cent became 27 per cent in one sample, and a third faster became an interval that included no difference. Neither says the tools do not work; a dashboard and a survey had answered a different question from the one a senior body asked.

Evidence expired faster than it was re-measured

Claims and rehearsals lapsed on dates that were derivable on the day each record was written. When the rehearsal behind Hansa's class approval lapsed, the Level 3 Bounded class fell to Level 2 Supervised on a date nobody had to decide.

The failures that mattered were quiet

A flag silently ignored, a gap listed without an owner, a build in a repository nobody owned, a package whose name existed. No dashboard showed any of them, and each was found by a person.

Records turned disagreement into text

A senior's dissent stayed in a design record, a quality engineer's right to hold a release was in the role-boundary matrix, and a doubtful ranking went to the chief risk officer's delegate through a rule.

Year read-out

A file in version control that counts commitments as closed or open against their closing records. It reports by team, never by named developer, and contains no acceptance rates, prompt logs or appraisal data.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Teaching plan

Discussion

1. In the dark week at Nordvik Region the revert outside the pipeline missed its target, and at Hansa Mutual one tool could not be switched off. What would a week with the tools off reveal in your team?
2. The similarity is called the more important finding: in both organisations answerability sat with a named senior person. Who is that person for AI in development where you work?
3. A requirement recorded as an assumption cost 53 applicants ten days. Which of your current assumptions has neither an acceptance criterion nor an owner and a date?

Written exercise

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

1. What happened to the Level 3 Bounded class of patch-level dependency updates at Hansa Mutual when its revert rehearsal lapsed on 31 December?

   1. It was withdrawn from the delegation profile for the rest of the year
   2. It fell to Level 2 Supervised until the rehearsal was repeated in January
   3. It continued at Level 3 because the class approval was still valid
   4. It was extended to the payment path to make up for lost time
   Show the answer

   B. It fell to Level 2 Supervised until the rehearsal was repeated in January
   The rehearsal of 2 October lapsed under the 90-day rule. The class ran at Level 2 Supervised while it had lapsed and returned to Level 3 Bounded when Hansa Forge repeated the rehearsal on 8 January.

2. What does the chapter say the illustrative year can and cannot show?

   1. It shows that the instruments raise productivity by a measurable amount
   2. It shows that Hansa Mutual's approach is better than Nordvik Region's
   3. It shows that Level 4 is safe once drills are passed
   4. It can show that the instruments are workable and cannot show that they work
   Show the answer

   D. It can show that the instruments are workable and cannot show that they work
   The first caution: the year is two fictional organisations over twelve months, built from the book's records. It measures nothing, so it shows the instruments are workable and not that they work.

3. How were the quiet failures of the year found?

   1. Each was found by a person, such as an applicant who telephoned or a claims handler
   2. Each was flagged by the coding tool's own dashboard within an hour of the release
   3. Each was caught by the AI reviewer's comments on the pull request before it was merged
   4. Each was reported by the supplier under the notice clause
   Show the answer

   A. Each was found by a person, such as an applicant who telephoned or a claims handler
   The third conclusion: a silently ignored flag, a gap without an owner and a package whose name existed were shown by no dashboard. Each was found by a person and handled by an owner who could explain and revert.