HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2014T1 Chocolicious Proj Management"

From IS480
Jump to navigation Jump to search
Line 505: Line 505:
 
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%"
 
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%"
 
|-
 
|-
! scope="row" colspan="5" | Project Risk
+
! scope="row" colspan="6" | Project Risk
 
|-
 
|-
! style="width:50%"|Possible Risk  
+
! style="width:50%"|Possible Risk || Reason & Implications
 
!Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy
 
!Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy
 
|-
 
|-
|<b>Medical Certificate or Leave Of Absence</b><br>
+
|<b>Medical Certificate (MC) / Leave of Absence (LOA)</b><br>
MC or LOA might be inevitable due to personal reason, such as falling sick due to over commitment or applying of LOA    due to unforeseen circumstances.
+
|<b> Reason</b>
 +
<li>Falling sick
 +
<li>Personal reasons
 +
<li>Unforeseen circumstances
 +
<br />
 +
<br />
 +
<b> Implications</b>
 +
Allocated work may not be completed on time
 
|Low (1)
 
|Low (1)
 
|Medium (2)
 
|Medium (2)
 
|2
 
|2
|<b>Risk mitigation</b><br>
+
|Project Manager to reschedule tasks or reallocate tasks to another member.
Reorganize team such that everyone understands each other’s job.
+
<br />Buffer days should be included in project schedule to accommodate such situations.
 +
 
 +
 
 
|-
 
|-
|<b>Minimal knowledge about new languages </b><br>
+
|<b>Minimal or lack thereof knowledge on <li>accounting-related software/tools<li>frameworks <li>languages </b><br>
We have no prior knowledge on these subjects and thus have to find out through reading. We would be only receiving little help from our supervisor or friends thus we have to do our own research to better understand the concept of these subjects.
+
|<b> Reason</b><br /> Not learned prior to start of project.
 +
<br />
 +
<b> Implications</b><br />
 +
Additional time will need to be allocated for learning the language and framework
 
|Medium (2)
 
|Medium (2)
 
|Medium (2)
 
|Medium (2)
 
|4
 
|4
|<b>Risk Contingency</b><br>
+
|Project Manager to allocate time for collaborative learning for the team. <br />&nbsp;
Source for other resources that might be able to help us better understand the topic
+
Lead Developer to organize meetings to facilitate team learning.<br />
 +
<br /> Team to speak with SMUSA accountant. <br />
 +
 
 +
 
 
|-
 
|-
|<b>Minimal knowledge on accounting related software or tools</b><br>
+
|<b>Change of project requirements</b><br>
We have no knowledge on accounting software or accounting related tools.
+
|<b>Reason</b><br /> Current requirements no longer fits client’s needs
 +
<br />
 +
<b>Implications</b><br />
 +
Delay in project completion date
 
|Medium (2)
 
|Medium (2)
|Medium (2)
+
|Medium (3)
|4
+
|6
|<b>Risk Contingency</b><br>
+
|Project Manager to adjust project schedule to accommodate the changes.<br />&nbsp;
Source for tutorials that might be able to help us better understand the tools or software.
+
Business Analyst to update team on the change of requirements.<br />
 +
<br />System Analyst and Quality Assurance Analyst to ensure that team changes codes in accordance to change in requirements without affecting code quality.
 +
 
 +
 
 
|-
 
|-
|<b>Understanding of Software Tutorial</b><br>
+
|<b>Hardware unavailability</b><br>
Tutorials found are mainly not meant for starters; hence understanding of the tutorial can be a problem as it might be time consuming.
+
|<b>Reason</b><br /> Laptop crash
 +
<br />
 +
<b>Implications</b><br />
 +
Member whose laptop has crashed will require time to either repair it or get a new laptop and re-install all required programs
 
|Medium (2)
 
|Medium (2)
|Low (1)
+
|Low (3)
|2
 
|<b>Risk Contingency</b><br>
 
Source for other tutorials that might be able to help us better understand how to use the software
 
|-
 
|<b>Requirements Changes</b><br>
 
