HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 513: Line 513:
 
|<b>Project may not be accepted</b><br>
 
|<b>Project may not be accepted</b><br>
 
|<b>Implications/Reason</b>
 
|<b>Implications/Reason</b>
Project is being done for the third time.
+
Project is being done for the third time
 
<br />
 
<br />
 
|Medium(2)
 
|Medium(2)
Line 524: Line 524:
 
|<b>Incompatibility with client’s server when application is deployed</b><br>
 
|<b>Incompatibility with client’s server when application is deployed</b><br>
 
|<b>Implications/Reason</b>
 
|<b>Implications/Reason</b>
Client has their own server/domain.
+
Client has their own server/domain
 
<br />
 
<br />
 
|Low (1)
 
|Low (1)
Line 536: Line 536:
 
|<b>Underestimation of scope during development and testing</b><br>
 
|<b>Underestimation of scope during development and testing</b><br>
 
|<b>Implications/Reason</b>
 
|<b>Implications/Reason</b>
Over-confidence of development ability.
+
Over-confidence of development ability
 
<br />
 
<br />
 
|Low (1)
 
|Low (1)
Line 548: Line 548:
 
|<b>Insufficient users for testing</b><br>
 
|<b>Insufficient users for testing</b><br>
 
|<b>Implications/Reason</b>
 
|<b>Implications/Reason</b>
Lack of incentives for users to do testing for us.
+
Lack of incentives for users to do testing for us
 
<br />
 
<br />
 
|Medium(2)
 
|Medium(2)
Line 559: Line 559:
 
|<b>Inaccurate feedback given by testers</b><br>
 
|<b>Inaccurate feedback given by testers</b><br>
 
|<b>Implications/Reason</b>
 
|<b>Implications/Reason</b>
Wrong testing mind-set (i.e. purpose of test is to show that application works, not to find defects or testers’ lack of commitment to support the testing efforts).
+
Wrong testing mind-set (i.e. purpose of test is to show that application works, not to find defects or testers’ lack of commitment to support the testing efforts)
 
<br />
 
<br />
 
|Medium(2)
 
|Medium(2)
Line 662: Line 662:
 
|<b>Project is not taken up by SMUSA after completion</b><br>
 
|<b>Project is not taken up by SMUSA after completion</b><br>
 
|<b> Implications/Reason</b>
 
|<b> Implications/Reason</b>
Users are not comfortable with the system and opt instead to revert back to their old way of doing things.
+
Users are not comfortable with the system and opt instead to revert back to their old way of doing things
 
<br />
 
<br />
 
|High (3)
 
|High (3)
Line 674: Line 674:
 
|<b>SMUSA does not know how to operate the system</b><br>
 
|<b>SMUSA does not know how to operate the system</b><br>
 
|<b> Implications/Reason</b>
 
|<b> Implications/Reason</b>
SMUSA lacks technical knowledge.
+
SMUSA lacks technical knowledge
 
<br />
 
<br />
 
|Medium(2)
 
|Medium(2)
Line 685: Line 685:
 
|<b>Miscommunication between Business Analyst and SMUSA</b><br>
 
|<b>Miscommunication between Business Analyst and SMUSA</b><br>
 
|<b> Implications/Reason</b>
 
|<b> Implications/Reason</b>
Language interpretation issues.
+
Language interpretation issues
 
<br />
 
<br />
 
|High(3)
 
|High(3)

Revision as of 17:20, 7 July 2014

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

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
12 Jun 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
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
27 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
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
Project may not be accepted
Implications/Reason

Project is being done for the third time

Medium(2) High(3) 6 Do our best to satisfy expectations of Course Coordinator.


Incompatibility with client’s server when application is deployed
Implications/Reason

Client has their own server/domain

Low (1) High(3) 3 Project Manager to search for plausible solutions.


Lead Developer to explore deploying on other servers in case compatibility issues cannot be resolved.


Underestimation of scope during development and testing
Implications/Reason

Over-confidence of development ability

Low (1) High(3) 3 Project Manager to allocate buffer time in schedule and monitor schedule metrics closely. Scheduling of tasks to be adjusted according to metrics.


Team to seek advice from supervisor as to whether certain functionalities should be dropped.


Insufficient users for testing
Implications/Reason

Lack of incentives for users to do testing for us

Medium(2) Medium(2) 4 Business Analyst to discuss with sponsors to provide users with incentives.


Inaccurate feedback given by testers
Implications/Reason

Wrong testing mind-set (i.e. purpose of test is to show that application works, not to find defects or testers’ lack of commitment to support the testing efforts)

Medium(2) Medium(2) 4 Team to get non-IT users for testing to ensure that feedback is more applicable to the generic public to ensure user-friendliness.


Testers to be briefed and encouraged to test the application without reservations.






Team Risk
Possible Risk Reason & Implications Probability
(1-3)
Effects
(1-3)
Priority
(P x E)
Strategy
Team is faced with technical difficulties
Implications/Reason

Inadequate skills

Medium(2) High(3) 6 Lead Developer to learn these new skills and teach team.


Systems analyst to research on other methods/technologies that could provide an easier solution.


Team member is faced with sudden illness
Implications/Reason

Virus attack

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


Project Manager to include buffer days in project schedule to accommodate such situations.


Team member drops module at the eleventh hour
Implications/Reason

Inability to cope

Low(1) High(3) 3 Project Manager to reallocate tasks.


Team members to devote more time to FYP.


Malfunction of software/hardware during development phase
Implications/Reason

Software crash/hardware malfunction

Medium(2) High(3) 6 Project Manager to reschedule tasks.


Team to consistently back up all data.



Sponsor Risk
Possible Risk Reason & Implications Probability
(1-3)
Effects
(1-3)
Priority
(P x E)
Strategy
Constantly adding/changing of requirements
Implications/Reason

Sponsor unsure of all that they want from the very beginning

High(3) High(3) 9 Major changes are not permitted after agreement on requirements.


Project Manager to look at schedule for minor changes to see if project can still be completed on time if changes are accommodated.
Lead Developer and Systems Analyst to accommodate changes if changes are accepted.
Business Analyst to reject if changes are not accepted.


Project is not taken up by SMUSA after completion
Implications/Reason

Users are not comfortable with the system and opt instead to revert back to their old way of doing things

High (3) Low (1) 3 Team to organize training sessions for users.


Project Manager to assign team member to provide assistance if need be.


SMUSA does not know how to operate the system
Implications/Reason

SMUSA lacks technical knowledge

Medium(2) Low (1) 2 Business Analyst to discuss with SMUSA on whether to add user manuals.


Miscommunication between Business Analyst and SMUSA
Implications/Reason

Language interpretation issues

High(3) Low (1) 3 Team to discuss with supervisor before proceeding.

Metrics