Difference between revisions of "SMT483G1: WeRespond Project Management"
Jump to navigation
Jump to search
Hmkhoo.2017 (talk | contribs) (→Risks) |
Hmkhoo.2017 (talk | contribs) |
||
| Line 22: | Line 22: | ||
|} | |} | ||
<!--/MENU--> | <!--/MENU--> | ||
| + | |||
| + | <!-- Body --> | ||
| + | <!-- Sub Header --> | ||
| + | <center> | ||
| + | {| class="wikitable"; style="background-color:#fff; width="80%"| | ||
| + | |||
| + | | style="vertical-align:top;" | <div style="padding: 0px 10px 0px 10px; font-family:Tw Cen MT, Helvetica, Open Sans, Arial, sans-serif; font-size:20px; text-align:center; line-height: wrap_content; border-top:solid #EA4D4D; border-bottom:solid #EA4D4D; margin-left: 2em; margin-right: 2em;"> | ||
| + | [[SMT483G1: WeRespond Project Timeline | <font color="#111"><b>Project Timeline</b></font>]] | ||
| + | |||
| + | | style="vertical-align:top;" | <div style="padding: 0px 10px 0px 10px; font-family:Tw Cen MT, Helvetica, Open Sans, Arial, sans-serif; font-size:18px; text-align:center; line-height: wrap_content; border-top:solid #fff; border-bottom:solid #fff; margin-left: 2em; margin-right: 2em;"> | ||
| + | [[SMT483G1: WeRespond Project Schedule | <font color="#111"><b>Project Schedule</b></font>]] | ||
| + | |||
| + | | style="vertical-align:top;" | <div style="padding: 0px 10px 0px 10px; font-family:Tw Cen MT, Helvetica, Open Sans, Arial, sans-serif; font-size:18px; text-align:center; line-height: wrap_content; border-top:solid #fff; border-bottom:solid #fff; margin-left: 2em; margin-right: 2em;"> | ||
| + | [[SMT483G1: WeRespond Risk Management| <font color="#111"><b>Risk Management</b></font>]] | ||
| + | |||
| + | |} | ||
| + | </div> | ||
| + | <!-- End of Sub Header --> | ||
| + | <!-- End of Body --> | ||
=== Project Timeline=== | === Project Timeline=== | ||
Revision as of 15:59, 1 February 2020
Project Timeline
Changes in Project Timeline
| Version | Changes |
|---|---|
| Initial Timeline | |
| 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. |
