Tuesday, May 5, 2020

Project Management Case Study on RALS

Question: Describe about the Project Management for Case Study on RALS. Answer: Part 1: Team Name/ Team/ Description Name of Project: Riverina Agriculture and Lifestyle Show Rostering System Project Start Date October 14, 2016 Team Member Contact Details Rusiru Dharmawansa (02) 2622 66985; rusiru.dharmawansa@gmail.com; Shital Mainali (02) 2366 7445; shital.mainali @ gmail.com; Akruti Jagdishchandra Patel (02) 2398 1299; akruti.jagdishchandra.patel@gmail.com; Overview of the Project: The aim of the undertaken project is to develop a system for the Globex Corporation, that allows computerizes, automated, easy monitoring and management of the volunteers working on the Riverina Agriculture and Lifestyle Show. Project Description: Globex Co-corporation is responsible for the organization and management of the Riverina Agriculture and Lifestyle Show for appreciating and demonstrating the lifestyle of the farmers and their achievements. This show is being organized every year in November by Globex. The proper coordination and effective management of the show is completely depended on the various volunteers who works during the show. In the recent years, the number of volunteers have increased making it difficult for the Globex to manage them manually. Therefore, Globex has consulted Virtucon for developing a project management plan for the development of the computerized rostering system that will make the rostering and managing volunteer during the RALS show more easy and effective. In addition to that, the rostering system would be able to store information about the volunteers and allocate task depending on their criteria of experience. Team Charter Skills and Knowledge Inventory Name of Member Role in the project Skills and knowledge Rusiru Dharmawansa Project Manager Organization, Team Management, Leadership, Risk Management, Negotiation, Communication Shital Mainali Software Developer Business Knowledge, Technical Knowledge, Problem Solving, interpersonal Skills, risk assessment, risk identification, Optimized Coding, Error rectification Akruti Jagdishchandra Patel Software Tester Business Savvy, Analytical Skills, Thinking Skills, logical understanding, interpersonal Skills, risk assessment, risk identification, Error rectification skills Akruti Jagdishchandra Patel Business Analyst Decision Making Skills, Technical Knowledge, Conceptual modeling, Analytical Skills, Persuasion, Marketing, Change Management; Shital Mainali Software designer Graphical Knowledge, Creativity, valuing customer requirements; Roles and Responsibility Team Member Name Roles Responsibility Project Manager Rusiru Dharmawansa The project manager for the development of the rostering system project is responsible for effectively managing the team members and ensuring the proper standard being followed in the development. For proper monitoring and allocation of the technical and financial resources in the development of the rostering system; For ensuring the team member is following the proper scheduling for completing the project on time; Software Developer Shital Mainali Review and provide a feasibility study for developing the rostering system for the RALS festival; To prepare the various functional module for implementing the operational requirement of the system; To code the operational functionality of the application; To develop and review a prototype of the rostering system application for RALS; Software Tester Akruti Jagdishchandra Patel Responsible for developing the test cases for verification of the application; Conducting the system test and software test for ensuring the effective operational functionality of the system; Create and verify the criteria for acceptance of the developed rostering system application for RALS; Business Analyst Akruti Jagdishchandra Patel For understanding and evaluating the need of the RALS and Globex; Providing the visualization of the schedule, budget, profitability of the rostering system application; Ensuring the business requirements and considered and effectively implemented in the rostering system project; Software designer Shital Mainali To understand and evaluate the user requirements for developing the appropriate UI; To develop the interface for ease of access of the rostering system application; Team Communication Team Member Location Meeting Times Ways of communication Information Stored/Documented Rusiru Dharmawansa University or other pace on mutual understanding 10:00 am to 7:00 pm Verbal and written communication, email, face-to-face meeting, phone Written on paper or demented on softcopy; Shital Mainali University or other pace on mutual understanding 10:00 am to 7:00 pm Verbal and written communication, email, face-to-face meeting, phone Written on paper or demented on softcopy; Akruti Jagdishchandra Patel University or other pace on mutual understanding 10:00 am to 7:00 pm Verbal and written communication, email, face-to-face meeting, phone Written on paper or demented on softcopy; Team Rules and Expectation Team rules and expectation in project is one of the most essential factor that determines the strength and co-ordination of the team as a whole. Positive Experience of working in a team: Working in a project as a team with different members allows in gathering and applying different experience and specialty in a project. in addition to that, team work allows in breaking the whole task in smaller activities and dividing the pressures and work load for effective completion of the entire project within provided time. Negative Experience of working in a team: One of the most negative impact of working in team is the personal conflict between the team members that hinders the progress and completion of the undertaken project. In addition to that, the conflict of beliefs, and ideas in the project also creates inefficient project. Goal of the team: The vital goal identified in the project is to respect team members ideas, beliefs and work with mutual understanding for the completion of the rostering system before the next RALS show; Value of the Team: All the team members needs to value individual thoughts, idea, honesty, hard work, mutual understanding and commitment for completing the undertaken project. Statement of Team Value: Understanding, commitment, honesty, punctuality, hard work, and sharing experience is the key for delivering the requirement of the project in provided budget and time. Code of ethics: All the team members will be following a particular code of ethics for providing required standard and process to the developed rostering system; Rules and Exception: Each team member is expected to completed his part of the task as assigned in the project. In addition to that, the team members should follow the project schedule for completing the project on time. Signatures Name Date Signature Rusiru Dharmawansa October 14, 2016 Rusiru Dharmawansa Shital Mainali October 14, 2016 Shital Mainali Akruti Jagdishchandra Patel October 14, 2016 Akruti Jagdishchandra Patel Part 2: Learning Cycles Time Phase of the Project Scribe Organizer Mode of communication While verifying the project and business requirements of RALS Evaluation Phase Shital Mainali Rusiru Dharmawansa, Akruti Jagdishchandra Patel Verbal and written communication, email, face-to-face meeting, phone While evaluating and accessing the risks involved with the project Extension Phase Rusiru Dharmawansa, Akruti Jagdishchandra Patel Shital Mainali Verbal and written communication, email, face-to-face meeting, phone While developing the rostering system project Explanation Phase Shital Mainali, Akruti Jagdishchandra Patel Rusiru Dharmawansa Verbal and written communication, email, face-to-face meeting, phone While planning for the development of the rostering system Exploration Phase Akruti Jagdishchandra Patel, Rusiru Dharmawansa Shital Mainali, Verbal and written communication, email, face-to-face meeting, phone While planning for the development of the rostering system Engagement Phase Rusiru Dharmawansa Akruti Jagdishchandra Patel Verbal and written communication, email, face-to-face meeting, phone Part 3: Stakeholders Identification The identification of the significant stakeholders in the project is essential for the developing of the efficient communication plan while developing the rostering system project. Stakeholders Role Description Project Manager The project manager in the project is responsible for timely completion of the project within the schedule and budget plan as developed in the project management phase; Software Developer The software developer in the project has the responsibility of developing the programming module and code of the application; Software Tester The software tester runs the testing cases on the developed application for ensuring the operational and functional efficiency of the rostering system; Globex Representative The Globex representative provides us the business needs and requirements of the rostering system for the RALS festival. In addition to that, the Globex Representative verifies and provides feedback on the developed rostering system application; Virtucon representative The Virtucon representative is authorized to undertake the project and provide an effective management plan for competing the project within budget and allocated time; Business Analyst The business analyses has the significant responsibility of ensuring that the business requirement of Globex is integrated in the developed application of the RALS; Software designer The software designer in the project developed an easy and effective user interface required for the rostering management at RALS; Communication Plan Who What Why When How Project Manager Any issues, modification, changes and problems faced during the development of the project that hinders the budget, schedule and quality of the rostering system; The project manager verifies and validate the changes required for the issues raised and identified in the project. In addition to that, the project manager changes the budgeting and plans new scheduling of the project with the remaining time and activities; Whenever Required Verbal and written communication, email, face-to-face meeting, phone Software Developer Any problems and issues faced while implementing the operational logic of the rostering system application. Apart from that, for integrating any new features and requirement to the rostering system; To verify and review whether the changes can be implemented in the developed application at a particular phase. Moreover, the software developer determines and integrate the changes in the rostering system application; Once a week Email, written communication Software Tester Any issue arise during the testing phase or functionality phase of the rostering system; To determine and evaluate the cause of error for ensuing the functional operation of the rostering system; Whenever required Email, written communication, verbal communication and face-to-face interviews Globex Representative Verifying and reviewing the developed rostering system for the RALS festival. In addition to that, the Globex representative provides details of the modification and changes required for the rostering system; Discussing the changes and requirements needed in the developed rostering system for achieving the business needs; Twice in every month Face-to-face meetings, written mode of communication, emails; Virtucon representative The Virtucon representatives develops the project management plan for the developing the rostering system application required by Globex for RALS festival; Modification, changes in the scheduling, budgeting, and management plan for the rostering system project; Whenever required Face-to-face meetings, written mode of communication, emails; verbal communication, phone calls Business Analyst Changes in business requirements, modification required in the project for dissatisfied clients of Globex; To pursue the project manager with the integration of the new changes and modification required in the project. In addition to that for ensuring the developed project needs the business and customer requirements as stated; Twice in every month Face-to-face meeting, written communication, emails; formal meetings Software designer For implementing the changes required in order to make the system more user friendly Issues or problem identified in the design and user-interface of the system for providing effective operational functionality Whenever required Face-to-face meeting, written communication, emails; formal meetings, phone, verbal communication; Part 4: Project Closure Project Name: RALS Rostering System Development Project Project Manager: Rusiru Dharmawansa Start Date: [Please Fill] End Date: [Please Fill] Acceptance Criteria Person Responsible Check if Achieved 1. The identified goals are met during the development of the rostering system; Project Manager; 2. All the functional and business requirements are included in the developed project; Project Manager, Business Analyst; 3. The developed rostering system is able to meet the requirements of Globex and RALS; Project Manager, Business Analyst; 4. The technical and software requirements of the systems are licensed and properly obtained; Project Manager; 5. Proper schedule was maintained during the completion of the project; Project Manager; 6. Proper budget plan was followed for completing the project; Project Manager; 7. Risks were identified, analyzed and assessed; Project Manager; 8. Inspection of the proper standard and methods being followed in the project; Project Manager, Business Analyst; 9. The developed software were verified and accepted by the Globex Co-corporation; Project Manager, Business Analyst; 10. Implementing the data backup methods; Project Manager; 11. Developing the complete documentation of the developed rostering system application; Project Manager; 13. Sign off the team members; Project Manager; Project Evaluation Project objectives: The significant objective of the undertaken project is to develop the rostering system for RLS within low budget and before the next RALS festival; Team Staffing: Team members selected for developing the rostering system were experienced in their particular area of work; Deliverables of the Project: The initial deliverables set for the development of the project were successfully and efficiently achieved during the development of the rostering system for RALS; Project Transition to Operations: During the deployment phase of the rostering system, standard and specified test cases and risks assessment plan were employed for ensuring the proper operational effectiveness of the developed project; Cost: The project was developed and managed within the total financial cost provided by Globex; Schedule: The completion of the entire rostering system application was developed and produced before the next RALS festival; Recommendations: During the development of the project, the representative of the Globes Co-corporation should have been included in iterative phased for providing recommendation and feedback to the developed application; Projects MOV Evaluation Process Financial value For evaluating the financial value of the developed project, the Globex should cash flow of the project and NPV (Net present value) for determining the profitability of the organization; Operational value The operational value of the developed rostering system application is evaluated by the determination of the functional capabilities of the developed system. In addition to that, the time required by the project to recover from a system failure is used for determining the operational value; Customer value The satisfaction and feedback of the Globex on receiving and reviewing the rostering system determines the effectiveness of the customer value in the project; Strategic Value The ability of the rostering system in efficiently allocating the task to the volunteers and managing them for achieving profitability of Globex is determined as strategic value; Part 5: Reflection I have been given the opportunity as working as the project manager for the development of the computerized and automated Rostering System Application for the Riverina Agriculture and Lifestyle Show. As the project manager in this project, I have undertaken the foremost responsibility or evaluating the business case of the Globex for understanding customer needs and business needs for the rostering system. I have furthermore, identified the intended user of the application for identifying the operational need of the rostering system. I have formed a particular team for conducting the project in efficient manner. As the project manager, I have developed the project budget plan and scheduling for completing the rostering system within provided deadline. Moreover, as the project manager, I have the responsibly of accessing whether the project is feasible in terms of technology and business requirements or not. therefore, I have efficiently documented the business needs, user requirement s and technical needs of the system. I have further conducted meeting with my team member for analyzing the feasibility test of the undertaken project. in addition to that, as a project manager and team leader, I have communicated with the team members and allocated the task according to their individual area of work. I have further developed a communication plan between the team members with mutual understanding and verification of the location and mode of communication for continuing the flow of communication between the team members. The communication plan has assisted in full collaboration of the undertaken project and timely completion. While developing the rostering system application, due to various issues and problems, the project was running behind time that formed a potential risk to the delivery of the system. In this situation, I have communicated with all the team members in a formal meeting and identified the issues going on with the development of the project. In addi tion to that, I have documented the progress of the report and rescheduled all the remaining activities in the project. Moreover, for completing the project within the new schedule, I have motivated and pursued the team members for their collaboration for completing the project within clients deadline. I have gained valuable experience in working as project manager in this ICT project. Through this project, I have learned that the project manager in the ICT project need to have in-depth understanding of the technical needs for evaluating the business need and requirement of the system. in addition to that, the project manager should be experience in team management, communication and estimating the risk underlying in the project. Furthermore, the most vital responsibility of the project manager is to plan and develop an effective management plan for completing the project within allocated time and budget. Therefore, my experience as the project manager in this particular project wil l assist me in the future with the experience of managing and working as a team. Bibliography Ahsan, K., Ho, M., Khan, S. (2013). Recruiting project managers: A comparative analysis of competencies and recruitment signals from job advertisements.Project Management Journal,44(5), 36-54. Alberghini, E., Cricelli, L., Grimaldi, M. (2014). A methodology to manage and monitor social media inside a company: a case study.Journal of Knowledge Management,18(2), 255-277. Bhm, C. (2013). Cultural flexibility in ICT projects: A new perspective on managing diversity in project teams.Global Journal of Flexible Systems Management,14(2), 115-122. Chipulu, M., Neoh, J. G., Ojiako, U. U., Williams, T. (2013). A multidimensional analysis of project manager competences.IEEE Transactions on Engineering Management,60(3), 506-517. Davies, R., Harty, C. (2013). Implementing Site BIM: a case study of ICT innovation on a large hospital project.Automation in Construction,30, 15-24. Fantozzi, M., Popescu, I., Farnham, T., Archetti, F., Mogre, P., Tsouchnika, E., ... Bimpas, M. (2014). ICT for efficient water resources management: the ICeWater energy management and control approach.Procedia Engineering,70, 633-640. Holzmann, V. (2013). A meta-analysis of brokering knowledge in project management.International Journal of Project Management,31(1), 2-13. Jugdev, K., Mathur, G. (2013). Bridging situated learning theory to the resource-based view of project management.International Journal of Managing Projects in Business,6(4), 633-653. Marcelino-Sdaba, S., Prez-Ezcurdia, A., Lazcano, A. M. E., Villanueva, P. (2014). Project risk management methodology for small firms.International Journal of Project Management,32(2), 327-340. Martinsuo, M. (2013). Project portfolio management in practice and in context.International Journal of Project Management,31(6), 794-803. Pemsel, S., Wiewiora, A. (2013). Project management office a knowledge broker in project-based organisations.International Journal of Project Management,31(1), 31-42. Pemsel, S., Wiewiora, A. (2013). Project management office a knowledge broker in project-based organisations.International Journal of Project Management,31(1), 31-42. Rezgui, Y., Beach, T., Rana, O. (2013). A governance approach for BIM management across lifecycle and supply chains using mixed-modes of information delivery.Journal of Civil Engineering and Management,19(2), 239-258. Rosemann, M., vom Brocke, J. (2015). The six core elements of business process management. InHandbook on Business Process Management 1(pp. 105-122). Springer Berlin Heidelberg. Silvius, A. J., Schipper, R. P. (2014). Sustainability in project management: A literature review and impact analysis.Social Business,4(1), 63-96. Too, E. G., Weaver, P. (2014). The management of project management: A conceptual framework for project governance.International Journal of Project Management,32(8), 1382-1394. Turner, R. (2016).Gower handbook of project management. Routledge. Verburg, R. M., Bosch-Sijtsema, P., Vartiainen, M. (2013). Getting it done: Critical success factors for project managers in virtual work settings.International Journal of Project Management,31(1), 68-79. Yang, L. R., Chen, J. H., Wang, H. W. (2012). Assessing impacts of information technology on project success through knowledge management practice.Automation in Construction,22, 182-191.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.