Peace Maikasuwa

Risk No. Risk Description Impact Reference Describe what this risk is. "There is risk Number that..." Description of what will happen if this risk happens R1 There is a risk that will cause scope creep from changing stakeholder requirements. If this happens, there will be an Increased costs and extended timelines. R2 There is a risk with development delays due to technical challenges If this happens, Project milestones may be missed. R3 There is a risk with Vendor onboarding issues R4 There is a risk that will cause Integration issues with third-party tools R5 There is a risk with the Marketing If this happens, there will be Low traffic campaign fails to attract target audience and conversion rates. R5 Increased development time and potential costs. Severity Probability Date Raised Mitigation L/M/H L/M/H The date that risked was raised Outlines the planning process for implementing actions to reduce or eliminate business losses due to the type of hazards High High 7/1/2024 Implement a strict change control process Medium Medium 9/29/2024 Conduct thorough technical planning; ensure adequate resources. Pre-qualify vendors; establish clear onboarding procedures. High Medium 8/25/2024 Early integration testing; choose compatible tools. High Medium 9/15/2024 Conduct market research; continuously monitor and adjust campaign Target Resolution Date Risk Raised When this risked needs to be Who identified the closed off before it becomes an risk issue Project Manager Owner Person responsible for managing the risk Project Manager Tech Lead Vendor's Manager Vendor's Manger Tech Lead Tech lead Marketting Lead Marketting Lead Ass No. Description Reference Number Describe what the assumption is. "It is assumed that..." A1 It is asssumed that key stakeholders will be available as per the project schedule. A2 Required third-party tools are compatible with existing systems A3 Users will adapt to the new platform with minimal training Impact Owner Description of what will happen if this assumption fails Who will manage it. Delays in approvals and requirement clarifications. Project Manager Integration delays; increased costs for alternative tools. Tech lead Increased support requests; lower user Training Lead satisfaction. Issue No. Description Reference Number Describe the issue I1 Stakeholders unavailable for requirement gathering meetings I2 / R1 Changing stakeholder requirements causing scope creep I3 / R3 Delays in vendor onboarding affecting product availability Impact Severity Date Raised Description of what the issue impact is L/M/H Delays in design and development phases. High High Increased costs and extended timelines Delays in product listing and marketing High / campaigns. Medium The date that issue was raised Containment Owner Outlines the planning process for implementing for reducing the impact of the issue and ensuring that the impact does not expand. Person responsible for managing the issue Escalate to senior management for priority adjustment use backup stakeholders. Project Manager Enforce change control process strictly; communicate impact of changes. Project Manger Consider alternative vendors if delays persist. Increase follow-up frequency with vendors Vendor's Manager Date Closed Dep No. Dependency Description Reference Describe what is dependency. "There is Number a dependency on ..." Dep_001 There is a dependency for Onboarding of key vendors to be ready for Product Listing and Marketting compaign Dep_002 There is a dependency for User training completion for Going Live Dependency No Dependency Date Impact Who does the dependency sit with The date the dependency needs to be fulfilled by What will happen if the dependency is not met. Vendor Manager Delays in product listing and marketing campaigns. Training Lead Delays in final preparations and golive.