This project will not choose the virtualization software Any Technologies work

This project will not choose the virtualization

This preview shows page 8 - 12 out of 20 pages.

This project will not choose the virtualization software Any Technologies, work or services other than those previously described. Problems and Opportunities We dealt with great success and minor setbacks when it came to our project, its scope and follow through. It was clear to us by then that minor scope creeps were inevitable. Despite everything, we stayed within the guidelines of our main scope. The risk assessment we carried out in consultation with our lecturers and they helped us immensely along the way. The openness to new ideas, sharing them, and ability to listen to our lecturers helped us to overcome our inexperience, our communications within as a team. During the implementation of Xenserver deployment phase we have come across technical difficulties like Hardware problem that the “HVM required for this operation” (Figure 01). Final Project Report XenServer Technology Page 7
Image of page 8
Figure 01 To overcome this challenge initially we replace Oracle VM VirtualBox with VMware Workstation (Figure 02). And then we were compelled consulted our lectures for further guidance since desire result yet to be reached (refer appendix 1. Problem solution) Final Project Report XenServer Technology Page 8
Image of page 9
Figure 02 Final Project Report XenServer Technology Page 9
Image of page 10
Project Results and Work Completed During planning stage of BIT372, to achieve our set targets we used sprint to make our product easy. We divided sprint into products, then into a tasks followed by status, was given to each team member (refer appendixes 2. Sprints one to four). We were able to organize our major products to be delivered in certain time period via Sprint. We shared the work load among colleagues and agreed to deliver the product with the help of Sprint. Tasks were given sprint numbers among the members. Sprint one was from week two to week four, sprint two was from week four to week six, sprint three was from week six to week eight lastly the sprint four was from week nine to week eleven. The Gantt chart refers to major features and aspects of this project that was completed (Figure 03). Site preparation Hardware installing Installing Software Customization Deployment of Xen desktop Unit Testing Planning System Testing Checklist UAT for Xen Server Unit Testing Checklist UAT for application Classification and Extraction Database Synchronization 3/4/2019 3/24/2019 4/13/2019 5/3/2019 5/23/2019 Products Figure 03 Lessons learned and Recommendations In this semester the project plan was broken to sprints one to four according as a week one to week eleven (refer appendixes 2. Sprints one to four), so it was helpful to develop the products that we presented as a health report and delivered to each phase. When we have finished the sprints work that pushing us as a group get our major deliveries or finished line of project. The project had lots of advantageous we can think off. How to integrate real-world product directly into our learning curve through various stages such as how to identify a client’s concerns - research, planning, design, progressive reporting and implementation of a solution to that concerns. Also, we gained heaps of knowledge on showing maturity when it comes to real work situation through team work, effective communication, information
Image of page 11
Image of page 12

You've reached the end of your free preview.

Want to read all 20 pages?

  • Spring '17
  • Sui

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

Stuck? We have tutors online 24/7 who can help you get unstuck.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes