Payroll Business Project - Research Proposal Example

Payroll Business Project Plan Name: Institution: Instructor: Course: Date: Table of Contents Table of Contents 2 Introduction 3 Justification for the project 3 Expected project benefits and deliverables 4 The scope of the project 5 The crucial circumstances that can hinder the project 7 The project life cycle 7 Planning Phase 8   Implementation (execution) Phase 8   Closing phase 9 The life cycle of the project 9 Time frame 9 Cost of the project 10 Project risk analysis 10 Conclusion 13 References 14 Sudhakar, G. P., 2010. Elements of Software Project Management. New Delhi, India: PHI 15 Introduction The project gives the outline of the business plan and management that will provide consulting services that are the best, test, implementation, and management of an assimilated computer personnel solution, and it offers enough preparation for the employees on the use and function of the payroll computer information system (Michael pp 20, 2011). The current payroll system of the clients is outdated; therefore there is need for upgrading the system in use. The management feels that by changing the payroll system there will be a fresh start and this will give the company the easy time when it comes to payment. This will be encouraged by the use of personnel system with subcontracted administration that will reduce the problems that the company is experiencing, do the personal bookkeeping, and achieve a long term cost of saving for the Human Resource Management. Justification for the project This project will provide immense benefits for the clients, and the business. Instead of wasting time on delivery of information, training of the employees, reduced redundancy, reduce the costs and time in preparation of the reports (Shenhar, 2008). A part from this the will be up to date software and advanced solutions, professionals, and support staff, there will be no more upgrading of the systems, and there will be the flexibility of adapting the system to suit the daily operations of the business, hence there will be a noticeable growth of the business. According to Cerpa and Verner the research from other companies that have adopted the use of this system the results show a positive feedback and none of the systems have failed (26, 2009). Expected project benefits and deliverables We will meet the customers’ often to the far the project is moving so as to show them part of the project in order to get feedback and from that we will be able to make the necessary changes to the project. The project will enable the business to have an ease time in financial records for future reference. Project assumptions There following are the assumptions about the project 1. The business clients and employees will accept the changes of the operating so as to have the advantage of the payroll system introduced. 2. The mangers will make sure that the group carrying out the project is present when required to carry out the roles and objectives of the project. 3. The committee will be take part in the timely implementation of the project plan especially during the phases of the project and attend meetings when called upon. 4. Incase the projects does not identify and make any changes within the timeframe will delay the process of the project. 5. The members of the group will follow the communication plan. 6. The middle and the higher managers will give the support and support the goals and objectives of the project. 7. The businesses will acertain the presence of technology that will enable the new payroll system to take place. 8. Every individual participating in the project will adhere to the set guidelines 9. The moment new ideas come in the plan of the project is likely to change. Resources Project management Number of persons required The person 1 The project manager 1 administrator 1 Configuration administrator 1 writer Module of resources will include People needed Number required 1 Leading subject management 10 2 Business analysts 12 3 Development mangers 3 4 developers 40 The scope of the project The project will cover client to clients depending on the type of the business, this will involve the firm to firm in the industry. So far the system that has already been implemented in some companies and they cover firm to firm (Chen, 2008). Therefore this project will connect between the nature and the premise that the company holds. The designing and implementation of this project will consist of the clients, and its termination will be based on the success of the project without interfering with the clients (Cesarone, 2007). Body of project plan (e.g. discussion of constraints, life-cycle; planning schedule, resources, budget and estimates; WBS, Gantt Chart, etc) The constraints Some of the expected constraints are: -The project may luck adequate funds, in case of any emergency -The nature of laws in place, resource that are available may not be constant. Related projects So far some of the companies have already implemented the project and it is doing well. Such related companies are banks, institutions and more. . The crucial circumstances that can hinder the project Apart from the risks, there are expected crucial barriers that are likely to destruct the project some of these barriers include: The financial resources, the funds may lack adequate money to be implemented. Secondly there maybe some unavoidable natural disasters that may hinder the progress of the project. In case of such misfortunes the project will be termed as invalid. The project life cycle In this project, it will have the cycle of four phases, these are the initial phase, planning, implementation and closing phase. In the initial phase, there will be the identification of the payroll system project as a business problem. Then the results will be recorded with the solutions to the problem as recommended. Such issues like the justification and viability of the project will be discussed. Then the project will be initiated the moment all the recorded recommendations have been approved, and the solutions then there will be the appointment of the manager of the project. Here the deliverables and the groups that will take part in the project will be named and the project will start after the manager has approved. Planning Phase In this phase, the solutions given in the initial stage will be developed comprehensive, and the steps required for the goal of the project will be developed. The group will check all the work that needs to be accomplished; the resources will be identified, and plans for getting them. The manger of this project will organize and led the preparation of the budget, here the costs will be estimated to cater for manpower, equipment and the cost of the material required. This will be used to watch and manage the expenses at the implementation of the project. After having known the group required for the project, the schedule, and the cost estimates, then planning will come to the end. Then any possible threats will be easily identified, through risk management. The stakeholders of the project will be identified. In case of any occurring problems, they will be seen here, this way there will be a communication network about anything required and the delivery way so that all the people involved will be informed (Kent, 2009).   Implementation (execution) Phase During this phase, the project will be put in place, and the project will take place. The communication network and management will be in control. The process will be watched and any necessary changes will be made as well as put in record as discrepancy from the plan. The manager will be in control of everything. The payroll system will be in place and progressing as the feedbacks will be sending and recorded during the internal meetings. The manager of the project will make use of the relevant information in order to help in maintenance, and management of the project, by giving important directions to the project using the information, comments and recommendations made.   Closing phase In this phase the final deliverables will be given to the clients, the project will be handed over to the to the company, then contract of the suppliers will be put to an end, the resources of the project and communication will be send to the stakeholders. The life cycle of the project Time frame The project design, testing, implementation and management will take a period of 12 months. Each section will be allocated an equal time period of 3 months each. Cost of the project Phase 1: initial discussion Time Hrs Monthly cost in $ Carry out meetings with human resource manger 3 2000 Complete existing gaps, payroll requirements, and applications 3 6000 Requirements, and recommendation 4 10000 Phase II: solution proposal Build software to suit client request 48 20000 Carry out better testing, and hand over to the client 8 8000 Phase III: Execution Install application to client systems 48 20000 Form the client’s data centre 6 4000 HR staff training 1 wk 5000 Project official handoff 4 4000 Phase IV: administration and maintenance Hosting of data at the data centre 7 30000 Client operational and mechanical support 3 600 Monthly payroll management 1month 40000 total 419600 Project risk analysis Risk Risk Level Low/Medium/High chances of occurrence Mitigation Strategy Project Size     Person Hours H: Over 25,000 definite High working hours to meet the set goal of the project Estimated Project timetables H: above 1year months definite Review to confirm if the project is within the timeframe Team Size at Peak H: Over 10 workers definite full communications plan, numerous meetings, tight project running oversight Number of Interfaces to Existing Systems Affected H: Over three definite extend interface management document immediately Project Definition     Availability of project members M: the way members are spread all over makes it unpredictable probable Continuos asseament of project momentum, and if possible require commitment from all members Location of project members that restrict effective management M: spread of team members in all sites probable Communicate through intranet Poor working condition due to shared work experience L: Some members have little experience probable All inclisive in the communication plan Poor client participation L: client staff are part time workers Doubtful All members will be full time members Software vender Lack of knowledge Theoretical understanding probable Better understing of the project will be enhanced by aii inclusive processes Timeline are not realistic M: Timeline presume no derailment likely Timeline to be revised every monthly by four groups so as to avoid unplanned timeline. Insufficient practical matching with the system Low matching to the system required doubtful The likelyhood of the matching requirements of requierements and the selection of vender is based on its suitability Workers participate in bundle selection, design and implementation Extraordinary participation in selection  doubtful  All inclusive application examination, and choice included in the plan Conclusion The benefit that will be derived from the successful implementation of the project will result in major changes, in the structure of the human resource management (Gupta, 1970). The Client Payroll system will be streamlined it and brought to the confinements of global standards. This project will result in the lowering the cost and, therefore, support the clients company strategic objectives. References Cerpa, N. & Verner, 2009. Why did your project fail?. Verner Communications of the ACM, 52(12), pp. 130-134. Chen M.T. (2008). The ABCs of earned value application. AACE International Transactions. Cesarone, J., 2007. Project management by the numbers. Industrial Engineer, 39(11), p. 36. Douglas, E. E., 2008. Project planning-then scheduling, Newtown Square, PA: Management Institute. Forbes, D. E., 2000. Project Management Information Systems. Washington D.C.: Transportation Research Board. Gupta, A., 1970. Enterprise resource planning: the emerging organizational value systems. Virginia, USA: MCB UP Ltd. Jack Gido, J. P. C., 2012. Successful Project Management. London: Cengage Learning. Meshoulam, L. B. a. I., 1988. Managing Two Fits of Strategic Human Resource Management. Academic Management Review, pp. 116-128. Michael J. Kavanagh, R. D. J. M. T., 2011. Human Resource Information Systems: Basics, Applications, and Future Directions. New York: SAGE . Sudhakar, G. P., 2010. Elements of Software Project Management. New Delhi, India: PHI Shenhar, A. J. (2008). Unleashing the Power of Project Management . Industrial Management. 50, 14. Kent, S. (2009). Tough sell. PM Network. Newtown Square, Pa, Project Management Institute. Morris, R. A. (2008). Stop the Insanity of Failing Projects .Industrial Management. 50, 20. Khan, A. (2006). Project Control Management .Cost Engineering : a Publication of the American Association of Cost Engineers. 48, 12. Read More