<!-- 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. --> # Assessing the Effectiveness of Your Project Plan *The C10-4 judgement: was the plan any good, and how do you know? Read it before class write 3, side B.* > [!NOTE] > **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. ```mermaid flowchart LR D["Your C10-3 record<br/>annotations · logs · commit dates"] --> Q1 Q1["What happened?<br/>the facts"] --> Q2["What was the impact?<br/>positive · negative · neutral"] Q2 --> Q3["What would I do next time?<br/>the learning"] Q3 --> V["A verdict on the plan,<br/>carried by the evidence"] Q3 -.->|"repeat per major change"| Q1 ``` *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.* ## **What is this?** A thoughtful **post-project analysis** looking back at how well your planning worked and what you learned about project management. **Purpose:** Assess the effectiveness of your project plan using evidence from your tracking data (C10-3) to demonstrate critical evaluation skills. **⚠️ Important:** This reflection is based entirely on **actual events and logged modifications**, not retrospective reconstruction. --- ## **🎯 Reflection Framework (C10-4)** ### **Optional: Build on milestone mini-retrospectives** _If you wrote brief reflections during your project, use them as foundation:_ - **Post-Analysis**: What worked in problem investigation? - **Post-Design**: How effective was your design process? - **Post-Alpha Testing**: What did testing reveal about your planning? - **Post-Beta Testing**: How did user feedback change your timeline? ### **Your final reflection should answer:** - **Was my project plan effective?** Why or why not? - **What factors made it work well or poorly?** - **How did changes impact my project completion?** - **What patterns emerged in my modifications?** - **What would I do differently next time?** ### **💭 Use Simple Reflective Thinking:** For each major issue, ask yourself: - **What happened?** (The facts) - **What was positive/negative?** (Impact analysis) - **What will I do next time?** (Learning) --- ## **📝 Reflection Structure** ### **1. Overall Plan Assessment** - _"How effective was my plan?"_ **Rate your plan's effectiveness (with justification):** - **Highly Effective (80-100%)**: Plan worked well with minor adjustments - **Moderately Effective (60-79%)**: Plan needed several modifications but project succeeded - **Somewhat Effective (40-59%)**: Plan required major changes, some delays occurred - **Ineffective (0-39%)**: Plan failed to guide project successfully **Evidence-based justification:** _"My plan was 75% effective because I completed all requirements on time, but underestimated testing phases by 4 days total."_ ### **2. Effectiveness Factors Analysis** - _"What worked and what didn't?"_ #### **✅ What Made the Plan Effective:** - **Realistic timeframes**: Which estimates were accurate? - **Good planning decisions**: What early choices paid off? - **Flexibility**: How did the plan adapt to changes? - **Resource allocation**: Were resources planned well? #### **❌ What Made the Plan Less Effective:** - **Underestimated tasks**: Which took longer than expected? - **Missing considerations**: What didn't you plan for? - **Over-optimistic timelines**: Where were you unrealistic? - **Resource constraints**: What limitations affected the plan? **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."_ ### **3. Change Impact Analysis** - _"How did modifications affect completion?"_ **Use your C10-3 tracking data to analyze:** - **Positive changes**: Modifications that improved project outcomes - **Negative changes**: Modifications that caused delays or problems - **Neutral changes**: Modifications with minimal impact - **Change attribution**: Who/what drove each change (you, teacher, user feedback, technical issues) ### **4. Planning Approach Evaluation** - _"What does this reveal about my planning effectiveness?"_ **Based on the evidence:** - **Planning strengths**: What aspects of my approach worked well? - **Planning weaknesses**: What aspects need improvement? - **Overall planning accuracy**: How realistic were my original estimates? - **Adaptability**: How well did my plan handle unexpected changes? **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."_ --- ## **📋 Simple Reflection Template** ### **Project Plan Effectiveness Reflection** **Overall Assessment:** [Rating/100 with justification] **What Made My Plan Effective:** 1. [Factor 1 with evidence] 2. [Factor 2 with evidence] 3. [Factor 3 with evidence] **What Made My Plan Less Effective:** 1. [Issue 1 with evidence] 2. [Issue 2 with evidence] 3. [Issue 3 with evidence] **Change Impact Summary:** - **Most helpful change:** [Change + why it helped + who/what drove it] - **Most problematic change:** [Change + why it caused issues + who/what drove it] - **Overall impact:** [Did changes mostly improve or harm project completion?] **Evidence from Project Logs:** - [Reference specific log entries that support your assessment] - [Include 2-3 examples of changes with outcomes and attribution] **Planning Approach Evaluation:** 1. **Planning Strengths:** [What worked well in your approach] 2. **Planning Weaknesses:** [What aspects were less effective] 3. **Estimate Accuracy:** [How realistic were your original timelines] 4. **Plan Adaptability:** [How well did your plan handle changes] **Final Conclusion:** [Was the plan successful in helping you complete the project? One paragraph summary] --- ## **✨ Pro-tips:** **Use your C10-3 data** - Reference specific log entries as evidence **Be honest** - Authentic reflection shows maturity and learning **Think like a project manager** - What would you tell someone planning a similar project? **Connect to outcomes** - Link plan effectiveness to final solution quality **Show growth** - Demonstrate what you learned about project management ## **🎯 Remember:** 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! --- ## Check Your Understanding **1.** *"My plan was effective because I finished the project."* Which band does that reach? >| ### Answer >| 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. **2.** Where does the evidence for C10-4 come from? >| ### Answer >| 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. **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? >| ### Answer >| 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.