Chapter 12 — Practice portfolio and final review
Lesson map
Lesson 12 published. Map, example, EX056.
flowchart TD
N0["Learning outcomes"]
N1["12.1 Portfolio"]
N2["12.2 Assessment"]
N3["12.3 Reflection"]
N4["12.4 Next steps"]
N5["12.5 Closing the audit"]
N6["Assessor feedback"]
N7["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX056"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["12.1 Portfolio"]
N2["12.2 Assessment"]
N3["12.3 Reflection"]
N4["12.4 Next steps"]
N5["12.5 Closing the audit"]
N6["Assessor feedback"]
N7["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX056"]
[Learning outcomes]
|
v
[12.1 Portfolio]
|
v
[12.2 Assessment]
|
v
[12.3 Reflection]
|
v
[12.4 Next steps]
|
v
[12.5 Closing the audit]
|
v
[Assessor feedback]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX056]
Learning outcomes
You will (1) assemble a portfolio of evidence; (2) reflect on growth; (3) plan continued practice.
12.1 Portfolio
Hannah's portfolio includes her authority brief, method note, role analysis, triage, verification evidence, the exception, reports and rehearsal records. Each item shows a different competence: the brief shows working within authority, the method note shows planning, the analyses show technical skill, the verification evidence shows care, and the reports show communication. Hannah arranges the portfolio in the order of the work, so assessors can follow the project from start to finish. Each item is dated and linked to the evidence register. The course moved from foundations and context, through authority and methods, to tools, workflow, verification, case analysis, communication, quality, rehearsal and portfolio. Each step used evidence from the previous one.
12.2 Assessment
Kingsbridge assessors check that each item shows applied competence with evidence. Assessors look for evidence that the method was applied at work, not just described. They check that the role analysis matches the exports, that verification used fresh evidence and that the exception was handled properly. They may ask Hannah to explain any item. The assessment criteria are published by Kingsbridge, and Hannah maps each portfolio item to the criteria before submitting it, so assessors can find the evidence for each one.
12.3 Reflection
Hannah notes her strength in careful verification and her growth in stakeholder communication. Her careful verification showed in the fresh evidence for every change and in the colleague's repeat of the role analysis. Her growth in communication came from meeting stakeholders, writing three versions of the report and answering councillors' questions. She also notes a mistake she learned from: relying on action names in logs without mapping them to permissions. Writing the reflection helps her plan what to develop next.
12.4 Next steps
She plans to extend role reviews to the council's other cloud services. Elmstead runs other services on the same cloud platform, and their roles have probably grown in the same way as the permit service's. Hannah proposes starting with the service that holds the most sensitive data, using the method note and the quarterly review routine. Dev agrees to include the proposal in the platform team's plan for the next year. She also plans to share the method with the digital team so they can run reviews themselves. Hannah will keep the quarterly role reviews and weekly triage, track Kubernetes release notes for changes to security features, and revisit the CIS Benchmark when new versions appear.
12.5 Closing the audit
The reporting rebuild closes after two weeks; audit closes both findings. Once the library was updated, the reporting image was rebuilt and scanned again, and the exception was closed. Audit received the final evidence and closed both findings within the three-month target agreed at the start. Hannah records the closure in her portfolio and in the final fortnightly update, so every stakeholder knows the project is complete. Dev thanks the digital team and the parking team for their patience during changes, and the quarterly role review and weekly triage continue as normal work. All work stayed within written authority, using synthetic data for the course labs and read-only access for evidence. She thanks Dev, the digital team and audit. Hannah begins her new cloud security role, starting with housing, with the method, the evidence habits and a team that trusts the process.
Assessor feedback
The assessors note that Hannah's portfolio links every claim to evidence and that her exception for the reporting rebuild shows honest judgement rather than forcing a closure. They suggest she write a short guide for other councils, anonymised, as a contribution to the profession.
Dev's feedback highlights that the stakeholder meetings prevented resistance and that the digital team now asks Hannah for advice before adding permissions.
Worked example
An assessor asks which habit mattered most. Hannah says confirming with owners before removing anything.
Synthetic case. Synthetic.
Errors and limits
A portfolio shows evidence; reflection explains it.
Exercises
- EX056 — Portfolio items. List four portfolio items. Rubric: 3 = brief, method, analysis, triage, verification, exception, reports, rehearsal; 2 = four; 1 = two; 0 = none.
- EX057 — Strength. What strength did Hannah identify? Rubric: 3 = careful verification; 2 = partial; 1 = vague; 0 = none.
- EX058 — Growth. Where did she grow? Rubric: 3 = stakeholder communication; 2 = partial; 1 = vague; 0 = none.
- EX059 — Audit closure. When did audit close the findings? Rubric: 3 = after reporting rebuild; 2 = partial; 1 = vague; 0 = none.
- EX060 — Key habit. Which habit mattered most? Rubric: 3 = confirm with owners before removing; 2 = partial; 1 = vague; 0 = none.
Synthesis
Evidence plus reflection shows professional competence.
Continue studying — chapter 12 of 12
← Chapter 11 (draft) · Course chapter index · Worked results ↓ · Next course via chapter index →