final presentation - wiki.smu.edu.sg€¦ · final presentation 21st apr 2014 team zora tan yun xi...
TRANSCRIPT
21/4/2014
1
FINAL presentation 21st APR 2014
Team zora
Tan Yun Xi Business Analyst
Tan Mei Zhen Quality Analyst (Assistant PM)
Fiona Woo Project Manager
Lee Yi Xian System Analyst
Lim Ken Khoon Lead Developer
Darryl Leong Lead Designer
21/4/2014
2
overview
• About the Sponsor
• Project Overview
• Demo
• Project Management
• Stakeholder Management & Scope/Risk
• Quality Attributes (Design)
• Technical complexity
• User testing
• X – Factors
• Handover to Client
• Learning Outcomes
OUR CLIENT – sterling engineering
• Construction Industry
• Supply, fabrication and installation of structural steel works and metal works
• Small company, size of ~ 30 employees
21/4/2014
3
Problem highlights
• Manual
• Long and tedious process
• Time consuming and inefficient
Hard copy forms
Reimbursement Form
Payment Voucher
21/4/2014
4
Project description
• A web portal for all employees to access
• Aid HR personnel and higher management in their business activities
• System customised to company’s needs
Organization structure
Higher Management (HM)
System Administrator
Managing Director (MD)
HR Personnel (HR)
21/4/2014
5
june
modules
Training and Development
Remuneration And Claims
Leave Performance Management And Appraisal
System Administration
Remuneration june
Leave
Performance Management And Appraisal
System Administration
Claim entitlement
Claim
Employee’s salary Race, nationality CPF contribution
Allowance entitlement
Leave entitlement
Appraisal metrics
Value to sponsor: extensive scope
21/4/2014
6
Training and Development
june
Leave
Performance Management And Appraisal
Remuneration
Claim
Reimbursement with salary
Unpaid Leave
Check leave taken
VWS Bonus Salary Increment
View past appraisal scores
Value to sponsor: extensive scope
Deployment
Actual Server (Live)
Hosting Server Bluehost (Client - Web Hosting Server)
URL http://hrms.sterling-portal.com
Development Server
Hosting Server Bluehost (Client - Web Hosting Server)
URL http://hris.sterling-portal.com
User Testing Server
Hosting Server Bluehost (Client – Web Hosting Server
URL http://hruat.sterling-portal.com
21/4/2014
7
Demo
Employee Username System Role
leo Employee
noel Line Manager
angeline HR Personnel
LC Higher Management
spg Managing Director
marc System Administrator
Demo URL: http://hris.sterling-portal.com
Claim
1. Submit Claim
Submit Claim
3. Validate Claim
Employee (Leo) HR Personnel (Angeline)
2. Receive pending claim
4. Receive pending claim
Higher Management (LC)
5. Approve/Reject Claim
6. Receive pending claim
7. Approve/Reject Claim
Managing Director (SPG)
8. View Claim Status
Employee (Leo)
21/4/2014
8
Claim
Edit Payment Method
1. Edit Payment Method
HR Personnel (Angeline)
Leave
3. Receive pending leave email
1. Apply unpaid leave
4. Approve leave
Apply Unpaid Leave
Line Manager (Noel)
2. View & Edit leave
5. View approved & rejected leave
Employee (Leo)
21/4/2014
9
Remuneration
Generate payslip for employees & drivers
2. View Payslip 1. Generate payslip
HR Personnel (Angeline)
Generate worker costing
1. Generate worker costing
HR Personnel (Angeline)
Performance management & appraisal
Create Employee Appraisal
Higher Management (Noel)
1. Create Regular Appraisal
21/4/2014
10
Training & Development Propose a training
Line Manager (Noel)
1. Propose a training for a
employee
2. Receive pending proposed training
HR Personnel (Angeline)
Internal
3. Approve/Reject proposed training
Managing Director (SPG)
External
2. Receive notification of the
nomination
Employee (Leo)
5. Approve/Reject proposed training
6. Manage External Training
HR Personnel (Angeline)
4. View Nominated
Training
Training & Development
Manage External Training
1. Receive Approved training
HR Personnel (Angeline)
2. Fill the payment details
3. Set the training as completed
4. Fill in the course completion details
1. Fill up and submit the training
feedback
Employee (Leo)
21/4/2014
11
Training & Development Training Feedback
2. Review Feedback HR Personnel (Angeline)
1. Fill up and submit the training
feedback
Employee (Leo) Line Manager (Noel) 2. Review Feedback
View Training Record
HR Personnel (Angeline)
1. Select Employee 2. View Training
Details
Administration
1. Manage Remuneration
Manage Remuneration
HR Personnel (Angeline)
1. Manage Claim
Manage Claim
HR Personnel (Angeline)
21/4/2014
12
Administration
Claim Fraud Notification
1. Manage Claim Fraud
Manage Claim Fraud
2. Add Simulated Claim
Employee (Leo)
System Administrator (Marc)
1. Submit Fraudulent Claim
2. Receive email notification
3. Verify claim fraud
System Administrator (Marc)
SCOPE
21/4/2014
13
NO CHANGE
CHANGE
Iteration 12
21/4/2014
14
CHANGE
Change of features • New good-to-have feature: fraud detection • Enhance core & secondary features
PROJECT SCHEDULE (ACTUAL)
21/4/2014
15
Project schedule
70% Completion of Core Features • Remuneration
(Core) • Leave • Claim • Administration • ACL • User Testing 1 • Heuristic 1 • Acceptance
90% Completion of Core Features, 40% Completion of Secondary Features • Remuneration
(Core) • Leave • Claim • Administration • Performances
Management & Appraisal
• Training & Development
100% Completion of Core Features, 70% Completion of Secondary Features • Remuneration (Core) • Claims (Core) • Leave • Performances Management &
Appraisal • Training & Development • User Test 2 • Live Deployment
23 Sep – 8 Nov 9 May– 22 Sept 9 Dec– 5 Jan 6 Jan – 16 Feb
Gathering of Requirements & Preparation for subsequent Development phases
PROJECT SCHEDULE (PLANNED)
Iteration 9 (17 Feb ~ 2 Mar) • Claims Analysis Report
• Mid-Term Presentation
17 Mar– 27 Apr
Iteration 11 (17 Mar ~ 30 Mar) • User Test 3
Iteration 10 (3 Mar ~ 16 Mar) • Remuneration (Secondary) • Training & Development • Administration • Portal Notification (Other
features)
17 Feb – 16 Mar
Iteration 12 (31 Mar ~ 13 Apr) • Live Deployment 2 • Buffer • Final Presentation • Poster Day
21/4/2014
16
PROJECT SCHEDULE (ACTUAL)
Iteration 9 (17 Feb ~ 2 Mar) • Claims Analysis Report
• Mid-Term Presentation
17 Mar– 27 Apr
Iteration 11 (17 Mar ~ 30 Mar) • Fraud Detection (Algorithm &
Email notification)
• User Test 3 Iteration 10 (3 Mar ~ 16 Mar) • Remuneration (Secondary) • Training & Development
(Training session) • Administration • Research on Fraud Detection • Portal Notification (Other
features)
17 Feb – 16 Mar
Iteration 12 (31 Mar ~ 13 Apr) • Training & Development
(Completed) • Fraud Detection (Completed)
• Live Deployment 2 (14 Apr) • User Manual Guide • Buffer • Final Presentation • Poster Day
• Addition of new feature: Fraud detection
• Splitting of Training & Development: Create more buffer time to test before UT3
Milestone completed
21/4/2014
17
Schedule metric
Score Description Action
SM < 0.9
The team is ahead of planned schedule. There is a
substantial number of days when members are not
working on any task.
- PM to re-estimate and schedule lesser time for similar tasks in future
iterations.
0.9 <= SM <= 1.1 Estimations for planned
schedule are fairly accurate. The team is roughly on track.
- No readjustments on schedule needed.
SM > 1.1
The team is behind schedule. Deadlines are not met. PM
has underestimated the duration of most tasks in this
iteration.
- PM has to re-estimate tasks for future iterations.
- Incomplete task to be rescheduled to the next iteration and deduct the
number of buffer days at the end of the phase if required.
Schedule metric
Actual Number of Days / Estimated number of days
How it is measured
• Micro view Average score is calculated for each task.
• Macro View Score calculated using the start date and end date for both the estimated and actual number of days for the entire iteration.
21/4/2014
18
Iteration1
Iteration2
Iteration3
Iteration4
Iteration5
Iteration6
Iteration7
Iteration8
Iteration9
Iteration10
Iteration11
Iteration12
Micro 1.05 0.99 0.94 1.00 1.00 0.97 0.94 0.95 1.02 0.99 1.03 1.00
Macro 1.00 1.21 1.00 0.95 0.98 1.00 1.29 1.00 1.00 1.07 1.00 0.93
0.00
0.20
0.40
0.60
0.80
1.00
1.20
1.40
Iter
atio
n S
core
Iteration Score
Micro Macro
Schedule metric Reschedule incomplete
task
No readjustments needed
No readjustments needed
Schedule metric
Iteration1
Iteration2
Iteration3
Iteration4
Iteration5
Iteration6
Iteration7
Iteration8
Iteration9
Iteration10
Iteration11
Iteration12
Micro 1.05 0.99 0.94 1.00 1.00 0.97 0.94 0.95 1.02 0.99 1.03 1.00
Macro 1.00 1.21 1.00 0.95 0.98 1.00 1.29 1.00 1.00 1.07 1.00 0.93
0.00
0.20
0.40
0.60
0.80
1.00
1.20
1.40
Iter
atio
n S
core
Iteration Score
Micro Macro
Reasons behind delay 1. Apply Leave: • More complex than we thought: • Different way of handling different
leaves 2. Upload file for leave & claim: • High difficulty level for our team
Action taken 1. Shifted incomplete tasks to other
iterations 2. Review all future tasks and break it
down further to simpler tasks
Delay in Iteration 2
Reasons behind delay 1. User Test 2 in iteration 8: • Intensive test and deployment using
Task Instructions
Action taken 1. Allocate time to do intensive testing
with task instructions before user testing 3
Delay in Iteration 7
21/4/2014
19
Total Bug Severity Points = 1 x no (low) + 5 x no (medium) + 10 x no (high)
Bug Metric Severity Value
(points) Bug Description
Low Impact (1)
Typo error or basic user interface alignment issues. Application still works on a whole.
Medium Impact (5)
Some non-critical functionalities do not work as expected. Application still works on a whole
High Impact (10)
Entire application is down or is not usable after a short period of time. Team has to stop and fix bugs before continuing.
Bug Metric
End of the iteration
Points Action Required
points < = 15 Safe: Program does not require immediate attention. Bugs to be
solved during planned debugging time.
15 < points < 30 Caution: Program has issues that require fixing. Coders to use the
planned debugging time in the iteration to solve the issue.
points > = 30 Danger: Team to meet and review project scope. Stop all current
development and resolve the bug immediately.
21/4/2014
20
5
16
25
20
11 10
8
10 11 10
12 12
0
5
10
15
20
25
30
1 2 3 4 5 6 7 8 9 10 11 12
Total Bug Score Value in each Iteration B
ug
Sco
re V
alu
e
Iteration
Caution
Safe
Mid-Term Finals
Reasons behind increase in bugs • Lack of integration testing before
System testing on server.
Action taken • Implemented a more systematic
testing protocol
Number of bugs Increase in bugs in iteration 4
Functionality Testing Integration Testing System Testing
Systematic Testing Protocol
21/4/2014
21
Change management
Feature Description
How does it value add? Implementation period
Priority level (1 – Highest to 4 – Lowest)
Additional features in Leave: - Generate Leave Report
- HR can view the different leave of all employees at one go.
Iteration 11: Together with UT3
changes
3 (Discuss with sponsor to reduce additional change scope)
Update of change tracker
Edited Change on Access Rights: - Enable HR personnel to access to feature “View
Approved & Rejected Leave”
Change management
Feature Description
How does it value add? Implementation period
Priority level (1 – Highest to 4 – Lowest)
Additional features in Claim: - Claim summary report
- Allow HR to view the breakdown of claims (claim type/claim status) in a selected period of time
- 4 (Rejection of change)
Update of change tracker
21/4/2014
22
Risk management
Likelihood Low Medium High
Impact
High B A A
Medium C B A
Low C C B
Past Activated risk
Risk Statement Consequence Lvl Mitigation Strategy /Contingency Plan
Major Changes in Client Requirement
Overall project Schedule is Delayed.
A
• Re-plan coding tasks • Re-negotiate project scope with
sponsor. • Further changes to be documented by
business analyst • Activation of Change Management Plan
Inconsistent and missing real data to be incorporated into the system
Overall project schedule is being Delayed. System becomes buggy with new data.
A
• Assign a member to clean the data before live deployment
• Set aside time to do sufficient testing before live deployment
Users are not familiar with the application when it is fully deployed.
Functionalities of the system not utilized fully
A
• Ensure sponsor (Marc) has a clear idea of the use of functionalities
• Create a user guide • Hold a HRMS training session
21/4/2014
23
Meet their needs - Engage & consult on
interest area
Key player - Focus efforts on this group - Engage & consult regularly
Least Important - Inform via general communications
Show consideration - Potential supporter - Make use of interest to
improve project
Infl
uen
ce o
f sta
keh
old
ers
Interest of stakeholders
Stakeholder management priority metric
Meet their needs • Prof Benjamin Gan (IS480 Course coordinator) • Prof Jiang Lingxiao
(Reviewer 1) • Prof Alan Megargel
(Reviewer 2) • Fiona Lee (Instructor)
Key player • Mr. Marc Sim
(Client/Sponsor) • Ms. Angeline (Key user) • Prof David Lo (Supervisor) • Team Zora
Least Important NIL
Show consideration • Fellow course mates • Family & Friends
Infl
uen
ce o
f sta
keh
old
ers
Interest of stakeholders
Stakeholder management priority metric
21/4/2014
24
Key player stakeholders Stakeholder Name Mr. Marc Sim Ms. Angeline
Project Role Sponsor & Client Key Client
Needs – Key interests and issues
• Sterling Engineering HR System (HRMS) Vision and Objective
• Fulfilment of user needs on the system and requirements
• Fulfilment of user needs on the system and requirements
Communication Approach
• Manage closely Manage closely
Engagement • Have frequent meeting (at least once a month)
• Demonstration of progress on application
• Constant update of progress • Change management
• Have frequent meeting (at least once a month)
• Demonstration of progress on application
• Change management
Key player stakeholders Stakeholder Name Prof David Lo Team Zora
Project Role Supervisor Contributing team
Needs – Key interests and issues
• Team’s fulfilment of the objective of IS480
• Evaluate IS480 criteria • Learning outcomes
• Completion of IS480 project
• Work balance (with other modules)
• Appropriate allocation of time and type of tasks
Communication Approach
• Manage closely • Manage closely
Engagement • Have fortnightly meeting and emails (Tue)
• Demonstration & update on project progress
• Update of Wiki & Documents
• Have frequent weekly meeting (Mon)
• Open communication • Conflict management • Constant communication
via email and Whatsapp group
21/4/2014
25
QUALITY OF PROJECT: Design considerations
Twitter Bootstrap
• Error prevention • Help users recognize, diagnose, and recover
from errors
• User control and freedom
Nielsen's Heuristics
Colour Scheme
Typeface
Trebuchet MS
Arial
• Aesthetic and minimalist design
Nielsen's Heuristics
QUALITY OF PROJECT: Design considerations
21/4/2014
26
System Architecture
OVERALL ARCHITECTURE
• Application – Codeigniter Framework
– PHP 5.2.17
– Apache
• Browser – Javascript
• Jquery Library
• Jquery Validation
– HTML
– CSS
• Database – MySQL 5.1.66
– phpMyAdmin
21/4/2014
27
Controller View
MySQL
Model
Service DataAccess
Object
Object
Maintainability
Maintainability • Codeigniter Style guide
21/4/2014
28
QUALITY OF PROJECT: Security considerations
• Password salting and hashing
• Cross Site Scripting Validation
QUALITY OF PROJECT: Security considerations
• Dynamic Access control
21/4/2014
29
QUALITY OF PROJECT: INTEGRATION with other libraries
• TCPDF – Open source PHP library for PDF generation
• PHPass – Password hashing for PHP applications
TECHNICAL COMPLEXITY: INTEGRATION oF VARIOUS MODULES
• Need to ensure consistency among various modules – Technical documents to ensure consistency of database
21/4/2014
30
TECHNICAL COMPLEXITY: Managing live deployment data
• Inconsistency in structure of database tables – Major changes in database structure
– Identify and migrate changes
– Need to ensure current data is compatible with new structure
TECHNICAL COMPLEXITY: KNN algorithm
• User of k-nearest neighbor algorithm (kNN) to determine if a claim is fraudulent
New Claim
Fraudulent Claim
Non- Fraudulent claim
21/4/2014
31
TECHNICAL COMPLEXITY: KNN algorithm
• Classify the distance based on the following attributes with the different weights
– Claim Amount (30%)
– Income of claimer(30%)
– Claim Type (20%)
– Department of claimer (10%)
– Day of claim incurred (10%)
• Euclidean distance for numerical attributes
(𝑎 − 𝑏)2
• Distance normalized: 𝑛
𝑛 + 1
• Lazy Classifier
Test Plan
Update Results in
Test Cases
Update Bug Log
after resolving bugs
Create Test
Cases
Perform functionality
testing
Perform
integration testing
Fix all bugs
Perform
system testing
Update Bug
Metric
Record Bugs found in
Bug Log Fix all bugs
Update Results in
Test Cases
Fix all bugs
Regression Testing
21/4/2014
32
Test Cases
Login &
Logout (7)
Claim (95)
Leave (71)
Remuneration (42)
Performance &
Appraisal (45)
Training &
Development (75)
Administration (63)
Integration (35)
User Tests
1st 2nd 3rd
20 Oct 2013 25 Jan 2014 21~22 Mar 2014
COMPLETED COMPLETED COMPLETED
21/4/2014
33
Our Goal:
User Test (UT)\
Observe user activity and system load
Provide users with an early look and feel of
the system
Improve our system based on the feedback
gathered
Ensure developed functionalities are in
line with client’s requirements
Gather feedback from future users of the system so that we are able to:
UT1 participants
Marc (32)
Business Development
Manager
Ching Png (24)
Student
Pei Wen (26)
Accountant
Jasmine (50)
Administrator
21/4/2014
34
UT1 – Qualitative Analysis Positive Negative “Interface of the application is simple” “Mouse-over for the navigation bar is too
sensitive”
“Inconsistencies in the page header and the navigation bar tabs”
Navigation bar is not very nice and not
intuitive
UT1 - Qualitative Analysis Positive Negative “Interface of the application is simple” “Mouse-over for the navigation bar is too
sensitive”
“Inconsistencies in the page header and the navigation bar tabs”
Consistent wordings in page header and
navigation bar
21/4/2014
35
UT2 participants
Marc (32)
Business Development
Manager
Angeline (45)
HR Personnel
Fredinand (50)
Quantity Surveyor
Rhoylan (50)
Structural Draftsman
Elysee (26)
Contract Manager
UT2 - Qualitative Analysis Positive Negative “Interface of the application is simple with not too much of information in a page and easy to navigate”
“Some font size are quite small to see”
“Application is user-friendly with nothing too overwhelming”
“Links are not obvious enough”
Links not obvious
Fonts too small
21/4/2014
36
UT3 participants
Marc (32)
Business Development
Manager
Angeline (45)
HR Personnel
Fredinand (50)
Quantity Surveyor
Rhoylan (50)
Structural Draftsman
Elysee (26)
Contract Manager
Lady Ching (30)
Quantity Surveyor
Mikhael (28)
Design Engineer
Rupert (20)
Student Intern
Rashid (30) Work & Safety
Health Manager
UT2 VS UT3
UT2
UT3
0
1
2
3
4
Strongly
Disagree
Disagree Neutral Agree Strongly
Agree
System was Intuitive & easy to navigate
0
1
2
3
4
5
6
7
8
Strongly
Disagree
Disagree Neutral Agree Strongly
Agree
System was Intuitive & easy to navigate
3 2
2
7
0
1
2
3
4
Strongly
Disagree
Disagree Neutral Agree Strongly
Agree
Like the overall layout of the system
0
1
2
3
4
5
6
7
8
Strongly
Disagree
Disagree Neutral Agree Strongly
Agree
Like the overall layout of the system
1
2 2
1
8
21/4/2014
37
Based On The Same 5 Participants – Quantitative Analysis
0
50
100
150
200
Validate Submitted
Claim
Edit Payment Method Apply Other Leave
Average Timing Taken to Perform One Functionality
UT2
2m 35s
0
50
100
150
200
Validate Submitted
Claim
Edit Payment Method Apply Other Leave
Average Timing Taken to Perform One Functionality
1m 14s
3m 1s
UT3
1m 19s
35s
1m 45s
Most users are not able to locate the
“view” claim receipt link
Confirmation message was not displayed
Most users was unsure how to upload
2 files as no instruction was stated
Reasons for changes in timing: 1. Changes on the
application was useful
2. Live Deployment + Used the system before
UT3 – Quantitative Analysis
50
100
150
200
Approve/Reject Training by HR
Average Timing Taken to Perform One
Functionality
2m 50s
Of the 2m 50s, approximately 1 min was
used to accept the training.
This was resulted from the confusion of the button
21/4/2014
38
UT3 - Qualitative Analysis Positive Negative “Well-designed application. Easy to handle and user-friendly”
“Color scheme easy on the eye. Functions and rationale are clear cut and not complicated”
UT3 – Response Plan S/N Functionality Feedback Proposed Solution Proposed Decision
CLAIM
1 Submit Claim Tedious to record receipt numbers of the claim receipts by HR
Have an addition field "Receipt No." for employee to key in their own receipt number and HR will just validate instead of having to input it herself'
Implementing
2 Validate Claim Did not know need to update the edited amount before continuing to validate the claim
To include a "message" whenever the edit button is click to remind the user that update button must be hit before the changes can be made
Implementing
LEAVE
1 Record Leave Not obvious that employee's name is able to be selected by keying the alphabet
Enable filtering for user's to type employee's name
Implementing
2 Emailing for all leave Leave approval emails did not CC HR personnel CC HR personnel for all leave emails Implementing
TRAINING & DEVELOPMENT
1 Approve/Reject Proposed Training
UI Changes for select the training to be approve/reject - Accept / Reject button unclear, user was not sure she needs to click the button to proceed.
Change the name of the button Implementing
2 Manage External Training
Training Status Training Status from Completed change to Course Completed
Change from completed to Course Completed
Implementing
21/4/2014
39
UT3 – Response Plan S/N Functionality Feedback Reason for not implementing Proposed Decision
LEAVE
1 Record medical leave Did not check for duplicate medical series no. There is a possibility that 2 person can have the same medical series no. Hence, this will not be checked
Not Implementing
2 Validate Claim Did not know need to update the edited amount before continuing to validate the claim
To include a "message" whenever the edit button is click to remind the user that update button must be hit before the changes can be made
Not Implementing
REMUNERATION
1 Worker payslip Timesheet to include dinner breakdown (3h x 2) instead of giving the total ending sum
Dinner is allocated $3 for each dinner, if necessary. The payslip in the system is mirroring the current payslip they are using.
Not Implementing
2 Input worker timesheet
user tend to miss out the days but will notice when see days
The timesheet in the system is mirroring the current worker timesheet they used. Others may not be familiar but the HR personnel who is in charged of inputting the timesheet will be familiar if it is the same format as the one she is using.
Not Implementing
UT3 – Changes
Space for signature too small
Claim slip too small
21/4/2014
40
UT3 – Changes
Not obvious that the employee’s name is able to be
selected by keying the alphabet
UT3 – Changes
Accept/Reject button is misleading and caused confusion
21/4/2014
41
X FACTOR: fraudulent claim detection
• Automatically identify fraudulent claims via email • Reduce losses associated with fraudulent claims • Identify dishonest employees
X FACTOR: Highly configurable controls
Remuneration: • Dates to generate payslip (employee, driver
OT) • Default OT times • Minimum Wage
21/4/2014
42
X FACTOR: Highly configurable controls
Leave • Leave Entitlement
Claim: • Generated Date
X FACTOR: Highly configurable controls
Performance Management & Appraisal: • Appraisal Score /NWC Weightage • Increment Metrics
21/4/2014
43
june
Claims Leave System
Administration
Deployment URL : http:// hrms.sterling-portal.com
X FACTOR: Early Live deployment & usage tracking
41 Claims Submitted
15 Leave Applications
Usage
X FACTOR: Early Live deployment & usage tracking - Heat map
Live deployment 1 (19 Feb 2014)
Live deployment 1 update (31 Mar 2014)
21/4/2014
44
X FACTOR: Early Live deployment & usage tracking
Display Project names in alphabetical order
Allow user to past dates more efficiently
Remuneration Performance Management
& Appraisal
Training & Development
Deployment URL : http:// hrms.sterling-portal.com
Live deployment
21/4/2014
45
Value to sponsor: improving productivity
Time taken for specific function
Improvement in productivity (%) (UT2)
Improvement in productivity (%) (UT3)
Claim (submit, process, approve/reject)
73 90
Leave (Apply, edit/cancel, inform
department)
91 92
Remuneration (gather info, generate payslip)
92 92
System Administration (create, update profile)
52 83
Handover to client
• User guide for different user roles
• Conduct HRMS Workshop @ Kranji on 17 April
21/4/2014
46
Clients’ Feedback on HRMS Elysee: HRMS has indeed taken a streamlined approach for the claim process.
Roy: I have already applied 2 leave with HRMS. It is extremely convenient!
Generoso Jr. Baring: HRMS is faster, easier, non-manual and much more synchronised compared to our current way of doing things.
Ching: HRMS is effective, has fast access and easy to understand.
Ferdinand: HRMS is very good and helpful. Our work becomes easier. Now we can check our leave balance faster.
Goot Cheng: HRMS is indeed effective for applying leave and remuneration. It is also easy to use.
Learning outcomes
• Importance of documenting business requirement proposal properly
• Business requirement serves only as a guideline
• Be a trailblazer by researching on new technologies, weigh their cost and benefits in order to decide whether to implement them.
• More versatile as I become more receptive towards unexplored technologies.
• Understand the importance in seeking common consensus from my fellow group mates in whatever decision I have made.
• Maintaining the morale and camaraderie of the team is essential for the success of the team.
YUN XI
KEN
KHOON
FIONA
21/4/2014
47
Learning outcomes
• Learn the important of having building a system with well-design backend.
• Striking a balance between ease of accessing the system information and data redundancy in database design.
• Testing is an essential procedure that should not be eliminated or avoided when developing an application
• Cannot fully understand the real needs of the user until they tried the system themselves
• Learnt that system UI design requires deep, intimate understanding of the client’s business processes and environment .
• Realize the usefulness of prototyping.
YI XIAN
MEI
ZHEN
DARRYL
Team Learning outcomes
Time Management
Change Management
Effective Communication
Stakeholder Management