Chapter 35 — Capstone proposal

Chapter 35 — Capstone proposal

Lesson map

Lesson 35 published. Map, example, EX103.

flowchart TD
  N0["Learning outcomes"]
  N1["35.1 Scope and objectives"]
  N2["35.2 Tasks and risks"]
  N3["35.3 Approval"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX103"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["35.1 Scope and objectives"]
  N2["35.2 Tasks and risks"]
  N3["35.3 Approval"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX103"]

[Learning outcomes]
    |
    v
[35.1 Scope and objectives]
    |
    v
[35.2 Tasks and risks]
    |
    v
[35.3 Approval]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX103]

Learning outcomes

You will (1) define the capstone scope and objectives; (2) plan tasks, risks and evidence; (3) obtain approval.

35.1 Scope and objectives

Elena's capstone aims to improve Greenhill's identity hygiene in one cycle: raise multi-factor coverage above 95 percent, disable all leavers within one day, remove both shared accounts, reduce administrator accounts to four and remove unused paid licences. Each objective is linked to a measure from her evaluation plan. The scope covers staff, contractors and the two service accounts across six systems, and excludes the future tenant portal, which she has recorded as later work. Each objective has a named owner at Greenhill and a target date within the year.

35.2 Tasks and risks

Tasks include enrolling the repairs team with security keys, launching the HR-driven leaver job, replacing reception's shared login, reducing administrators and reviewing licences. Each task has an owner, a date and a test from her laboratories. Risks include operatives losing keys, HR dates being late and a supplier delay for repairs app sign-in. Each risk has a response, such as spare keys at the depot. The plan is realistic for her final year alongside other studies. The plan is reviewed with her supervisor every fortnight.

35.3 Approval

Elena presents the proposal to Dr Asante and Greenhill's IT lead and chief executive. They ask about disruption to repairs work and agree that enrolment will happen at the depot before shifts start. Approval is recorded in writing, together with her permission letter, now updated to cover supervised production changes made by the IT team. Formal approval protects everyone and ensures that the capstone's changes are Greenhill's decisions, carried out with Elena's support. Copies of the approval are kept by Greenhill, the university and Elena, and any later change in scope requires the same approval again.

Worked example

The approved proposal sets five measurable objectives, eleven tasks with owners and tests, and four risks with responses.

Synthetic case. Objectives, tasks and approvals are synthetic.

Errors and limits

Starting production changes without written approval blurs who decided and who is responsible.

Exercises

• EX103 — Coverage objective. What multi-factor coverage does the capstone target? Rubric: 3 = above 95 percent;; 2 = 95%;; 1 = 100%;; 0 = none.
• EX104 — Excluded item. What does the capstone scope exclude? Rubric: 3 = future tenant portal;; 2 = tenants;; 1 = finance;; 0 = none.
• EX105 — Approval update. What changed in Elena's permission letter? Rubric: 3 = covers supervised production changes by IT;; 2 = production;; 1 = vague;; 0 = none.

Synthesis

A scoped, measurable, risk-aware and approved proposal sets up the capstone for success.

Continue studying — chapter 35 of 40

← Chapter 34 (draft) · Course chapter index · Chapter 36 (draft) →