SMT483G1: WeRespond Risk Management

From SMT Project Experience
Revision as of 16:02, 1 February 2020 by Hmkhoo.2017 (talk | contribs) (Created page with "<!--HEADER--> 800px|frameless|center <!--/HEADER--> <!--MENU--> <!--rax--> {|style="background-color:#AC3E3B ; color:#FFFFFF; padding: 5 0 5 0;" w...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Werespond logo.jpg

HOME

ABOUT US

PROJECT OVERVIEW

PROJECT MANAGEMENT

DOCUMENTATION

Project Timeline

Project Timeline
Project schedule on 1 feb.png

Changes in Project Timeline

Version Changes
Timeline1.jpg
Initial Timeline
Updated timeline 30 Jan 20.png
Updated due to scope changes

Risk Management

  • Any delay in the implementation of core functions module can cause a delay in implementation of secondary, tertiary and good-to-have functions.
  • Any bugs in Account and Administrator modules will also affect the base functions of the application.
  • Any bugs that are not fixed in the core functions module can affect the performance of those in the secondary, tertiary and good-to-have modules.
No. Risk Type Risk Event Likelihood Impact Mitigation
1 Project Management Risk Allocation of too much/little time for development of functions Medium High Include buffer days before final submission. Allocate more time to develop more complex functions.
2 Sponsor Risk Change in sponsor's requirement Medium High Meet and update once every 1-2 weeks to ensure that development is on par with sponsor's requirements.
3 Human Risk Team member is not available due to illness or unforeseen circumstances Medium Medium Each member has dual roles to take over temporarily for the member who is unavailable.
4 Technical Risk Unfamiliar with programming language. Medium Medium More experienced developer to share knowledge and developers to research and learn technologies required.