website development project plan with a template

Project Description
The Human-Computer Interaction Lab (HCIL) allows the iSchool to showcase its proficiency in Human-Computer Interaction (HCI) research and provide information about the University of Marylandâ€s range of degrees in HCI. Our project will fulfill the clientâ€s needs by applying HCI design principles to best serve their audience while utilizing cost-effective means. This website must display current content created by the iSchool as well as degree descriptions in an effective, easily navigable way. To achieve optimal returns from the HCIL website, the project will apply HCI and User-Centered Design principles as the main development framework. These principles will steer the project towards developing a website that guarantees maximum customization and high performance.
The website been analyzed:
https://dev.hcil.umd.edu/
Assignment:
You will be outlining and developing a project plan that will describe the major milestones and the subtasks, and deadlines. Successful project plans need to map to your requirements document and the tasks that you will need to complete to deliver a satisfactory project (whether it’s a series of reports, a website, a data management plan, or user interface guidelines).
Project plans typically include the phases (milestones) of a project, activities in each phase, task end and start dates, interdependencies between tasks, and the specific individual assigned.
For this assignment, please upload your project plan, which should include the Abstract, Scope, Schedule including resources, Communications Plan, and Deliverables. This document should be professional, as if you were presenting it to an official client who would pay for your services. It should also be extremely detailed as you will use it throughout the semester in project check-in meetings.
Format:

Abstract (Copy from Requirements Document)
Scope
Schedule
Communication Plan
Deliverables

(Include a very brief Introduction Statement)
(Include a very brief Introduction Statement)
(Include a table with the schedule)
(Include a Gantt Chart)
Include assigned resources
(Include a very brief Introduction Statement)
Include a table with:
Contact at Client site (with name | email | phone)
(Bullet pointed list of deliverables for the project)

This is what I have so far:
CAPSTONE: Website Design for Human Computer Interaction Lab

1. Abstract
The Human-Computer Interaction (HCIL) lab at the iSchool needs a redesigned website. This design will hopefully improve the interaction of the website between alumni, current and future members, and anyone else who has an interest in joining the HCIL. This document will explain the design process and what took place while making the new website.
2. Scope
The project itself exists of taking selected parts of the older website and integrating them into the new website, adding new elements, and taking out old elements that Beth Domingo has deemed unnecessary.
3. Schedule
(Include a very brief Introduction Statement)
This schedule is meant to show markers, milestones, and tasks that are meant to be accomplished by a certain date. If we find it necessary to go to a previous task to make edits, the schedule will indeed be adjusted.In addition to adjustments, this schedule will also keep the team on track
(Include a table with the schedule)
(Include a Gantt Chart)
Include assigned resources
4. Communication Plan
(Include a very brief Introduction Statement)
We plan on making Skype calls weekly on Wednesday nights. This time and day seems to be the best for each team member, including Beth Domingo. Progress reports will be made and concerns or suggestions made by Beth Domingo will be addressed.
Include a table with:
Contact at Client site (with name | email | phone)
5. Deliverables
(Bullet pointed list of deliverables for the project)

A new website with source code to show how the website operates

Create a table using this format as an example:

Milestone

Task

Description

Propose New Data to Collect

1.1 Research Business Intelligence and Contract Bidding Literature

Research professional advice and literature to determine valuable data

1.2 Examine Data Currently Collected

Interview and examine current data to determine missing data

1.3 Research Potential New Data

Explore potential data for business intelligence and decisions

1.4 Develop Standards for Old and New Data Collection

Design business rules and data formatting for old and new data

1.5 Propose New Data and Standardizations

Write small proposal report and speak with client

1.6 Document Research, Data Proposal, and Standardizations

Record all decisions, steps, and rules for reference and future report building

Configure Microsoft Dynamic

2.1 Create Content Pages

Content pages to be created: 1. Home Page 2. Instruction Page (placeholder)

2.2 Configure Partnering Page

Design and configure page to collect, store, and display partnering information

2.3 Configure Opportunity Page

Design and configure page to collect, store, and display opportunity information

2.5 Configure Contacts Page

Interview and examine current data to determine missing data

2.5 Configure Document Management Settings

Implement and organize document management settings

2.6 Configure Data Management Settings

Implement and organize data management rules

2.7 Create Forms

Design and configure forms for data entry

2.8 Configure Analytics

Design and configure statistical tests for data

2.9 Configure Reporting

Design and configure graphs, tables, and pdfs for reports

2.10 Perform Unit Testing

Test each page for functionality or bugs

2.11 Perform Client User Acceptance Testing

Demonstrate page for Client for acceptance

2.12 Fix Bugs

Fix bugs or issues introduced during testing

2.13 Document steps, decisions, problems, and solutions

Record all decisions, steps, and rules for reference and future report building

Migrate data from existing system to Microsoft Dynamics

3.1 Accumulate data and capability matrices

Collect capability matrices from Business Development Group

3.2 Import Data

Import or enter data into Dynamics

3.3 Perform Unit Testing

Test Data and Reports for functionality or bugs

3.4 Fix bugs

Fix bugs or issues introduced during testing

3.5 Document steps, decisions, problems, and solutions

Record all decisions, steps, and rules for reference and future report building

Test and Debug System

4.1 Test content pages