Project Plan: VMware Vsphere Implementation for Simple Studios

Verified

Added on  2023/01/05

|4
|981
|46
Project
AI Summary
This project plan details the implementation of VMware Vsphere and related technologies for Simple Studios Pty Ltd, a graphic design company expanding its infrastructure. The plan, developed using Agile SCRUM methodology, outlines key objectives such as creating a competitive network, implementing security measures, and reducing IT expenses. The project, initiated on July 29, 2019, and scheduled for completion on November 25, 2019, involved connectivity and data migration testing. The plan includes a product backlog with user stories, sprint planning, testing procedures, and retrospective analysis. The project faced challenges related to hardware capacity and team knowledge gaps, which were addressed through training. The student's plan includes a project methodology, references, and a cover letter, providing a comprehensive overview of the project's scope, objectives, and execution strategy.
Document Page
Running head: PROJECT PLAN
Project Plan
Name of the Student:
Name of the University:
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
1PROJECT PLAN
Dean Robertson
Please enter your address
27th September, 2019
Jon Bon (CEO of Simple Studios)
Hilary Flamingoose (Art Production Manager)
Dear Jon and Hilary,
I am writing to provide a brief of our project plan on “Implementation of VMware Vsphere and
Technologies for Simple Studios Pty Ltd”. We developed this project as our implementation plan
would shift operations from various physical servers and combined in single physical server.
Our project had started work on 29th July, 2019 and it is estimated to complete on 25th
November, 2019. Therefore, we scheduled the project plan for 24 weeks. As our acceptance
project criteria, we determined that the project will finish on time and proposed network would
be secured. The software is being implemented and functioning with the system to be scalable.
While working in the project, our business faced challenges when it is seen that the hardware
can handle specific amount of applications. Some of the team members had limited knowledge
in software networking; therefore we decided to provide training to them. Training program is
conducted for them. The key objectives of our project are creating a network for Simple Studios
Pty Ltd to be competitive with other business organizations. There is implementation of network
security for mitigating attacks and monitoring traffic.
The project is involved with investigating the current networking system of Simple Studios Pty
Ltd by designing a planned network. We had conducted connectivity test to authorize continuity
of the network communications and data migration test to contrast migrated data with innovative
data to find out discrepancies when moved data from legacy database to destination database.
Our implementation work is proceeding with reducing IT expenses while improving business
competence and agility of the business.
I am eager to hear your comments and please to provide answers to your questions you may
have. You can reach me at +61-260-6790.
Thank you for your valuable time and attention.
Yours faithfully,
Dean Robertson
Document Page
2PROJECT PLAN
Project Methodology
In order to implement VMware Vsphere and Technologies for Simple Studios Pty Ltd,
Agile SCRUM methodology is used. The implementation work is carried out by focusing on
below steps of SCRUM methodology such as:
Create product backlog: The product backlog is contained list of the user stories for
implementing VMware Vsphere and Technologies.
ID User Story
a-001 As a project manager, I have ability to add new project tasks, change the project
duration plus start date of existing one.
a-002 As a project coordinator, I am responsible to maintain and monitor project plan,
schedule, budget and documentation work.
a-003 As a project support administrator, I have ability to build action plan, analyse
risks and required project resources to conduct connectivity and data migration
testing.
Sprint planning and backlog creation: The sprint length is of same length for project
duration which is 24 weeks. The Scrum team members proceed with meeting to complete the
implementation work (Sandberg and Crnkovic 2017). The improvements are being reviewed
and it is planned in next sprint. Each of the project sprints is lasted for 2 weeks, and most
important is coordination among the project stakeholders as well as team members (Rigby,
Sutherland and Takeuchi 2016). The Scrum team comprised 3 members. The member is
combination of project coordinator, project manager and project support administrator. The team
is in charge to deliver increments of product by completion of each sprint. The team selected
important user stories from listed product backlog. The role of Scrum master is to resolve issues
faced by the project group. It is same as project manager in project team. They can assist team
to plan work for next sprints.
Testing and product demonstration: Full life cycle testing is performed by means of
connectivity testing and data migration testing. The cost of testing period is reduced by
decreasing entire amount of user stories. Therefore, there is minimization of bugs. Result of
each sprint is demonstration of product (López-Martínez et al. 2016). The key project
stakeholders are taking decisions for project changes.
Retrospective and next sprint planning: At the final stage, there is discussion of results
as well as determine methods to improve over the development process of implementation work
on next step (Hernández, Kreye and Eppinger 2019). Then the Scrum team concentrated on
next planning of sprint.
Document Page
3PROJECT PLAN
References
Hernández, T.R., Kreye, M. and Eppinger, S., 2019. Applicability of Agile and Scrum to Product-
Service Systems. In EurOMA Conference.
López-Martínez, J., Juárez-Ramírez, R., Huertas, C., Jiménez, S. and Guerra-García, C., 2016,
April. Problems in the adoption of agile-scrum methodologies: A systematic literature review.
In 2016 4th International Conference in Software Engineering Research and Innovation
(CONISOFT) (pp. 141-148). IEEE.
Rigby, D.K., Sutherland, J. and Takeuchi, H., 2016. Embracing agile. Harvard Business
Review, 94(5), pp.40-50.
Sandberg, A.B. and Crnkovic, I., 2017, May. Meeting industry: academia research collaboration
challenges with agile methodologies. In Proceedings of the 39th International Conference on
Software Engineering: Software Engineering in Practice Track (pp. 73-82). IEEE Press.
chevron_up_icon
1 out of 4
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]