Home A - Z
Page Index

An Otter Wiki

Blame

5c1696 lisa 2026-08-29 16:39:27
Add sd/C10: hub + guides for the in-class model Seven curated learning pages plus the C10 home hub, generated by the shared port script (new c10 config): the C100-* cluster, the tick sheet, the solutions booklet and the assessment paperwork stay out of the wiki. Each page gains a skill title, a lead naming the rubric band it serves, one earned mermaid visual and a Check Your Understanding fold. The git-log examples are anonymised (prior-cohort names, hostnames and repo URL removed). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RxqgYbTNNYrPNuko6xfbKs
1 
<!-- 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. -->
2
# Assessing the Effectiveness of Your Project Plan
3
4
*The C10-4 judgement: was the plan any good, and how do you know? Read it before class write 3, side B.*
5
6
> [!NOTE]
7
> **The bands this serves.** C10-4, 5–6: *describes the reasons why changes were made and how they impacted the effectiveness of the plan*. 7–8: *discusses how the changes impacted the completion of the project and the effectiveness of the plan*. 9–10: *evaluates the changes, **with evidence**, and how they impacted completion and overall effectiveness*. The words "with evidence" are why C10-3's record decides your C10-4 mark.
8
9
```mermaid
10
flowchart LR
11
D["Your C10-3 record<br/>annotations · logs · commit dates"] --> Q1
12
Q1["What happened?<br/>the facts"] --> Q2["What was the impact?<br/>positive · negative · neutral"]
13
Q2 --> Q3["What would I do next time?<br/>the learning"]
14
Q3 --> V["A verdict on the plan,<br/>carried by the evidence"]
15
Q3 -.->|"repeat per major change"| Q1
16
```
17
18
*Three questions, run once per significant change, then one verdict over the lot. The loop is why the record has to exist first — the facts step has nowhere to start without it.*
19
20
## **What is this?**
21
22
A thoughtful **post-project analysis** looking back at how well your planning worked and what you learned about project management.
23
24
**Purpose:** Assess the effectiveness of your project plan using evidence from your tracking data (C10-3) to demonstrate critical evaluation skills.
25
26
**⚠️ Important:** This reflection is based entirely on **actual events and logged modifications**, not retrospective reconstruction.
27
28
---
29
30
## **🎯 Reflection Framework (C10-4)**
31
32
### **Optional: Build on milestone mini-retrospectives**
33
34
_If you wrote brief reflections during your project, use them as foundation:_
35
36
- **Post-Analysis**: What worked in problem investigation?
37
- **Post-Design**: How effective was your design process?
38
- **Post-Alpha Testing**: What did testing reveal about your planning?
39
- **Post-Beta Testing**: How did user feedback change your timeline?
40
41
### **Your final reflection should answer:**
42
43
- **Was my project plan effective?** Why or why not?
44
- **What factors made it work well or poorly?**
45
- **How did changes impact my project completion?**
46
- **What patterns emerged in my modifications?**
47
- **What would I do differently next time?**
48
49
### **💭 Use Simple Reflective Thinking:**
50
51
For each major issue, ask yourself:
52
53
- **What happened?** (The facts)
54
- **What was positive/negative?** (Impact analysis)
55
- **What will I do next time?** (Learning)
56
57
---
58
59
## **📝 Reflection Structure**
60
61
### **1. Overall Plan Assessment** - _"How effective was my plan?"_
62
63
**Rate your plan's effectiveness (with justification):**
64
65
- **Highly Effective (80-100%)**: Plan worked well with minor adjustments
66
- **Moderately Effective (60-79%)**: Plan needed several modifications but project succeeded
67
- **Somewhat Effective (40-59%)**: Plan required major changes, some delays occurred
68
- **Ineffective (0-39%)**: Plan failed to guide project successfully
69
70
**Evidence-based justification:** _"My plan was 75% effective because I completed all requirements on time, but underestimated testing phases by 4 days total."_
71
72
### **2. Effectiveness Factors Analysis** - _"What worked and what didn't?"_
73
74
#### **✅ What Made the Plan Effective:**
75
76
- **Realistic timeframes**: Which estimates were accurate?
77
- **Good planning decisions**: What early choices paid off?
78
- **Flexibility**: How did the plan adapt to changes?
79
- **Resource allocation**: Were resources planned well?
80
81
#### **❌ What Made the Plan Less Effective:**
82
83
- **Underestimated tasks**: Which took longer than expected?
84
- **Missing considerations**: What didn't you plan for?
85
- **Over-optimistic timelines**: Where were you unrealistic?
86
- **Resource constraints**: What limitations affected the plan?
87
88
**Example:** _"Effective: I allocated extra time for coding which absorbed alpha testing delays. Ineffective: I didn't plan for user tutorial creation - beta testing revealed this need."_
89
90
### **3. Change Impact Analysis** - _"How did modifications affect completion?"_
91
92
**Use your C10-3 tracking data to analyze:**
93
94
- **Positive changes**: Modifications that improved project outcomes
95
- **Negative changes**: Modifications that caused delays or problems
96
- **Neutral changes**: Modifications with minimal impact
97
- **Change attribution**: Who/what drove each change (you, teacher, user feedback, technical issues)
98
99
### **4. Planning Approach Evaluation** - _"What does this reveal about my planning effectiveness?"_
100
101
**Based on the evidence:**
102
103
- **Planning strengths**: What aspects of my approach worked well?
104
- **Planning weaknesses**: What aspects need improvement?
105
- **Overall planning accuracy**: How realistic were my original estimates?
106
- **Adaptability**: How well did my plan handle unexpected changes?
107
108
**Example:** _"My planning showed strength in coding estimates but weakness in testing allocation. The plan demonstrated good adaptability when technical issues arose, with minimal impact on final delivery."_
109
110
---
111
112
## **📋 Simple Reflection Template**
113
114
### **Project Plan Effectiveness Reflection**
115
116
**Overall Assessment:** [Rating/100 with justification]
117
118
**What Made My Plan Effective:**
119
120
1. [Factor 1 with evidence]
121
2. [Factor 2 with evidence]
122
3. [Factor 3 with evidence]
123
124
**What Made My Plan Less Effective:**
125
126
1. [Issue 1 with evidence]
127
2. [Issue 2 with evidence]
128
3. [Issue 3 with evidence]
129
130
**Change Impact Summary:**
131
132
- **Most helpful change:** [Change + why it helped + who/what drove it]
133
- **Most problematic change:** [Change + why it caused issues + who/what drove it]
134
- **Overall impact:** [Did changes mostly improve or harm project completion?]
135
136
**Evidence from Project Logs:**
137
138
- [Reference specific log entries that support your assessment]
139
- [Include 2-3 examples of changes with outcomes and attribution]
140
141
**Planning Approach Evaluation:**
142
143
1. **Planning Strengths:** [What worked well in your approach]
144
2. **Planning Weaknesses:** [What aspects were less effective]
145
3. **Estimate Accuracy:** [How realistic were your original timelines]
146
4. **Plan Adaptability:** [How well did your plan handle changes]
147
148
**Final Conclusion:** [Was the plan successful in helping you complete the project? One paragraph summary]
149
150
---
151
152
## **✨ Pro-tips:**
153
154
**Use your C10-3 data** - Reference specific log entries as evidence
155
156
**Be honest** - Authentic reflection shows maturity and learning
157
158
**Think like a project manager** - What would you tell someone planning a similar project?
159
160
**Connect to outcomes** - Link plan effectiveness to final solution quality
161
162
**Show growth** - Demonstrate what you learned about project management
163
164
## **🎯 Remember:**
165
166
This isn't about having a perfect plan - it's about **demonstrating thoughtful analysis** of your planning effectiveness and **showing professional growth** in project management skills!
167
168
---
169
170
## Check Your Understanding
171
172
**1.** *"My plan was effective because I finished the project."* Which band does that reach?
173
174
>| ### Answer
175
>| Band 1–2 at best. Finishing is not evidence about the plan. A band 7–8 answer names specific changes, says how each affected completion, and only then judges the plan.
176
177
**2.** Where does the evidence for C10-4 come from?
178
179
>| ### Answer
180
>| From your C10-3 record — the annotated baseline, the logs and the commit dates — plus the C01 plan you started from. C10-4 adds no new evidence; it judges what C10-3 collected.
181
182
**3.** You underestimated testing by four days but delivered on time because you had padded the coding phase. Is that a strength or a weakness of the plan?
183
184
>| ### Answer
185
>| Both, and saying so is what "evaluates" means. The estimate was wrong (a weakness in accuracy) and the padding absorbed it (a strength in adaptability). A verdict that names both, with the dates behind them, beats one that picks a side.