Chapter 30 — Capstone assessment

Chapter 30 — Capstone assessment

Lesson map

Lesson 30 published. Map, example, EX088.

flowchart TD
  N0["Learning outcomes"]
  N1["30.1 Presentation"]
  N2["30.2 Evaluation"]
  N3["30.3 Reflection"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX088"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["30.1 Presentation"]
  N2["30.2 Evaluation"]
  N3["30.3 Reflection"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX088"]

[Learning outcomes]
    |
    v
[30.1 Presentation]
    |
    v
[30.2 Evaluation]
    |
    v
[30.3 Reflection]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX088]

Learning outcomes

You will (1) present a capstone to assessors; (2) evaluate it against criteria; (3) reflect on your development as a technologist.

30.1 Presentation

Priya presents her capstone to Mr. Lind and Riverton's operations manager. She explains the problem, the design, testing, user feedback and documentation, then demonstrates a weekly summary. The assessors ask how the tool handles missing files; she shows that it reports missing sources clearly instead of silently omitting them. They also ask how she protected patient data; she explains that the tool reads governance records only, not patient records. Mr. Lind adds that reading governance records only also keeps the tool outside the scope of patient data handling rules.

30.2 Evaluation

Assessors evaluate against criteria agreed at the start: usefulness to Riverton, correctness, maintainability, documentation and professional conduct. The operations manager reports that the summary has replaced a weekly meeting agenda and that overdue actions fell after it was introduced, though other changes also contributed. Priya receives strong marks, with a suggestion to add simple trend charts in a future version. The operations manager's caution that other changes also contributed is the same attribution limit Priya stated in her own study.

30.3 Reflection

Priya reflects on three years. She learned to see GRC as practical work: knowing assets, mapping data, estimating risks, documenting controls, watching indicators and fixing root causes. She also learned that people make governance work and that clear, respectful communication matters as much as tools. Mr. Lind notes that her habit of checking evidence before claiming success will serve her well in any role. Her refusal to mark an access review complete during her placement is one example of that habit in practice.

Worked example

Priya presents and demonstrates her capstone, is evaluated on five criteria and reflects on her development.

Synthetic case. The assessment is synthetic.

Errors and limits

Assessments sample skills. Reported improvements have several causes.

Exercises

• EX088 — Missing files. How does the tool handle missing source files? Rubric: 3 = reports them clearly;; 2 = explicit;; 1 = silent;; 0 = none.
• EX089 — Patient data. Does the tool read patient records? Rubric: 3 = no, only governance records;; 2 = no;; 1 = yes;; 0 = none.
• EX090 — Future suggestion. What did assessors suggest for a future version? Rubric: 3 = simple trend charts;; 2 = charts;; 1 = vague;; 0 = none.

Synthesis

A capstone assessment confirms practical value and reflects on growth as a GRC technologist.

Continue studying — chapter 30 of 30

← Chapter 29 (draft) · Course chapter index · Worked results ↓ · Next course via chapter index →