HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 122: Line 122:
 
<li>Update database & diagrams</li>
 
<li>Update database & diagrams</li>
 
</ul>
 
</ul>
|Proposal
+
|
 
|23 May 2014
 
|23 May 2014
 
|12 Jun 2014
 
|12 Jun 2014
Line 158: Line 158:
 
<li>Update wiki page & project progress</li>
 
<li>Update wiki page & project progress</li>
 
</ul>
 
</ul>
|Proposal
+
|
 
|11 Jul 2014
 
|11 Jul 2014
 
|31 Jul 2014
 
|31 Jul 2014

Revision as of 12:18, 10 June 2014

Chocoliciousmenu.jpg
Overview Project Management Documentation
1. Project Progress 1. Our Team 1. Meeting Minutes
2. Project Description 2. Time Line 2. Database
3. Stakeholders 3. Schedule 3. Use Cases
4. Scope 4. Risks & Constraints 4. System Diagram
5. Learning Outcomes 5. Metrics 5. Test Cases

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
23 May 2014 12 Jun 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

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 Probability
(1-3)
Effects
(1-3)
Priority
(P x E)
Strategy
Medical Certificate or Leave Of Absence

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.

Low (1) Medium (2) 2 Risk mitigation

Reorganize team such that everyone understands each other’s job.

Minimal knowledge about new languages

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.

Medium (2) Medium (2) 4 Risk Contingency

Source for other resources that might be able to help us better understand the topic

Minimal knowledge on accounting related software or tools

We have no knowledge on accounting software or accounting related tools.

Medium (2) Medium (2) 4 Risk Contingency

Source for tutorials that might be able to help us better understand the tools or software.

Understanding of Software Tutorial

Tutorials found are mainly not meant for starters; hence understanding of the tutorial can be a problem as it might be time consuming.

Medium (2) Low (1) 2 Risk Contingency

Source for other tutorials that might be able to help us better understand how to use the software

Requirements Changes

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 Risk mitigation

Reorganize team such that everyone understands each other’s job.

Personal Reasons

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.

Low (1) Low (1) 1 Risk Avoidance

The project is our main priority hence it is important that we put the project above all else.

Hardware Unavailability

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) 3 Risk Contingency

Ensure that other companies will be able to back up for the essential hardware.

Incomplete Tasks

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 Risk Avoidance

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.

Miscommunication

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.

Low (1) Medium (2) 2 Risk Mitigation

Have more discussion among the team, so to ensure that the final decision is agreeable by all the team members.

Work Efficiency

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 Risk Avoidance

Risk Avoidance Work together in the lab so to avoid slowing down the process for the other group members.

Technical Risk
Possible Risk Probability
(1-3)
Effects
(1-3)
Priority
(P x E)
Strategy
Defective Components

Lab machines might be faulty which result in us not being able to fulfil our task.

Low (1) High (3) 3 Risk Avoidance

Replace faulty components or get help from IT HELP DESK.

Data Loss

Thumb drive or hard disk might be corrupted and is unable to retrieve the information.

Low (1) High (3) 3 Risk Contingency

Have backup copies of our work with each and every one in the team.

Business Risk
Possible Risk Probability
(1-3)
Effects
(1-3)
Priority
(P x E)
Strategy
Product Competition

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 Risk Contingency

Ensure that our product is made better than our competitors.

Metrics