HeaderSIS.jpg

IS480 Team wiki: 2014T1 AT Co JR RISKS

From IS480
Jump to navigation Jump to search
AT+Co. Jr. OVERVIEW PROJECT MANAGEMENT DOCUMENTATION
[ TIMELINE ] [ SCHEDULE ] [ METRICS ] [ RISKS ] [ TECHONOLOGY ]


Risks & Mitigation

ATNCOJR Metrics.001.jpg


Project Requirement

# Risk Description Example Likelihood Impact
Risk Value
Mitigation

1.1

  • Unclear Requirements
System requirements is not clearly identified, is unclear or is incorrect, leading to continuous change of requirements
  • Client is indecisive of his business plan, which might leads to requirements are not clear for the team
  • The team may not know what is best for the client as the idea is relatively new to the industry. Conversely, the client might not have a clear idea on the deliverables of the project as well

4

4

16

Work closely with client, and review the requirements list with client at every iteration so changes can be addressed as soon as possible.

1.2

  • Continuous Changes of Requirements
Unforeseen change in requirements due to lack of experience or expectations towards requirements
  • Client may have new ideas coming out during development phase
  • Tendency to add additional functionalities and try to deliver more than agreed which will ultimately cause the team to not be able to meet deadlines

4

4

16

Evaluate priority and feasibility of new requirements before taking action

Design and Developement

# Risk Description Example Likelihood Impact
Risk Value
Mitigation

2.1

  • Technology and Learning
Project involves the use of new technology not used by members of the team prior to project or technology with inherently high level of technical complexity. This risk is extremely exposed to team members who are inexperienced, inadequately trained, or lacking in specialized skills. This leads to steep learning curve and potential personal “shortfalls” by team members, requiring long amount of time to complete tasks
  • This risk is extremely exposed to team members who are inexperienced, inadequately trained, or lacking in specialized knowledge
eg: new file framework, javascript library or other useful web service
  • This leads to steep learning curve and potential personal “shortfalls” by team members, requiring long amount of time to complete tasks

4

4

16

Provide more buffer time in the first few iterations for developer to explore the new tools

2.2

  • Integration of Project
The lengthened integration of all different levels due to the complexities of the front-back end integration might result in a delay in the schedule
  • Varied coding competency and coding style of each team member might result in difficulties during integration

4

3

12

Work closely with client, and review the requirements list with client at every iteration so changes can be addressed as soon as possible.

2.3

  • Critical Bug
  • Application may contain some bugs that crashes the whole application in the last phase

4

4

16

Constantly test the system and have proper testing documentation

2.4

  • Platform incompatibilities
  • Versioning software currently used goes down or encounters problems preventing the retrieval of project source codes
  • Unforeseen incompatibilities between various software uses may also arise

3

4

12

Constantly test the system and have proper testing documentation


Project Management

# Risk Description Example Likelihood Impact
Risk Value
Mitigation

3.1

  • Scheduling Creep
Tendency to add additional functionalities and try to over-deliver which will ultimately cause the team to not be able to meet deadlines
  • Project manager is not sure of the competency of each team member, task allocation might not accurate which leads to project milestones or schedule inaccurately defined

3

4

12

Constantly track the task hour in the first iteration, and estimate task distribution based on that

3.2

  • Monitor & Management
  • There is an absence of adequate project management or there is ineffective project managers
  • The project progress may also not be monitored closely enough

3

4

12

PM need to constantly monitoring whether the milestone being hit

3.3

  • Communication
  • Ineffective communications is carried out by team members
  • This can be due to various barriers of communication

3

4

12

PM need to make sure the team is bonded
PM need to make sure everybody’s voice is heard
FYP meeting will be on a routine basis to make sure


3.4

  • Team Conflicts
  • Team member doesn’t have a common understanding of the project, resulting difficulties in deriving final decisions

3

4

12

Seek for supervisor and client’s idea when necessary

3.4

  • Unforeseen Absence
  • Team member withdraw from the project due to unexpected reason eg: family, personal issue.

2

5

10

Allocate a 2nd-person in charge to take over the responsibilities when needed


Risks & Mitigation (Acceptance)

Type of Risk Risk Description Risk Level Mitigation

Project Management

Unexpected absence of team members

High

  • Assistant of the task owner will take over the task on his or her behalf
  • Review on roles and capabilities
  • Reschedule the task
  • Source for another team member and reevaluate the roles

Project Management

Changes in business concept leading to changes in system requirements

Medium

  • Conducted business and competitor analysis for sponsor
  • Use prototypes were used for discussion during sponsor meeting


Design and Development

Steep learning curve when using new language or frameworks

Medium

  • The team has performed extensive research and practice on the technologies
  • Knowledge sharing sessions were conducted


Risks & Mitigation (Mid-Term)

Type of Risk Risk Description Risk Level Mitigation

Project Management

Team members might underestimate school commitments and conflicting priorities. This might affect the completion of deliverables and even the quality.

Medium

Every week, all the members have to filling the "Time for FYP" sheet and clarify if he/she has other school commitments, so that PM can better schedule the task for each member.

Project Management

Client was overseas and not able to meet with team physically.

Low

Online tools were being used. Regularly email client about the team's progress.

Design and Development

We have underestimated the difficulties of Facebook integration

Medium

Reschedule and shift independent development in front

Project Requirement Risk

Client raise concern of the pricing model. Project schedule may be affected to accommodate the changes to the project.

High

Work with the sponsor to create a requirement document that both parties agreed on. Come to an understanding that any change requests would subject to the other party’s approval based on their judgment of necessity of the change


Risks & Mitigation (Final)

Type of Risk Risk Description Risk Level Mitigation

Project Management

During week11&12, the entire team was overwhelmed by projects from different modules, which reduced the time we have spent on FYP.

High

Estimate the time for the to be developed functions, adjust the project scope and drop certain tertiary functions accordingly.

Project Management

It's very hard for the team to meet physically when we are overwhelmed by different projects.

Medium

Facebook chat and google hangout are being used to facilitate our communication

Business Requirement Risk

Client changed the business requirement

High

  • Adjust the project scope
  • Re-schedule the project
Business Requirement
There is insufficient promotions posted on the website.

Medium

  • Push sponsor refer us more merchant to post on our website
  • Visit restaurant to promote TheFoodieMarket