Maya's Final Project Presentation
- 1. WEB APPLICATION FOR HUMAN RESOURCE INFORMATION SYSTEM USING LEAN SOFTWARE DEVELOPMENT METHOD MAYA NASTASYA 212116122
- 2. KEY POINTS Background Objectives Human Resource Management Lean Software Development Implementation Conclusions 2 36
- 3. 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
- 4. OBJECTIVES ? Computerizing HRM system ? Aiding HR managers ? Simplify reports making 4 36
- 5. HRDesigned to maximize employee¡¯s performance The knowledge, skills, creative abilities, talents, and attitudes of the employees 5 36 MANAGEMENT
- 6. The process an organization undergoes to manage people to achieve its goals. WHAT IS HRM Function 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
- 7. 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
- 8. HRM core areas ? Job design and analysis ? Workforce planning ? Recruitment ? Work force selection ? Training & development ? Performance management ? Compensation ? Legal issues 8 36
- 9. 9 36
- 10. SOFTWARE LEAN Designed for fast delivery & minimal waste 10 36 DEVELOPMENT
- 11. ? 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
- 12. Excess products & materials not being processed Wasted time waiting for the next step in a process Unnecessary movements by people Repetition or correction of a process Unnecessary movements 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
- 13. ? One of Agile Software Development Practices ? Has 7 principles called Lean Thinking What is Lean SD 13 36
- 14. ? Eliminate Waste Spend time only on what adds real customer value ? Amplify Learning When you have tough problems, increase feedback ? Decide as Late as Possible Keep 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
- 15. ? 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
- 16. ? 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
- 17. ? 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
- 18. ? Fast delivery ¡ú only small amount of resources tied-up in work-in- progress ? Let the customer needs pull the work ? Pull scheduling with kanban system Put to do list, work in progress, and completed work in one board Deliver as Fast as Possible 18 36
- 19. ? 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
- 20. ? Perceived integrity Gained through the customer¡¯s experience, how the system is advertised, delivered, installed, accessed ? Conceptual integrity Gained 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
- 21. ? 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
- 22. Project Life Cycle 22 36
- 23. SYSTEM IMPLEMENTATION Iterations used and features made 23 36
- 24. ? 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
- 25. ? Offers flexibility to every type of company ? Available for all modules ? Can be accessed by the Super User Setting 25 36
- 26. Organization Employee Career Reimbursement Loan Performance Training Recruitment Each module has reports and a dashboard to summarize data Modules 26 36
- 31. 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
- 32. ? 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
- 33. 1st Iteration User Feedback 58.8% Passive User 41.2% Admin User 52.9% said the features are detailed 47.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 friendly 5.9% felt MayHR isn¡¯t user friendly 64.7% felt MayHR is quite user friendly 17 people filled the questionnaire 33 36
- 34. 2nd Iteration User Feedback 40% Passive User 60% Admin User 60% participated in first user feedback 40% didn¡¯t participate in first user feedback 5 said the modules are easy to use 7 said the modules are quite easy to use 3 said the modules are hard to use 3 people didn¡¯t find any significant changes since first feedback 4 people felt the changes are useful 15 people filled the questionnaire 34 36
- 35. 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
- 36. THANKS!
Editor's Notes
- #5: Aiding human resource managers to manage employees¡¯ data, career, reimbursement, loan, training, and performance planning.
- #6: The power of an organization lies within the human resources, that is the qualitative and quantitative aspects of employees working in an organization. It¡¯s very important to put human resources at the top of the agenda to achieve the organization¡¯s goals
- #7: Since every organization is made up of people, acquiring their services, developing their skills, motivating them to higher levels of performance and ensuring that they continue to maintain their commitment to the organization are essential to achieve organizational objectives.
- #11: Derived from Lean Manufacturing, which is a management philosophy from the Toyota Production System.
- #12: At the time when TPS was founded, Taiichi Ohno, the TPS founder, realized that production scheduling can¡¯t be done by sales or production target. In pull production system which used by lean manufacturing, production will be done by order, not by target. Lean is focused on eliminating waste & deliver fast. However, these 2 methods should be adapted to the value needs to be produced by the organization or company.
- #13: Lean is all about eliminating waste. Waste is anything that doesn¡¯t add value to customer.
- #14: Agile software development is a term for software development methods which apply the principles in Agile Manifesto, that is adaptive planning, evolutionary development, early delivery, and continuous improvement. Agile encourages rapid and flexible response to change. Lean SD has 7 principles called Lean Thinking.
- #16: Spend time only on what adds real customer value
- #17: When you have tough problems, increase feedback. In most cases, increasing feedback is the most effective way to deal with troubled software development projects and environments. Small iterations of try it, fix it, test it cycle will discover design problems and develop tolerance to changes while producing final and usable product.
- #18: Keep your options open as long as practical, but no longer. Repetition: every function should be placed in one place in the code. Separate concerns: every module should only have one responsibility. Encapsulate: encapsulate things that is likely to change. Defer implementation: don¡¯t add capabilities of what you know will be needed in the future. Extra features: only add whatever the customer need right now.
- #19: Deliver value to customers as soon as they ask for it. Customers like rapid deliveries, that¡¯s why the immediate shipping became the standard for online shopping. Only work on what the customer asked to deliver fast. Use pull scheduling for developers with the kanban board. Put to do list, work in progress list, & completed work list in a kanban board & let the developers choose their work.
- #20: Let the people who add value use their full potential.
- #21: A system is called to have an integrity if the user thinks this is what they really need. A software is called to have an integrity if it still works even after a long time passed.
- #22: Beware of the temptation to optimize parts at the expense of the whole.
- #23: There¡¯s no exact life cycle in Lean SD, you have to adapt Lean principles to your own project. For my case, this is the project life cycle. The first 3 phases are iterated until the customer no longer has any request or requirement change. After all of customer¡¯s needs are already made, then the project will be deployed. In the Analyze & Design phase, the system designer will gather customer¡¯s requirements and make the system¡¯s structure. After each implementation or coding, the system will be tested and if there is any bugs or problems, designer will re-design the structure and programmer will implement the new structure.
- #25: Super admin is the MayHR website admin who will register clients & their respective super user. Each client can have many companies but only one super user who holds all access to the client¡¯s data in MayHR and set the options in Setting feature.
- #26: Super User can set options in every modules, from organization structure, job positions, survey questions, to key performance indexes.
- #27: Organization module is used to handle announcements & company policies. Employee : employee¡¯s data, surveys, onboarding, & work accidents. Career : career transitions, awards, & disciplines. Reimbursement : employee¡¯s reimbursement requests. Loan : employee¡¯s loan requests & payments. Performance : employee¡¯s appraisal & performance planning. Training : employee¡¯s training courses. Recruitment : job applicants recruitment processes. MayHR doesn¡¯t handle payroll & attendance
- #28: This is the employee¡¯s information page.
- #29: This is the organization structure page. The left sidebar is the list of every module and its features inside. The sidebar on the right is the menu for setting feature. The right sidebar will not be accessible if the logged on user is not super user.
- #30: This is the employee dashboard page which summarize employee headcount by gender and by job grade.
- #31: And this is one of reimbursement module¡¯s reports.
- #34: 10 passive, 7 admin. 9 Detailed, the others not detailed enough. 15 Satisfied UI, 2 not. 5 User Friendly, 11 quite easy to use, 1 not friendly enough. No bug and error. One user asked for forgot password feature and it was made right after that. Some user asked for improvements in the UI and some changes were made in UI.
- #35: 6 passive, 9 admin. 9 participated in first feedback, 6 didn¡¯t participate. 2 people didn¡¯t fill the question about changes usefulness.
- #36: Lean SD speed up the development time with concurrent development where big decisions taken first so that crucial problems will be detected earlier