<!-- Generated from applied-computing-au vic/unit3-4/sat/C10-2026 by port-reference-godot-to-wiki.py — do not hand-edit; re-run the port. -->
# Recording Project Progress — a 20-Minute Practice Task

*A worked scenario for practising the three C10-3 recording techniques on somebody else's project, before you apply them to your own.*

> [!NOTE]
> **The band this serves.** C10-3, 7–8: *"Uses adjustments or logs/journals to document and explain the modifications made to the initial project plan."* The three techniques below — annotation, task adjustment, log entry — are exactly the instruments that descriptor names.

## Task Overview

**Duration:** 20 minutes  
**Skills:** SD41KS01 - Monitor, modify and annotate project plans as necessary  
**Assessment:** C10-3 preparation

## Scenario

You're the cybersecurity developer for an online quiz application used by schools. Your original project plan estimated:

- User authentication system: 2 days
- Data encryption implementation: 2 days
- Security testing and vulnerability assessment: 1 day
- **Total: 5 days**

**Reality:** It's now Day 4, and you've discovered several critical security issues that will extend your timeline significantly.

```mermaid
gantt
    title The quiz-app scenario — planned 5 days, actual 8
    dateFormat YYYY-MM-DD
    axisFormat Day %d
    section Planned
    Authentication   :p1, 2025-01-01, 2d
    Encryption       :p2, 2025-01-03, 2d
    Security testing :p3, 2025-01-05, 1d
    section Actual
    Authentication +1 (two-factor)   :crit, a1, 2025-01-01, 3d
    Encryption +1 (end-to-end)       :crit, a2, 2025-01-04, 3d
    Testing +1 (SQL injection)       :crit, a3, 2025-01-07, 2d
```

*Read the slip off the bars: every task moved by one day, and because they run in sequence the finish date moved by three. This is the picture your annotations have to explain.*


## Your Task

Apply the three project recording techniques to document what's happening:

### 1. Annotations to Project Plans

**Tool:** Create a simple Gantt chart (GitHub Projects, Excel, or hand-drawn)

**Instructions:**

- Mark your original timeline
- Add annotations showing:
    - Authentication took 3 days (not 2) due to implementing two-factor authentication for teacher accounts
    - Data encryption will need 3 days (not 2) because quiz answers require end-to-end encryption
    - Security testing needs 2 days (not 1) after discovering SQL injection vulnerabilities

**What to annotate:** Why security requirements changed, not just that they changed

### 2. Adjustments to Tasks

**Tool:** Create 3 GitHub Issues or log entries

**Record these cybersecurity task modifications:**

- **Original task:** "Basic user login system"
    
- **Modified task:** "Multi-factor authentication with role-based access (student/teacher/admin)"
    
- **Reason:** School district requires enhanced security after recent data breaches
    
- **Original task:** "Encrypt stored quiz data"
    
- **Modified task:** "Implement AES-256 encryption for data at rest and TLS 1.3 for data in transit"
    
- **Reason:** Compliance with student privacy regulations
    

### 3. Monitoring Progress Using Logs/Journals

**Tool:** OneNote page or simple document

**Create a 4-day cybersecurity progress log:**

- **Day 1:** "Basic login working, but district security officer requested two-factor authentication review"
- **Day 2:** "Implementing SMS-based 2FA, discovered need for backup codes for students without phones"
- **Day 3:** "Encryption module complete, but penetration testing revealed session hijacking vulnerability"
- **Day 4:** "Behind schedule but security compliance significantly improved - no data breach risks identified"

## Deliverables

1. Annotated cybersecurity project timeline showing changes
2. Three security task adjustment records with compliance reasoning
3. Four-day cybersecurity progress journal

## Success Criteria

✅ Demonstrates understanding of **why** security changes occurred, not just **what** changed  
✅ Shows practical application of each recording technique in cybersecurity context  
✅ Prepares evidence for C10-3 assessment requirements  
✅ Reflects real-world cybersecurity project challenges

## Reflection Questions

1. Which technique gave you the clearest picture of cybersecurity project changes?
2. How would this security documentation help you plan future cybersecurity implementations?
3. What would happen if security modifications weren't properly recorded for compliance audits?
4. Why is thorough documentation especially critical in cybersecurity projects?

## Real-World Connection

**Cybersecurity projects often require extensive documentation because:**

- Compliance audits need detailed change records
- Security incidents require traceability of all modifications
- Budget justification for extended timelines due to security requirements
- Team handovers must include complete security implementation history

---

**Assessment Connection:** This task directly prepares you for demonstrating C10-3: "Documents the modifications made to the initial project plan throughout the duration of the project" while building cybersecurity awareness.