We might make changes to the project’s requirement so to better fit the objective, which will result in our work being delayed.
 
|Medium (2)
 
|High (3)
 
 
|6
 
|6
|<b>Risk mitigation</b><br>
+
|Project Manager to reschedule tasks or reallocate tasks to another member.<br />&nbsp;
Reorganize team such that everyone understands each other’s job.
+
Member may be able to borrow laptop from team members to complete immediate tasks.
 +
 
 +
 
 
|-
 
|-
|<b>Personal Reasons</b><br>
+
|<b>Incomplete tasks</b><br>
Due to very personal reason such as family day, birthday or functions that we must attend, we might have to leave earlier than expected; this might drag down the overall performance of the team. 
+
|<b>Reason</b><br /> Unable to code out the function
|Low (1)
+
<br />
|Low (1)
+
<b>Implications</b><br />
|1
+
Deviations from project schedule will affect the whole team
|<b>Risk Avoidance</b><br>
+
|Medium (1)
The project is our main priority hence it is important that we put the project above all else.
 
|-
 
|<b>Hardware Unavailability</b><br>
 
Our laptop machines where the programs are installed might not be working or might be faulty and thus we are unable to carry out our task as accordingly.
 
|Low (1)
 
 
|High (3)
 
|High (3)
 
|3
 
|3
|<b>Risk Contingency</b><br>
+
|Project Manager to reschedule tasks or reallocate tasks to another member.<br />
Ensure that other companies will be able to back up for the essential hardware.
+
<br />Member may be able to borrow laptop from team members to complete immediate tasks.
|-
+
 
|<b>Incomplete Tasks</b><br>
+
 
If anyone were to not complete the designated task on time it will drag down the rest, this will then result in incomplete submission when it’s due.
 
|Low (1)
 
|High (3)
 
|3
 
|<b>Risk Avoidance</b><br>
 
We will be working on our project in school during the weekdays and we will also be working from home during the weekends so that we are able to fulfil our task.
 
 
|-
 
|-
 
|<b>Miscommunication</b><br>
 
|<b>Miscommunication</b><br>
Due to different ideas generated by each members not all might agree thus leading to communication problems, such as getting of the wrong ideas across and unable to make up final decision.
+
|<b>Reason</b><br /> The idea was not presented or understood correctly
 +
<br />
 +
<b>Implications</b><br />
 +
Time spent wrongly on things not required
 
|Low (1)
 
|Low (1)
|Medium (2)
+
|High (2)
 
|2
 
|2
|<b>Risk Mitigation</b><br>
+
|Business Analyst to ensure that each team member fully understands exactly what he/she is to accomplish.<br />
Have more discussion among the team, so to ensure that the final decision is agreeable by all the team members.
+
<br />Project Manager to allocate some time for team member to rectify the mistakes.
|-
+
 
|<b>Work Efficiency</b><br>
 
Each of the members work at a different pace thus accommodating each and every one might slow down the process. Task might not be completed in time, due to the large work scope.
 
|Medium (2)
 
|Medium (3)
 
|6
 
|<b>Risk Avoidance</b><br>
 
Risk Avoidance
 
Work together in the lab so to avoid slowing down the process for the other group members.
 
|}
 
  
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%"
 
|-
 
! scope="row" colspan="5" | Technical Risk
 
|-
 
! style="width:50%"|Possible Risk
 
! Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy
 
 
|-
 
|-
|<b>Defective Components</b><br>
+
|<b>Conflicts among team members</b><br>
Lab machines might be faulty which result in us not being able to fulfil our task.
+
|<b>Reason</b><br /> Team members might have a difference in opinion on how things should be done and unable to solve it on their own
 +
<br />
 +
<b>Implications</b><br />
 +
Such conflicts impede smooth project flow
 
|Low (1)
 
|Low (1)
|High (3)
+
|High (2)
|3
+
|2
|<b>Risk Avoidance</b><br>
+
|Project Manager to arrange meeting for team to come together and talk things out.
Replace faulty components or get help from IT HELP DESK.
 
|-
 
|<b>Data Loss</b><br>
 
