Project Administration
Nicholas will communicate with clients ahead of time to see what they would like on the website and will check to see if the Yahoo website builder can provide all of the desirables.
If there are any changes in scope then those changes will need to be mitigated through meetings with all stakeholders prior to making any major changes. Once changes are agreed to be within budget then those changes can be made.
Communication plan: Communicate with clients starting 6 months prior to the design of the website to ensure that all of the desirables are thought of. Once all desirables are made known there will be meetings once a month with all stakeholders to discuss any new desirables or change in plans. Once the project is underway, there will be daily meetings via email to ensure quality control. Once the project has been tested and debugged and tested again then the project will be approved by Nicholas Kanemoto.
Testing plan: Two days prior to the launch of the website Nick will test all of the applications used on the website and the website itself to ensure all the bugs have been worked out or can be fixed. Once the bugs are thought to have been fixed, SeleniumHQ, a test program, will be ran and will ensure that everything is working and communicating properly.
Human resource plan: Nicholas must save 1500 dollars that otherwise he would make that week on guided trips to supplement for that loss of income, as he will be working full time on the project.
Nicholas will have his family and friends check the webpage after implementation and make sure they can actually book a trip using the e-website and make sure the email address provided on the site works, Facebook link works and the YouTube link runs on the website.
Change management plan: Determine what exactly needs to change, brainstorm potential solutions, and finally decide how to move forward with the changes. This will all be done with meeting with all of the key stakeholders
Nicholas will communicate with clients ahead of time to see what they would like on the website and will check to see if the Yahoo website builder can provide all of the desirables.
If there are any changes in scope then those changes will need to be mitigated through meetings with all stakeholders prior to making any major changes. Once changes are agreed to be within budget then those changes can be made.
Communication plan: Communicate with clients starting 6 months prior to the design of the website to ensure that all of the desirables are thought of. Once all desirables are made known there will be meetings once a month with all stakeholders to discuss any new desirables or change in plans. Once the project is underway, there will be daily meetings via email to ensure quality control. Once the project has been tested and debugged and tested again then the project will be approved by Nicholas Kanemoto.
Testing plan: Two days prior to the launch of the website Nick will test all of the applications used on the website and the website itself to ensure all the bugs have been worked out or can be fixed. Once the bugs are thought to have been fixed, SeleniumHQ, a test program, will be ran and will ensure that everything is working and communicating properly.
Human resource plan: Nicholas must save 1500 dollars that otherwise he would make that week on guided trips to supplement for that loss of income, as he will be working full time on the project.
Nicholas will have his family and friends check the webpage after implementation and make sure they can actually book a trip using the e-website and make sure the email address provided on the site works, Facebook link works and the YouTube link runs on the website.
Change management plan: Determine what exactly needs to change, brainstorm potential solutions, and finally decide how to move forward with the changes. This will all be done with meeting with all of the key stakeholders