HeaderSIS.jpg

IS480 Team wiki: 2013T2 Five&AHalfMen Project Management risk

From IS480
Revision as of 14:39, 27 October 2013 by Ygchan.2011 (talk | contribs)
Jump to navigation Jump to search

Five&ahalfLogo.png


Home   Project Overview   Project Management   Documentation   The Team
Schedule Risks Metrics Resources Learning Outcomes
RiskRisk DescriptionLikelihoodImpactMitigation
TechnologyMost of the technology and tools to be used are relatively new to the team. If the learning curve becomes too steep, there would be delays and expected dateline might not be met.ModerateHighMembers are to research comprehensively and consult experts on the new technologies. PM will observe member’s progress closely and make decision to drop function, use backup technology or reallocate the developers if a certain technology is becoming the bottleneck of the project
Scope and project scheduleScope of the project is currently complex and project schedule is very tight. There is a high chance that project might contain too many tasks, overestimating the team ability and exceed project submission datelineHighHighPM will have to observe closely at the project progress right at the start and make a decision early to drop functionalities if found that members abilities are over estimated.
ResourceProject is looking at very heavy and long hours from developers. In addition to their academic work, developers might be over exhausted to meet dateline. Developers might breakdown and there might be a halt in the project.ModerateHighTeam members are to watch for each other and sound off if any seems to be over-exhausted. PM will have to observe the mental and physical state of the developers and might consider dropping functions and changing dateline if developers are not getting enough rest.