Thumb drive or hard disk might be corrupted and is unable to retrieve the information.
 
|Low (1)
 
|High (3)
 
|3
 
|<b>Risk Contingency</b><br>
 
Have backup copies of our work with each and every one in the team.
 
|}
 
  
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%"
 
|-
 
! scope="row" colspan="5" | Business Risk
 
|-
 
! style="width:50%"|Possible Risk
 
! Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy
 
|-
 
|<b>Product Competition</b><br>
 
Different service or products similar to ours hence we have to make sure that our service is competitive so that we can meet the expected standard of us.
 
|Low (1)
 
|High (3)
 
|3
 
|<b>Risk Contingency</b><br>
 
Ensure that our product is made better than our competitors.
 
 
|}
 
|}
  
 
==Metrics==
 
==Metrics==

Revision as of 12:31, 17 June 2014

Chocoliciousmenu.jpg

Our Team

Time Line

ScheduleChoco.png

Schedule

Planned Actual
Iter Tasks Milestone Start End Start End
1 Preparation
  • Documentation & Requirement Gathering
  • Research on Technologies
  • Setup necessary software
  • Develop project proposal

Project Management

  • Team roles & management
  • Project Schedule
  • Risk Assessment
  • Learning Outcome

Technical Requirements

  • Develop Use Case Diagram
  • Draft database entity
23 May 2014
12 Jun 2014
23 May 2014
2 Management & Documentation
  • Finalise project proposal
  • Prepare project writeup on wiki
  • Refine UCD
  • Develop diagrams
Proposal deadline

Coding Tasks

  • Develop mock UI & framework
  • Build up database
  • Login & authentication
  • Grant user roles
  • Create claims
  • Save function for unsubmitted claims
  • Edit/ update claims
  • View claims

Testing

  • Develop test cases for revelant functions
  • Integration testing
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
Proposal
18 Jun 2014
13 Jun 2014
26 Jun 2014
3 Coding Tasks
  • Refine UI and develop UI for relevant functions
  • Code for submission/editing of claims to relevant parties
  • Code for viewing/editting of all accounts for SMUSA Fin sec
  • Code for viewing/editting of accounts for users of different level

Testing

  • Develop test cases for revelant functions
  • Integration testing
  • Debugging

Management & Documentation

  • Update wiki page & project progress
  • Update database & diagrams
27 Jun 2014
10 Jul 2014
4 Management
  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Approval of claims
  • Rejection of claims
  • Resubmission of rejected claims
  • Report generation for claims
  • Filtering of reports for relevant user type
  • Reject claims due to error
  • Change of claims status

Testing

  • Develop test cases for revelant functions
  • Integration testing
  • Debugging

Documentation

  • Update wiki page & project progress
11 Jul 2014
31 Jul 2014
5 Management
  • Revise documentations / wiki page
  • Prepare for acceptance presentation
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Submit budget
  • Propose budget (save function for individual account)
  • Code for SMUSA CBD & SMUSA fin sec to edit submitted budget

