Upload
maya-nastasya
View
58
Download
0
Embed Size (px)
Citation preview
WEB APPLICATION FORHUMAN RESOURCE INFORMATION SYSTEM USING LEAN SOFTWARE DEVELOPMENT METHOD
MAYA NASTASYA212116122
KEY POINTSBackgroundObjectivesHuman Resource ManagementLean Software DevelopmentImplementationConclusions
2 36
BACKGROUND HRM is one of the key management in a company
Information system aims to support management and decision making
Information system will reduce human error in the process
3 36
OBJECTIVES Computerizing HRM system
Aiding HR managers
Simplify reports making
4 36
HRDesigned to
maximize employee’s
performance
The knowledge, skills, creative abilities, talents, and attitudes of the employees
5 36
MANAGEMENT
The process an organization undergoes to manage people to achieve its goals.
WHAT IS HRMFunction within an organization that focuses on recruitment, management, training, development, appraisal, and rewarding employees.
Procuring, developing, and maintaining competent human resources in the organization.
To make effective and efficient use of employees.
6 36
HRM includes… Conducting job analyses Planning personel needs Recruiting the right
people for the job Orienting and training Managing wages and
salaries
Providing benefits and incentives
Evaluating performance Resolving disputes Communicating with all
employees at all levels
7 36
HRM core areas Job design and analysis Workforce planning Recruitment Work force selection
Training & development Performance management Compensation Legal issues
8 36
9 36
SOFTWARELEANDesigned for fast
delivery & minimal waste
10 36
DEVELOPMENT
Pull production is a solution for Toyota at the time TPS was founded
Lean → eliminating waste, deliver fast
Different with mass production, doesn’t promote batch-and-queue
Promotes single-piece flow
Lean Manufacturing
11 36
Excess products& materials notbeing processed
Wasted time waitingfor the next step in
a process
Unnecessary movementsby people
Repetition or correction of
a process
Unnecessarymovements of
products & materials
More work or higher quality than
is required by the customer
Production that is more than needed
or before it’s needed
The Seven Wastes
12 36
One of Agile Software Development Practices
Has 7 principles called Lean Thinking
What is Lean SD
13 36
Eliminate WasteSpend time only on what adds real customer value
Amplify LearningWhen you have tough problems, increase feedback
Decide as Late as PossibleKeep your options open as long as practical, but no
longer Deliver as Fast as Possible
Deliver value to customers as soon as they ask for it Empower the team
Let the people who add value use their full potential Build integrity in
Don’t try to tack on integrity after the fact, built it in See the whole
Beware of the temptation to optimize parts at the expense of the whole
Lean Thinking
14 36
Inventory → half done work
Waiting → waiting for work assignment, customer approval, testing
Motion → information transfer between developer and customer
Defects → bugs undiscovered for a long time
Transportation → task switching
Overprocessing → unnecessary documents for every changes
Overproduction → extra features
Eliminate Waste
15 36
Customer feedback to understand what the customer needs
Small iterations of try-it, test-it, fix-it cycles produces final and usable product
Iterations with refactoring—improving the design as the system develops—is one of the most effective ways to generate knowledge, find answers early, and generate a system with integrity
Amplify Learning
16 36
A decision should be made based on facts, not speculations
Make high-level decision first, then low-level decision for the detailed problems
Concurrent Development ( make high-level and low-level decision simultaneously ) will decrease development time and costs while increasing product performance
Some ways to delay decision making : avoid repetition, separate concerns, encapsulate variation, defer implementation of future capabilities, avoid extra features
Decide as Late as Possible
17 36
Fast delivery → only small amount of resources tied-up in work-in-progress
Let the customer needs pull the work
Pull scheduling with kanban systemPut to do list, work in progress, and completed
work in one board
Deliver as Fast as Possible
18 36
Let the team members contribute in every decision made
Use pull scheduling system to make everyone in the team choose their work
The team manager’s role is to supervise, coordinate, and motivate the team
Empower the Team
19 36
Perceived integrityGained through the customer’s experience, how
the system is advertised, delivered, installed, accessed
Conceptual integrityGained through the system development, how
good is the system architecture
A customer will think that a system has perceived integrity if the system is relevant and useful for the customer’s needs
A system has conceptual integrity if all of its components works together as a whole, flexible, efficient, and responsive
Build Integrity In
20 36
A system capability depends on how its components works together, not only how every component works as an individuals
If everyone in the team only optimize their own, local, small works, there might be a chance for undiscovered problems in the system as a whole
Avoid local optimation, but pay attention to the details
See the Whole
21 36
Project Life Cycle
22 36
SYSTEMIMPLEMENTATION
Iterations used and features made
23 36
4 types of user : Super Admin, Super User, Admin, Passive
Super Admin → MayHR website admin, register clients and their respective Super User
Super User → Holds all access of the client’s data in MayHR, set the options in Setting feature
Admin & Passive → Determined in the employee’s user account registration, one user account may have admin access on one module and a passive access on the other
User & Membership
24 36
Offers flexibility to every type of company
Available for all modules
Can be accessed by the Super User
Setting
25 36
OrganizationEmployeeCareerReimbursementLoanPerformanceTrainingRecruitment
Each module has reports and a dashboard to summarize data
Modules
26 36
USER INTERFACE
27 36
USER INTERFACE
28 36
USER INTERFACE
29 36
USER INTERFACE
30 36
2 iterations :
1st iteration : membership system, organization, employee, and career modules with their setting
2nd iteration : reimbursement, loan, performance, training, and recruitment modules with their setting
Lean Implementation
31 36
Produce final usable product after each iteration
High tolerance for change
Faster development time
Less bugs and system problems
Lean can’t be used if the customer want a complete prototype of the system
Why Lean SD?
32 36
1st IterationUser Feedback
58.8% Passive User
41.2% Admin User
52.9% said the features are detailed47.1% said the features are not detailed enough
88.2% satisfied with the UI
11.8% not satisfied with the UI
29.4% felt MayHR is user friendly5.9% felt MayHR isn’t user friendly64.7% felt MayHR is quite user friendly
17 people filled the questionnaire33 36
2nd IterationUser Feedback
40% Passive User
60% Admin User
60% participated in first user feedback40% didn’t participate in first user feedback
5 said the modules are easy to use7 said the modules are quite easy to use3 said the modulesare hard to use
3 people didn’tfind any significant changes since first feedback4 people felt the changes are useful
15 people filled the questionnaire34 36
CONCLUSIONS Lean SD method minimalize wastes and problems while
producing high integrity software
Lean SD speed up the development time with concurrent development
The use of information system in HRM helps HR managers in data managing and reports making, reducing human errors, and speed up management process especially in performance appraisal process
HRM information system in this final project can be developed further, particularly in the performance module
35 36
THANKS!