Insights & Exemplars
This week, we looked at how to measure the "Risk" in a project using the Impact x Probability formula. It’s wonderful to see you shifting from simply doing the work to thinking like a project manager!
⭐ Risk Strategy Standouts
These students did a great job showing how to apply our textbook frameworks to real technical hurdles.
Adrian
Time Management
Adrian built a detailed 5-day schedule to show that planning the work is only half the battle—you have to plan the time too.
Amy
Scope Alignment
Amy highlighted that the Scope Statement is the "anchor" that keeps everything from floating away once you start coding.
Joseph
Technical Syntax
Joseph used professional tools to Eliminate risk, checking his work while he was typing instead of waiting until the end.
Hugo
Environmental Risk
Hugo showed us that "risks" aren't just in the code; they're in our environment, like having a backup hotspot for when WiFi fails.
Susan
Alignment Analysis
Susan perfectly used a high score to explain why misunderstanding a prompt is one of the biggest dangers to a project's success.
Risk Themes & TAME Application
This section breaks down how we chose to handle our risks using the TAME method. Most of you chose to "Mitigate" (reduce) the risk, but it was great to see some students "Accepting" things they couldn't control.
Textbook Reference: PMUPM Ch. 4
How we TAME a Risk
Our Formula
Risk Score = Impact × Probability
Passing the problem to someone else or a backup system.
Knowing the trouble might come and being ready for it.
Taking steps to make the risk less likely or less harmful.
Changing the plan to remove the risk completely.
How our class handled risks
This chart shows the strategies you chose. Click a bar to see how we applied them.
Select a strategy
Class Highlights
Choose a strategy on the left to see what we learned as a group.
How we did as a class
I am so proud of the honesty and hard work shown in this discussion. It’s not easy to look at a project and talk about what might go wrong, but you all did it beautifully. Here is a look at how we felt about the risks and where we can keep growing together.
How risky did Project 01 feel?
Most of you gave your risks a score of 12-16 out of 25. This tells me you were being careful and thoughtful about the technical requirements.
What were our biggest worries?
Understanding instructions was the top risk identified. This shows how much you value getting the work right!
✍️ Teacher's Highlights & Shout-outs
Luis Alvarez
"I loved your unique look at weather/wifi risks. Working ahead was a smart way to stay safe!"
Donna Baca
"Your reflection on 404 errors was very helpful for other students to read. Great troubleshooting!"
Blaire Bingham
"Excellent use of cross-referencing to eliminate doubt. You showed a lot of confidence here."
Tristen Dellinger
"We've all had those 'mini heart attack' moments with file saving! Your TAME application was spot on."
Adrian Fuentes
"A detailed mitigation schedule is the mark of a true project manager. Outstanding work."
Amy Gardner
"I loved how you called the scope an 'anchor.' That is the perfect way to describe its role."
Susan Gifford
"Perfect analysis of why alignment matters. Your checklist idea is a great tip for the whole class."
Latoya Masters
"Great catch on the list formatting requirements. Using the preview tool is the best way to catch those errors."
Katy Nance
"Your 'Measure twice, cut once' approach is exactly what we need for high-stakes projects. Very thoughtful."
Joseph Paris
"Using a code linter was an excellent technical strategy. Verifying as you type is a huge time saver!"
A tiny reminder: Citations
Let's keep working on getting our APA style book references right.