HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T1 SincereNet Metrics"

From IS480
Jump to navigation Jump to search
Line 268: Line 268:
 
  ! scope="row" align = "center" style="background:#ffffff;" |  
 
  ! scope="row" align = "center" style="background:#ffffff;" |  
 
<center>[[Image:member_schedule1.png]]</center>
 
<center>[[Image:member_schedule1.png]]</center>
<center>[[Image:member_schedule2.png]</center>
+
<center>[[Image:member_schedule2.png]]</center>
 
  |}
 
  |}

Revision as of 14:10, 3 October 2012

Curve border.pngCurve border.pngCurve border.pngCurve border.pngCurve border.pngCurve border.png

Home About Our Team Project Description Documentation Project Management Technologies & References Team Reflections
Project Progress Metrics Minutes User Acceptance Test System Test Programming Logs

Curve border.pngCurve border.pngCurve border.pngCurve border.pngCurve border.pngCurve border.png

Project Milestone

Project Milestone
Project Milestone (Updated 14 September 2012).jpg

Project Schedule

Project Milestone
Media:Project Schedule Team SincereNet 14September2012.pdf

Project Risk Description

S/N Risk description Type of risk Likelihood Impact Risk rating Mitigation Strategy
1
Our lead developer decides to leave the team
Technical High High A
  • Replace the lead developer with the next best experienced team member
  • Allocate sufficient time to familiarize with the Android mobile application environment
  • 2
    As most of us are not technically strong in programming, we need to learn and familiarize with the various programming languages and the usage of software tools such as Android Development on Eclipse, PHP, Javascript, WampServer, Web Development with Drupal etc.
    Technical High High A
  • Do research before dealing with databases.
  • Allocate time to try out and familiarize integrating the mobile application with the web development.
  • 3
    The mobile application that we develop need to integrate with their current web development at the B1G1 web portal
    Technical Medium High A
  • Allocate time to familiarize with the technologies that we need to use..
  • Have training sessions where the team member who is more familiar can teach the other team members.
  • 4
    Client may initiate unexpected changes during the course of project which could result in the change of project scope.
    External Low Medium C
  • Decide and work on the final project scope after discussion with client on the impacts of the changes such as deadlines and implications that may occur as a result of change.
  • Ensure that everyone in the team knows that there is a change in project scope.
  • Ensure everyone agrees with the new direction of the scope.
  • The project schedule needs to be changed
  • Inform our supervisor about the change
  • 5
    Encounter problems in completing complex functions such as instant messaging.
    Technical / Schedule Medium Medium B
  • Inform project manager immediately of potential delay in the completion of functionality.
  • Seek help from supervisor or assign more resources to complete the function
  • Project schedule may need to be reviewed.
  • 6
    Deployment errors may occur as we are using the client’s server and deployment software.
    Technical Medium Medium B
  • Deployment to be done after each or every 2 iterations rather than at the end of the project so that there would be additional time to fix deployment errors.
  • 7
    The user interface developed may not appear identical to the UI mockup
    Technical Medium Low C
  • The UI design may need to be reviewed with the sponsor
  • 8
    The sponsor is not willing to allow the team to access and make changes directly to the main database
    Technical Low High B
  • Discuss with the sponsor for alternative solution (i.e access to a mock database that has the same database structure, find out other database solutions)
  • 9
    Deploy the Drupal Web application to B1G1 production web server
    Technical Medium High A
  • Collaborate with our technical advisor (Pravin) to aid in the proper deployment of our Drupal Web application into B1G1 Production server.
  • 10
    Crash client's database and production server
    Technical Medium High A
  • Consult with Pravin on the necessary procedures to resolve and revert to previous safe version release.
  • 11
    Collaboration with Technical Advisor (Pravin) discontinues
    Technical Medium Medium B
  • Seek a new technical advisor from our Project Sponsor, and adopt independent team learning.
  • Continuity & Communications Plan

    Description Duration Risk Level Action Taken
    Team member is sick or on medical leave. < 3 days Low
  • Project manager may assign stand-in member to do the member’s assigned work.
  • 3 – 7 days Low
  • Project manager assign stand-in member to do the sick member’s assigned work.
  • Reschedule of project schedule may be required.
  • The stand-in member assigned to take over the work temporarily must update the progress to that member responsible.
  • > 7 days Low
  • Project manager have to reassign and redistribute workload among other team members.
  • Reschedule of project schedule may be required.
  • The stand-in member assigned to take over the work temporarily must update the progress to that member responsible.
  • Team member has to rush for assignment due or has a major quiz for other modules. < 3 days Moderate
  • Project manager may assign stand-in member to do the member’s assigned work.
  • 3 – 7 days Moderate
  • Project manager assign stand-in member to do the sick member’s assigned work.
  • Reschedule of project schedule may be required.
  • The stand-in member assigned to take over the work temporarily must update the progress to that member responsible.
  • Team member has other commitments in the midst of the project < 3 days Low
  • Project manager may assign stand-in member to do the member’s assigned work.
  • 3 - 7 days Moderate
  • Project manager have to reassign and redistribute workload among other team members.
  • Reschedule of project schedule may be required.
  • The stand-in member assigned to take over the work temporarily must update the progress to that member responsible.
  • Project Risk Metric

    Project Milestone
    Risk Metric SN.png

    Bug Metrics

    Bug Metrics
    Bug Severity SN.png
    Bug Calculation SN.png
    Bug Score SN.png

    Member Schedule

    Bug Metrics
    Member schedule1.png
    Member schedule2.png