Our Team
Time Line
Schedule
|
Planned
|
Iter |
Tasks |
Milestone |
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
|
2
|
Management & Documentation
- Finalise project proposal
- Prepare project writeup on wiki
- Refine UCD
- Develop diagrams
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
Proposal Feedback (Actions)
- Update wiki page & project progress
- Arrange for supervisor meeting for project discussion - 13-Jul-14
- Iteration 4 tasks on-hold for now.
- Deploy Minimum Viable Product (MVP)
- Incorporate the Lean Startup (where applicable) to schedule
Deploy MVP
|
Users |
Claims |
Accounts |
Budgeting
|
Create, Read, Update, Delete (C.R.U.D.)
Login
Grant user roles
Club Membership application
Acceptance & reject membership requests
Remove member
|
C.R.U.D.
Submission
Editting of submitted claims
|
R.U.
|
|
|
|
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
Deploy MVP
|
Users |
Claims |
Accounts |
Budgeting
|
C.R.U.D.
Login
Grant user roles
Club Membership application
Acceptance & reject membership requests
Remove member
|
C.R.U.D.
Submission
Editting of submitted claims
Acceptance & rejection
Resubmission
Status edit
|
R.U.
|
|
|
|
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
Deploy MVP
|
Users |
Claims |
Accounts |
Budgeting
|
C.R.U.D.
Login
Grant user roles
Club Membership application
Acceptance & reject membership requests
Remove member
|
C.R.U.D.
Submission
Editting of submitted claims
Acceptance & rejection
Resubmission
Status edit
Reports:
- Filter by User
- Claims reports generation
|
R.U.
|
C.R.U.D.
Submission
Edit submitted budget
|
|
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
Deploy MVP
|
Users |
Claims |
Accounts |
Budgeting
|
C.R.U.D.
Login
Grant user roles
Club Membership application
Acceptance & reject membership requests
Remove member
|
C.R.U.D.
Submission
Editting of submitted claims
Acceptance & rejection
Resubmission
Status edit
Reports:
- Filter by User
- Claims reports generation
|
R.U.
Funds allocation
Revenue deposit
|
C.R.U.D.
Submission
Edit submitted budget
|
|
|
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
Deploy MVP
|
Users |
Claims |
Accounts |
Budgeting
|
C.R.U.D.
Login
Grant user roles
Club Membership application
Acceptance & reject membership requests
Remove member
|
C.R.U.D.
Submission
Editting of submitted claims
Acceptance & rejection
Resubmission
Status edit
Reports:
- Filter by User
- Claims reports generation
|
R.U.
Funds allocation
Revenue deposit
Funds transfer
Funds transaction
Reports:
|
C.R.U.D.
Submission
Edit submitted budget
|
|
|
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
Deploy MVP
|
Users |
Claims |
Accounts |
Budgeting
|
C.R.U.D.
Login
Grant user roles
Club Membership application
Acceptance & reject membership requests
Remove member
|
C.R.U.D.
Submission
Editting of submitted claims
Acceptance & rejection
Resubmission
Status edit
Reports:
- Filter by User
- Claims reports generation
|
R.U.
Funds allocation
Revenue deposit
Funds transfer
Funds transaction
Reports:
SAC accounts
Funds injection
Pullback
Reports:
- Funds transaction report
- Pullback reports
- Allocation reports(partial)
|
C.R.U.D.
Submission
Edit submitted budget
|
|
|
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
Deploy MVP
|
Users |
Claims |
Accounts |
Budgeting
|
C.R.U.D.
Login
Grant user roles
Club Membership application
Acceptance & reject membership requests
Remove member
|
C.R.U.D.
Submission
Editting of submitted claims
Acceptance & rejection
Resubmission
Status edit
Reports:
- Filter by User
- Claims reports generation
|
R.U.
Funds allocation
Revenue deposit
Funds transfer
Funds transaction
Changing Reserve accounts' limit
Modify Pullback formula
Reports:
- Funds transaction report
- Pullback reports
- Allocation reports
SAC accounts
Funds injection
Pullback
Reports:
- Funds transaction report
- Pullback reports
- Allocation reports
|
C.R.U.D.
Submission
Edit submitted budget
|
|
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
Deploy MVP
|
Users |
Claims |
Accounts |
Budgeting
|
C.R.U.D.
Login
Grant user roles
Club Membership application
Acceptance & reject membership requests
Remove member
|
C.R.U.D.
Submission
Editting of submitted claims
Acceptance & rejection
Resubmission
Status edit
Reports:
- Filter by User
- Claims reports generation
|
R.U.
Funds allocation
Revenue deposit
Funds transfer
Funds transaction
Changing Reserve accounts' limit
Modify Pullback formula
Request reserve withdrawal
Approve & Reject reserve withdrawal request
Reports:
- Funds transaction report
- Pullback reports
- Allocation reports
- Transaction history report
SAC accounts
Funds injection
Pullback
Reports:
- Funds transaction report
- Pullback reports
- Allocation reports
|
C.R.U.D.
Submission
Edit submitted budget
|
|
|
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
Deploy Fully Functioning System
|
Users |
Claims |
Accounts |
Budgeting
|
C.R.U.D.
Login
Grant user roles
Club Membership application
Acceptance & reject membership requests
Remove member
|
C.R.U.D.
Submission
Editting of submitted claims
Acceptance & rejection
Resubmission
Status edit
Reports:
- Filter by User
- Claims reports generation
|
R.U.
Funds allocation
Revenue deposit
Funds transfer
Funds transaction
Changing Reserve accounts' limit
Modify Pullback formula
Request reserve withdrawal
Approve & Reject reserve withdrawal request
Reports:
- Funds transaction report
- Pullback reports
- Allocation reports
- Transaction history report
SAC accounts
Funds injection
Pullback
Reports:
- Funds transaction report
- Pullback reports
- Allocation reports
|
C.R.U.D.
Submission
Edit submitted budget
|
|
|
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
Documentation
- Update revelant documents & progress
- Update wiki page & project progress
Deploy Fully Functioning System
|
Users |
Claims |
Accounts |
Budgeting
|
C.R.U.D.
Login
Grant user roles
Club Membership application
Acceptance & reject membership requests
Remove member
|
C.R.U.D.
Submission
Editting of submitted claims
Acceptance & rejection
Resubmission
Status edit
Reports:
- Filter by User
- Claims reports generation
|
R.U.
Funds allocation
Revenue deposit
Funds transfer
Funds transaction
Changing Reserve accounts' limit
Modify Pullback formula
Request reserve withdrawal
Approve & Reject reserve withdrawal request
Reports:
- Funds transaction report
- Pullback reports
- Allocation reports
- Transaction history report
SAC accounts
Funds injection
Pullback
Reports:
- Funds transaction report
- Pullback reports
- Allocation reports
|
C.R.U.D.
Submission
Edit submitted budget
|
|
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 Presentation Poster Day
|
Documentation
- Update revelant documents & progress
- Update wiki page & project progress
Deploy Fully Functioning System
|
Users |
Claims |
Accounts |
Budgeting
|
C.R.U.D.
Login
Grant user roles
Club Membership application
Acceptance & reject membership requests
Remove member
|
C.R.U.D.
Submission
Editting of submitted claims
Acceptance & rejection
Resubmission
Status edit
Reports:
- Filter by User
- Claims reports generation
|
R.U.
Funds allocation
Revenue deposit
Funds transfer
Funds transaction
Changing Reserve accounts' limit
Modify Pullback formula
Request reserve withdrawal
Approve & Reject reserve withdrawal request
Reports:
- Funds transaction report
- Pullback reports
- Allocation reports
- Transaction history report
SAC accounts
Funds injection
Pullback
Reports:
- Funds transaction report
- Pullback reports
- Allocation reports
|
C.R.U.D.
Submission
Edit submitted budget
|
|
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
Schedule Metrics
The formula for calculating schedule metrics is as follows: Estimated time / Actual Time * 100
Score (S) tiers |
Actions to take
|
S <= 50%
|
Team's progress is TOO SLOW!!!
- Reflect on progress and reassess schedule.
- Consider dropping functions.
|
50% < S <= 90%
|
Team's progress is too slow. Tasks are possibly under-estimated.
- Consider the possibility of tasks being under-estimated.
- Use buffer days if available.
- If there are no buffer days available, consider dropping functions.
|
90% < S <= 110%
|
Estimations are fairly accurate.
|
110% < S <= 150%
|
Team's progress is too fast
- Reflect on progress and reassess schedule.
- Add number of days gained as buffer days.
|
150% < S
|
Team's progress is TOO FAST!!!
- Mitigations are the same as the previous tier.
|
Iteration
|
Planned
|
Duration
|
Actual
|
Duration
|
Score
|
Remarks
|
Start Date |
End Date
|
Start Date |
End Date
|
1 |
23-May-14 |
12-Jun-14 |
20 |
23-May-14 |
12-Jun-14 |
20 |
1 |
|
2 |
13-Jun-14 |
26-Jun-14 |
13 |
13-May-14 |
26-Jun-14 |
13 |
1 |
|
3 |
27-Jun-14 |
10-Jul-14 |
13 |
27-Jun-14 |
10-Jul-14 |
13 |
1 |
Changed Proj framework, integrate with Lean Startup's Minimum Viable Product
|
4 |
11-Jul-14 |
31-Jul-14 |
20 |
11-Jul-14 |
|
|
|
On hold for now, meet supervisor first
|
5 |
1-Aug-14 |
14-Aug-14 |
13 |
|
|
|
|
|
6 |
15-Aug-14 |
28-Aug-14 |
13 |
|
|
|
|
|
7 |
29-Aug-14 |
11-Sep-14 |
13 |
|
|
|
|
|
8 |
12-Sep-14 |
25-Sep-14 |
13 |
|
|
|
|
|
9 |
26-Sep-14 |
10-Oct-14 |
14 |
|
|
|
|
|
10 |
11-Oct-14 |
23-Oct-14 |
12 |
|
|
|
|
|
11 |
24-Oct-14 |
6-Nov-14 |
13 |
|
|
|
|
|
12 |
7-Nov-14 |
20-Nov-14 |
13 |
|
|
|
|
|
13 |
21-Nov-14 |
3-Dec-14 |
12 |
|
|
|
|
|
Bug Metrics
Severity |
Description
|
Low impact (1 point)
|
Unimportant. Typo error or small user interface alignment issues.
|
High impact (5 points)
|
The system runs. However, some non-critical functionalities are not working.
|
Critical impact (10 points)
|
The system is down or is usable after a short period of time. We have to fix the bugs to continue.
|
Points Calculation: Total = 1 x num (low) + 5 x num (high) + 10 x num (critical)
Points in iteration (P) |
Action
|
P <= 5
|
Fix during buffer time only.
|
5 < P < 10
|
Use the planned debugging time.
|
10 <= P
|
Stop current development and resolve the bug immediately. Project Manager reschedules the project.
|