Testing

  • Develop test cases for revelant functions
  • Integration testing
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
Acceptance Presentation
Acceptance Presentation
14 Aug 2014
1 Aug 2014
14 Aug 2014
6 Management
  • Revise documentations / wiki page
  • Prepare for acceptance presentation
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Code for SMUSA fin sec to allocate funds (from SAC account to every clubs' expenditure account)
  • Code for deposit revenue into expenditure account (CBD fin sec & SMUSA sec)

Testing

  • Develop test cases for revelant functions
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
15 Aug 2014
28 Aug 2014
7 Management
  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Fund transfer between CBD & Club fin sec
  • Report generation for fund transactions

Testing

  • Integration testing
  • Develop test cases for revelant functions
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
29 Aug 2014
11 Sep 2014
8 Management
  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Inject funds from SAC reserve
  • Pull back funds from SAC reserve
  • Viewing of expenditure & SAC account
  • Report generation of transaction of pullback and allocation

Testing

  • Integration testing
  • Develop test cases for revelant functions
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
12 Sep 2014
25 Sep 2014
9

Mid term preparation

Management

  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Code for SMUSA fin sec to change reserve limit
  • Editalble pull back formula for SMUSA fin sec
  • Viewing of reserve account
  • Report generation of transaction of pullback and allocation

Testing

  • Integration testing
  • Develop test cases for revelant functions
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
Mid Term Presentation
Mid Term Presentation
10 Oct 2014
26 Sep 2014
10 Oct 2014
10 Management
  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Code for SMUSA fin sec to approve reserve withdrawal
  • Code for request reserve withdrawal (CBD & Club fin sec)
  • Report generation of transaction history

Testing

  • Integration testing
  • Develop test cases for revelant functions
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
11 Oct 2014
23 Oct 2014
11 Management
  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Code for concurrency control

Testing

  • Testing
  • Develop test cases for revelant functions
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
24 Oct 2014
6 Nov 2014
12

Prepare for Poster Day

Management

  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions

Testing

  • Testing
  • Develop test cases for revelant functions
  • Debugging
Poster Day

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
Poster Day
10 Nov 2014
7 Nov 2014
20 Nov 2014
13

Prepare for Final Presentation
Prepare for Poster Day

Management

  • Revise documentations / wiki page

Testing

  • Final round of testing
Final Presentation
Poster Day

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
Final Presentation
24 Nov - 2 Dec 2014
Poster Day
3 Dec 2014
21 Nov 2014
3 Dec 2014

Risks & Constraints

Risk Table

Probability 1-low 2-medium 3-high
Effect 1-low 2-medium 3-high
Priority Higher number more important
Project Risk
Possible Risk Reason & Implications Probability
(1-3)
Effects
(1-3)
Priority
(P x E)
Strategy
Medical Certificate (MC) / Leave of Absence (LOA)
Reason
  • Falling sick
  • Personal reasons
  • Unforeseen circumstances

    Implications Allocated work may not be completed on time
  • Low (1) Medium (2) 2 Project Manager to reschedule tasks or reallocate tasks to another member.


    Buffer days should be included in project schedule to accommodate such situations.


    Minimal or lack thereof knowledge on
  • accounting-related software/tools
  • frameworks
  • languages
  • Reason
    Not learned prior to start of project.


    Implications
    Additional time will need to be allocated for learning the language and framework

    Medium (2) Medium (2) 4 Project Manager to allocate time for collaborative learning for the team.
     

    Lead Developer to organize meetings to facilitate team learning.

    Team to speak with SMUSA accountant.


    Change of project requirements
    Reason
    Current requirements no longer fits client’s needs


    Implications
    Delay in project completion date

    Medium (2) Medium (3) 6 Project Manager to adjust project schedule to accommodate the changes.
     

    Business Analyst to update team on the change of requirements.

    System Analyst and Quality Assurance Analyst to ensure that team changes codes in accordance to change in requirements without affecting code quality.


    Hardware unavailability
    Reason
    Laptop crash


    Implications
    Member whose laptop has crashed will require time to either repair it or get a new laptop and re-install all required programs

    Medium (2) Low (3) 6 Project Manager to reschedule tasks or reallocate tasks to another member.
     

    Member may be able to borrow laptop from team members to complete immediate tasks.


    Incomplete tasks
    Reason
    Unable to code out the function


    Implications
    Deviations from project schedule will affect the whole team

    Medium (1) High (3) 3 Project Manager to reschedule tasks or reallocate tasks to another member.


    Member may be able to borrow laptop from team members to complete immediate tasks.


    Miscommunication
    Reason
    The idea was not presented or understood correctly


    Implications
    Time spent wrongly on things not required

    Low (1) High (2) 2 Business Analyst to ensure that each team member fully understands exactly what he/she is to accomplish.


    Project Manager to allocate some time for team member to rectify the mistakes.


    Conflicts among team members
    Reason
    Team members might have a difference in opinion on how things should be done and unable to solve it on their own


    Implications
    Such conflicts impede smooth project flow

    Low (1) High (2) 2 Project Manager to arrange meeting for team to come together and talk things out.

    Metrics