Project Plan
Website Hardening, Team 4, IT4983 W01, D2L group 3
Date: 08/31/23
Project Participants
Project owner sponsor -
Donald Privitera
Determine the Project goals and receive the deliverables throughout the project.
dprivit2@kennesaw.edu
Team leader -
Kennedy Sanchez
Technical Writing, meeting note taker/recorder, creating and maintaining the team site, cybersecurity research, and some web server testing. I also help to facilitate group progress by scheduling and running the team meetings, creating outlines for presentations, and being available as much as possible to help clarify any issues or questions regarding the project and its expectations. I also act as a liaison between the Project Owner/Professor and the team.
Ksanch21@students.kennesaw.edu
Team members-
Alex Liu
Research, network defense planning, security policy drafting & implementation.
Aliu4@students.kennesaw.edu
Kenny Frontin
Research risk assessment on import assets, list common threats, analysis on threats that could happen
kfrontin@students.kennesaw.edu
Samrat Pandya
Server infrastructure management, research security hardening tactics, penetration testing within the server.
Spandya1@students.kennesaw.edu
Komlan Wogomebu
Help to research and implement the in accordance with the various tasks that need to be done in order to successfully complete this project.
kwogomeb@students.kennesaw.edu
Advisor / Instructor
Donald Privitera
Facilitate project progress; advise on project planning and management.
dprivit2@kennesaw.edu
Project website
https://sites.google.com/view/website-hardening-capstone?usp=sharing
Final Deliverables
Video Presentation, Project Website, Website Analysis, and Security Policies
Milestones
#1 - By 09/24/2023
#2 - By 10/22/2023
#3 FINAL - By 11/19/2023
Deliverable Expectations
Expect to finish deliverables in a timely manner and without delay. Deliverables should be of excellent quality.
Future milestone meetings date/time
Wednesdays 4:30 PM
Thursdays 4:30 PM
Fridays 4:30 PM
Times may change if needed
Collaboration Plan
Meetings in Microsoft Teams
Communication Plan & Policy
GroupMe will be used to keep track of team members and meeting times. All other communications will be done in Microsoft Teams where all materials are compiled.
Give the Team Member 24-48 hours to respond to messages. If no communication is received after 48 hours, the team will contact the leader. If no efforts for communication is made by the member, the sponsor/ professor will be notified to take further action.
Project Schedule, WBS, and Tasks Plan
See the .MPP file and Gantt chart - file attached.
Project Change Management
If any changes are needed in the scope of the project, the team will split the work appropriately between members to ensure there is no burden on one member.
Quality Assurance Plan
Team Members will check each other's work to make sure no basic mistakes are made and check for mistakes in calculations.
Risk Management Plan
There are two major sections in the risk management plan, project risk management plan and team risk management plan.
team risk management plan:
If a team member is non-communicative, the team will give them 24 hours to communicate back their status. If they haven’t responded, the remaining active team members will divide up their workload equally.
If the team leader is non-communicative, the team will give them 24 hours to communicate back their status. If they haven’t responded, the project will change its leadership to Alex Liu. And if the new team leader is non-communicative, the project will change its leadership once again. The final backup Leader will be Samrat Pandya. And due to the loss of members, the remaining active team members will divide up their workload equally.
Project Risk Management Plan:
If Microsoft Teams is down, the team will use other communication programs like Google Meets or Zoom. To conduct the meetings and the backup documents will be used to make progress on the project.
If D2L is down, the only option is to wait till service resumes. There is no other service option that replaces D2L if it is down. In the meantime, the saved documents from d2l will be used to progress on the project and if the deliverables are not submitted due to this issue, the project sponsor will be notified and updated.
If VM is down, we will use a backup VM that was safely created previously to work on the project.
