L3 Inquiry - Risks

Time Risk

• Poor time management could lead to missed deadlines, rushed work, or an incomplete project.

• Unexpected setbacks (e.g., technical issues, needing to learn new skills) can delay progress.

• Procrastination can result in a last-minute scramble, affecting quality.

How to mitigate it?

• Project management with key milestones.

• Set personal deadlines, allow for unexpected delays.

• Use time-tracking tools like Trello or Notion

• Schedule buffer time, leave extra time before final submission for any minor issues or improvements.

Factors Outside of One’s Control Risk

• School closures, sickness, or personal emergencies may disrupt progress.

• Software crashes or corrupted files could cause loss of work.

• Group projects might suffer if a team member doesn’t contribute.

How to mitigate it?

• • Back up work regularly: Use cloud storage like Google Drive or GitHub.

  • Have a contingency plan: If something fails, have an alternative way to continue.

  • Communicate with the teacher: Inform them early if delays occur due to valid reasons.

  • Manage group roles effectively: Assign clear responsibilities in group projects to avoid dependence on one person.

Financial Risk

• Software, hardware, or hosting costs could exceed expectations.

• A free tool might not meet project requirements, leading to last-minute paid upgrades.

• If a student purchases resources (e.g., digital assets), they may not be useful or needed.

How to mitigate it?

• Budget before starting: Identify necessary tools and check for free alternatives.

• Use school resources: Many schools provide free access to software and hardware.

• Explore open-source options: Free tools like GIMP, Blender, and VS Code can replace costly alternatives.

• Avoid impulse purchases: Research before buying assets or subscriptions.

Scope Creep Risk

• • Adding too many features can overwhelm the student and extend development time.

  • Changing project direction midway can cause delays.

  • Overcomplicating the outcome can lead to an incomplete or poorly executed project.

How to mitigate it?

• • Define project scope early: Clearly outline features and functionalities.

  • Stick to core goals: If new ideas arise, evaluate whether they are essential.

  • Use a ‘nice-to-have’ list: Extra features can be implemented only if time allows.

  • Get teacher approval: Before making major changes, ensure they align with the assessment criteria. 

Estimations and Scheduling Risk

• Overestimating what can be done in 20 weeks can lead to an unfinished or incomplete project.

• Underestimating task complexity can cause delays.

• Poor scheduling can mean too much work is left for the final weeks.

How to mitigate it?

• Use iterative development: Work in phases, so something is always functional.

• Plan based on experience: If similar projects took 4 weeks for coding, don’t assume it’ll take 2.

• Prioritize critical tasks first: Work on the most essential features early.

• Regularly review progress: If off-track, adjust the plan rather than rushing later.

Incorrect Functionality Risk

• The final outcome might not work as expected due to coding errors, poor design, or technical issues.

• Features may be implemented incorrectly or not be user-friendly.

• Bugs might appear late, causing delays in submission.

How to mitigate it?

• Test frequently: Conduct testing throughout development, not just at the end.

• Use feedback loops: Ask peers or teachers to review and provide feedback.

• Debug regularly: Fix small issues early to avoid major breakdowns later.

• Follow best practices: Use clear, organized code and proper documentation.