Skip to main content
Workforce LibreTexts

4.5.3: Project Reckon Risk Register and Control Log

  • Page ID
    54808
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \( \newcommand{\dsum}{\displaystyle\sum\limits} \)

    \( \newcommand{\dint}{\displaystyle\int\limits} \)

    \( \newcommand{\dlim}{\displaystyle\lim\limits} \)

    \( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)

    ( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\id}{\mathrm{id}}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\kernel}{\mathrm{null}\,}\)

    \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\)

    \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\)

    \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    \( \newcommand{\vectorA}[1]{\vec{#1}}      % arrow\)

    \( \newcommand{\vectorAt}[1]{\vec{\text{#1}}}      % arrow\)

    \( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vectorC}[1]{\textbf{#1}} \)

    \( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)

    \( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)

    \( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \(\newcommand{\longvect}{\overrightarrow}\)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)

    Project Reckon Risk Register & Control Log


    Purpose of the Risk Log

    Project Reckon is a fully outsourced product development initiative. Risks do not appear suddenly — they accumulate gradually.

    Students must maintain a living Risk Register across all scenarios.

    Each week:

    • New risks may be added.

    • Existing risks must be updated.

    • Risk severity may increase or decrease.

    • Mitigation actions must be documented.

    • Residual exposure must be evaluated.

    This artifact becomes cumulative and is submitted at the end of the practicum.


    Risk Log Structure

    Students must maintain the following table:


    Project Reckon Risk Register

    Risk ID Risk Description Category Trigger/Event Likelihood (1–5) Impact (1–5) Risk Score Mitigation Action Owner Status Residual Risk

    Field Definitions

    Risk ID

    Unique identifier (R-01, R-02, etc.)


    Risk Description

    Concise but specific statement.

    Example:
    “Synchronization Engine defect clustering may indicate architectural instability in concurrent update handling.”


    Category

    Choose one:

    • Scope

    • Schedule

    • Budget

    • Quality

    • Architecture

    • Vendor Management

    • Integration

    • Political/Executive

    • Dependency

    • Change Control


    Trigger/Event

    What caused the risk to be logged?

    Example:
    “Iteration 3 defect spike in integration module.”


    Likelihood (1–5)

    1 = Rare
    2 = Unlikely
    3 = Possible
    4 = Likely
    5 = Almost Certain


    Impact (1–5)

    1 = Minimal
    2 = Low
    3 = Moderate
    4 = High
    5 = Severe


    Risk Score

    Risk Score = Likelihood × Impact

    Interpretation:

    • 1–5 = Low

    • 6–10 = Moderate

    • 11–15 = Elevated

    • 16–25 = Critical


    Mitigation Action

    Specific and actionable.

    Example:

    • Require architectural walkthrough.

    • Increase QA concurrency testing.

    • Initiate formal change control.

    • Freeze new feature additions.


    Owner

    Who is accountable?

    • C-Bay PM

    • ZynoxDev Architecture Lead

    • QA Manager

    • Steering Committee


    Status

    • Open

    • Monitoring

    • Mitigating

    • Escalated

    • Closed


    Residual Risk

    After mitigation, what level remains?

    Low / Moderate / High / Critical


    Weekly Risk Log Requirements

    At the end of each scenario submission, students must:

    1. Add any new risks.

    2. Update likelihood/impact of existing risks.

    3. Adjust mitigation status.

    4. Identify any risks requiring escalation.

    5. Explain if risk posture is improving or deteriorating.


    Example Entry (Scenario 2)

    Risk ID Risk Description Category Trigger/Event Likelihood Impact Score Mitigation Owner Status Residual
    R-02 Integration defect clustering may reflect architectural instability Architecture Iteration 3 defect spike 3 4 12 Require root cause analysis and concurrency testing expansion ZynoxDev Arch Lead Mitigating Moderate

    Risk Log Grading Component

    Students are graded on:

    Criteria Points
    Risk Identification Accuracy 20
    Appropriate Likelihood & Impact Calibration 20
    Mitigation Precision 20
    Escalation Discipline 20
    Longitudinal Risk Tracking Across Weeks 20

    Total: 100 points (cumulative)


    Cumulative End-of-Module Requirement

    Final Submission must include:

    1. Complete Risk Register

    2. Risk Trend Analysis (2–3 pages)

      • Which risks increased?

      • Which were contained?

      • Which were underestimated?

    3. Risk Posture at Release Decision

    4. Lessons Learned in Risk Detection


    Teaching Impact

    This artifact forces students to:

    • Think longitudinally

    • Recognize pattern formation

    • Avoid “week-by-week amnesia”

    • Practice early detection

    • Understand mitigation vs resolution

    • Avoid reactive management

    It converts smulation into enterprise realism.


    4.5.3: Project Reckon Risk Register and Control Log is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by LibreTexts.

    • Was this article helpful?