Difference between revisions of "SMT483G1: WeRespond Project Schedule"

From SMT Project Experience
Jump to navigation Jump to search
(Created page with "<!--HEADER--> 800px|frameless|center <!--/HEADER--> <!--MENU--> <!--rax--> {|style="background-color:#AC3E3B ; color:#FFFFFF; padding: 5 0 5 0;" w...")
 
 
(9 intermediate revisions by the same user not shown)
Line 42: Line 42:
 
<!-- End of Body -->
 
<!-- End of Body -->
  
=== Project Timeline===
+
[[File:Project schedule 21 apr 1.png|1000px|frameless|center]]
[[File:Updated timeline 30 Jan 20.png|center|1100px|Project Timeline]]
+
[[File:Project schedule 21 apr 2.png|1000px|frameless|center]]
 
 
[[File:Project schedule on 1 feb.png|1000px|frameless|center]]
 
 
 
===Changes in Project Timeline===
 
{| class="wikitable"
 
|-
 
! Version !! Changes
 
|-
 
|[[File:Timeline1.jpg|thumb|center|800px|]] || Initial Timeline
 
|-
 
|[[File:Updated timeline 30 Jan 20.png|thumb|center|800px]] ||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.
 
 
 
{| class="wikitable"
 
|-
 
! 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.
 
|}
 

Latest revision as of 15:48, 21 April 2020