Question:

Project Schedule.

1. Project Schedule for the MXE Project. Ensure it has the following elements: (Tabular Format)

It completely tracks with the WBS. In fact, the WBS should, with minor exceptions, be the vertical axis.

It includes MILESTONES.

It reflects the time allocated in the Project Charter

It has PRECEDENCES.

2. In a not-to-exceed one page paper, discuss the difference between a Network Schedule and a Gantt Chart. What are they? What are the pros and cons of each?

Note: please be specific to the below question mentioned

--------------------------------------------------------------------------------------------------------------------

Background Information:

Please find the project charter and scope statement below

PROJECT CHARTER

PROJECT NAME	Multiplex Engineering HR Information System Project
DEPARTMENT/UNIT	HR Department
PROJECT BUDGET	$500,000
PROJECT START DATE	August 7, 2023
DURATION	6 months
PREPARED BY	Project Management Team
DOCUMENT VERSION	1.2	DATE (MM/DD/YYY)	06/04/2023

DOCUMENT PURPOSE

The Project Charter formalizes the agreement between the Project Sponsor and the Project Manager/Team, defining success metrics and serving as a reference throughout the project. It provides an overview of the project's goals, resource requirements, and scope boundaries. Scope changes require a documented request with an impact analysis, subject to formal approval. The project manager maintains additional documents, including a communications plan, issues log, risk log, change management plan, budget, and work schedule, to manage and track project details.

REVIEW & APPROVAL The Project Sponsor's signature on the Project Charter signifies approval, and acceptance of responsibilities, and authorizes the Project Manager and Team to proceed with detailed planning and execution using allocated resources.
Project Sponsor(s) Name	Signature	Date
Evelyn Carter

PROJECT OBJECTIVE

Develop and implement a web-based information system at Multiplex Engineering (MXE) that enables employees and customers to independently manage their records, resulting in streamlined HR operations, enhanced data accuracy, and improved efficiency in HR processes.

CURRENT SITUATION/PROBLEM/OPPORTUNITY STATEMENT

Multiplex Engineering (MXE) faces challenges in efficiently managing a large volume of employee and customer records, leading to potential delays, inefficiencies, and data inaccuracies. To address this, MXE has the opportunity to implement a web-based information system that empowers users to self-manage their records. By doing so, MXE can ease the burden on the HR department, streamline processes, ensure data accuracy, and enhance overall operational efficiency. To achieve this within the given timeframe, MXE's Project Sponsor and management team have decided to hire a software vendor with expertise in developing the HRIS, ensuring timely completion and leveraging external knowledge.

SCOPE

• Development of Human Resources Information System (HRIS): The project focuses on the development of an HRIS to manage human resources information effectively.

• Phased Implementation: The project will be executed in phases, with a detailed schedule provided and mutually agreed upon by all stakeholders.

• Acceptance Procedures: Separate acceptance processes will be established for technical aspects and user acceptance. This ensures that both technical requirements and user expectations are met.

• New Feature Specifications: Specific new features and functionalities required in the HRIS will be itemized and communicated to the vendor. These requirements will serve as guidelines for the development and customization of the system.

• System Maintenance: The vendor will be responsible for providing customers and system maintenance services for a duration of 6 months following the acceptance date. After this period, the maintenance responsibility will be transitioned to Multiplex Engineering (MXE).

• Data Migration: The vendor will assume responsibility for the seamless migration of data from the legacy system to the new HRIS.

• Training: The vendor will conduct the training for the IT team, HR personnel, and users on system maintenance, management, and usage, respectively.

OUT OF SCOPE

• Network Infrastructure Upgrade: The project does not encompass any upgrades or modifications to the current network infrastructure at MXE. This responsibility lies outside the scope of the project.

• Database Update/Maintenance Responsibility: The project does not include the update or maintenance of the database. MXE will retain full responsibility for updating the database, and it will not be delegated to the software vendor involved in the project.

• Hardware Procurement: The project does not involve the procurement or installation of new hardware devices or equipment. This responsibility lies outside the scope of the HRIS development project.

PROJECT REQUIREMENTS & ASSUMPTIONS

#	Description
1	The ability of the new HR Information System to handle over 10,000 employee records effectively
2	The system should provide self-service functionality for employees and customers to update their personal information, such as contact details, tax information, and benefits enrollment.
3	The project is not to exceed the $500,000 budget
4	Project completion not to exceed six months
5	The project team to collaborate with the stakeholders and HR personnel to gather the requirements
6	The system is compliant with data protection and privacy.
7	The system is user-friendly for all levels of technical expertise.

PROJECT BOUNDARIES & CONSTRAINTS

#	Description
1	The project is limited to the development and implementation of HR Information System and does not include any organizational and process changes.
2	The project budget is fixed at $500,000 and cannot be exceeded.
3	The project duration is fixed at six months, and any delays must be managed within this timeframe.
4	The system implementation should not disrupt ongoing HR operations and services provided to employees and customers.
5	Ensure that the new system is compatible with the existing IT infrastructure.
6	Any change or additions to the project scope should follow the Change Management process.

KEY SUCCESS CRITERIA

#	Measure of Success	How is it measured
1	Web Application Loading Time	Achieving a loading time of 1 second or less
2	User Interaction Responsiveness	Ensuring user interactions are processed within 100ms or faster.
3	Data Accuracy	Reaching a data accuracy rate of 99% or higher.
4	System Availability	Maintaining system uptime of 99% or higher.
5	Security and Privacy	Meeting compliance standards and achieving zero security breaches or data leaks.
6	Scalability	Ensuring the system can handle a concurrent user load without performance degradation.
7	Compatibility	Supporting multiple browsers and operating systems (e.g., Chrome, Firefox, Safari, Windows, iOS).
8	Usability	Obtaining a user satisfaction rating of 4 out of 5 or higher in usability surveys.

PROJECT MILESTONES & DELIVERABLES

#	MILESTONES	DELIVERABLES
1	System Design Completion	System design document Functional and technical specifications User interface design
2	System Testing	System deployment in the test environment Test plan and results Performance testing
3	System Deployment and Integration	Deployment and Integration plan System Deployment and Integration into the production environment System documentation Training materials and training sessions
4	User acceptance testing	User acceptance test cases and scenarios Feedback and improvement request Approval for system release
5	Go Live	Post Implementation support plan Transition of support/maintenance to the internal team Lesson learned documentation. Project closure

VENDOR DELIVERABLES

MXE made a make-or-buy decision. MXE decided to contract a vendor to provide a customized system that meets the company's specific needs. Among the options presented by four vendors, MXE chose option 4 (WeCode) due to its extensive features, user-friendliness, and after-sales support, despite being slightly higher in cost.

#	DELIVERABLE
1	Design Documents
2	Web/Software Application
3	System Integration
4	Data Migration
5	User Training
6	Documentation (User manual, technical specification, software management)
7	After-sales support

POTENTIAL RISKS & STRATEGIES

#	RISK	MANAGEMENT STRATEGY
1	Scope Creep	Provide clear project scope and obtain stakeholder sign-off. Establish a change management plan.
2	Delay in deliverables	Develop a realistic project schedule with buffer time for unforeseen delays
3	A data breach or unauthorized access	Work with the IT security group to conduct a security assessment
4	Cost Overruns	Develop a detailed project budget and monitor regularly
5	Lack of skilled resource	Hiring an external contractor with the required skills Engaging stakeholders and managing expectations to gain support throughout the project.

PROJECT COMMUNICATION ACTIVITIES

Description of Communication Activity	Meeting Participants & Document Recipients	Frequency of Communication	Person Responsible for Communication Activity	Distribution Method	Archive Location
Project Team Meetings	Project Team	Weekly	Project Manager	Meeting notes distributed thru the team's email list	Notes stored on the project's Gdrive
Sponsor Meetings	Sponsor & Project Manager	Monthly	Project Manager	Meeting notes sent to the Sponsor	Notes stored on the project's Gdrive
Project Status Report	Sponsor & Project Team	Monthly	Project Manager	Reports are distributed thru the team's email list and sponsor	Reports stored on the project's Gdrive
Project Planning Document	Sponsor & Project Team	As Needed	Project Manager	Notification of document creation/update emailed to the project team	All documents will be stored on the project's gdrive.

CHANGE MANAGEMENT REQUIREMENTS & ACTIVITIES

Any changes outside the project scope must undergo a formal approval process. The change request should include a clear justification for the change, an assessment of its potential impact on time and cost, and an estimation of the resources required.

PROJECT LEADERSHIP, ROLES & RESPONSIBILITIES

ROLE	NAME & TITLE	RESPONSIBILITIES
Project Sponsor	Evelyn Carter Chief Human Resource Officer	Provides HR resources to complete the project.
Project Champion	James Lee Chief Information Technology Officer	Provides technical resources supporting the development of the new web application.
Functional Project Owner(s)	Laura Jones Director of HR Accounting & HRIS	Coordinates system-level HR related activities with campus HR departments
Project Manager	Raquel Edora Project Manager	Schedules resources on both the technical and/or HR sides to ensure project completion
Project Management Team Members	Ramadevi Adoni Habeeb Khan Monish Manohar Adari Shoaib Ahmed	Understanding and completing the required work, including research, data gathering, analysis, and documentation. Informing the project manager and team members about any issues, scope changes, risks, and quality concerns. Proactively communicating project status and managing expectations.

RACI MATRIX FOR PROJECT SUCCESS

ROLES	RESPONSIBLE	ACCOUNTABLE	CONSULTED	INFORMED
Project Sponsor
Project Champion
Functional Project Owner(s)

Scope Statement

Project Title:Multiplex Engineering HR Information System Project

Date:21/06/23Prepared by:Team A

Project Justification:

The project aims to develop and implement a web-based Human Resources Information System (HRIS) at Multiplex Engineering (MXE) that enables employees and customers to self-manage their records. The project is needed to address the challenges of efficiently managing a large volume of employee and customer records, which affect the service quality, satisfaction, and operational efficiency of MXE. The project will benefit MXE by improving data accuracy, security, and compliance; increasing productivity and efficiency; enhancing user empowerment and engagement; and reducing operational costs.

Product Characteristics and Requirements:

Product Characteristics:

• User-friendly interface: The HRIS should have a simple and intuitive interface that allows users to access, update, and manage their personal information easily and quickly.
• Secure data encryption: The HRIS should encrypt all data in transit and at rest using industry-standard encryption algorithms and protocols to ensure data security and privacy.
• Fast data processing: The HRIS should process data efficiently and accurately without causing delays or errors in the system's performance or functionality.
• Customizable features: The HRIS should allow users to customize their preferences and settings according to their needs and roles.

Product Requirements:

• Self-service functionality: The HRIS should provide self-service functionality for employees and customers to update their personal information, such as contact details, tax information, and benefits enrollment. This will reduce the workload and pressure on the HR department and improve user satisfaction and empowerment.
• Data accuracy, security, and compliance: The HRIS should improve data accuracy, security, and compliance by automating data validation, encryption, and backup. This will ensure that the data is consistent, reliable, and protected from unauthorized access or loss. The HRIS should also comply with data protection and privacy laws and regulations in the relevant jurisdictions.
• Operational efficiency: The HRIS should enhance operational efficiency by reducing manual tasks, errors, and costs associated with data management. This will save time and money for the organization and increase productivity and profitability.

Summary of Project Deliverables

Project management-related deliverables:business case, charter, team contract, scope statement, WBS, schedule, cost baseline, status reports, final project presentation, final project report, lessons-learned report, and any other documents required to manage the project.

In addition, the following will need to be provided:

• Software vendor contract
• Risk register
• Communication plan
• Change management plan
• Quality management plan
• Project closure report

Product-related deliverables:research reports, design documents, software code, hardware, etc.

• Web-based HRIS that provides self-service functionality for employees and customers
• System acceptance report that documents both technical and user acceptance testing

Technical Deliverables:

• System architecture diagram - components, interfaces, and interactions of the HRIS
• System design document - features, functions, data structures, algorithms, user interfaces, etc. of the HRIS
• System stage test plan - this is categorized into two: technical and functional.
  • Technical - Unit testing
  • Functional - System Integration testing and User acceptance testing
• System configuration document - the hardware and software requirements and settings for installing and running the HRIS.
• Data migration plan - the steps and procedures for transferring data from the legacy system to the new HRIS
• System maintenance plan - roles and responsibilities of the vendor and MXE for providing customer and system support for six months after the acceptance date.
• Training plan - the learning objectives, methods, materials, and evaluation for the IT team, HR personnel, and users on system maintenance, management, and usage

Project Success Criteria:

Business:

#	Measure of Success	How is it measured
1	Cost and time of the project	Based on the budget and schedule defined and approved in the project charter. The project will cost $500,000 and takes 6 months to complete. Cost variance (CV) = Earned value - Actual cost Schedule variance (SV) = Earned value - Planned value Cost performance index (CPI) = Earned value / Actual cost Schedule performance index (SPI) = Earned value / Planned value
2	Scope and deliverables	The project's scope and deliverables are based on the approved scope statement and deliverables list in the project charter. Percentage of deliverables completed = Number of deliverables completed / Number of deliverables planned Percentage of deliverables accepted = Number of deliverables accepted / Number of deliverables completed Percentage of scope changes approved = Number of scope changes approved / Number of scope changes requested
3	Value and benefits of the project	The project is expected to have a positive value within 24 months after the acceptance date based on the estimates and justifications indicated on the business case. Return on investment (ROI) = (Benefits - Costs) / Costs Benefit-cost ratio (BCR) = Benefits / Costs Net present value (NPV) = Present value of benefits - Present value of costs Internal rate of return (IRR) = Discount rate that makes NPV equal to zero Payback period = Time required to recover the initial investment

Technical Functionality:

#	Measure of Success	How is it measured
1	Web Application Loading Time	Achieving a loading time of 1 second or less
2	User Interaction Responsiveness	Ensuring user interactions are processed within 100ms or faster.
3	Data Accuracy	Reaching a data accuracy rate of 99% or higher.
4	System Availability	Maintaining system uptime of 99% or higher.
5	Security and Privacy	Meeting compliance standards and achieving zero security breaches or data leaks.
6	Scalability	Ensuring the system can handle a concurrent user load without performance degradation.
7	Compatibility	Supporting multiple browsers and operating systems (e.g., Chrome, Firefox, Safari, Windows, iOS).
8	Usability	Obtaining a user satisfaction rating of 4 out of 5 or higher in usability surveys.
9	Functionality	The application meets all requirements stated in project documents and specifications, verified through testing and acceptance reports.
10	Maintainability	After six months, the internal team can maintain and update the system without issues, supported by relevant documents. This ensures MXE's independent system management.

Lifecycle Phases of the MXE HRIS Project

The following are the 7 lifecycle phases that are applicable to the MXE HR Information System project.

1. Planning & Analysis

During the initial planning phase, requirements are gathered from stakeholders and clients. This involves evaluating customer needs, production costs, and other factors, and prioritizing features and development timelines.

1. Define Requirements

This phase converts gathered information into clear development requirements.

1. Design

In the design phase, the original plan and vision come to life on paper. This includes creating a software design document (SDD) with system design, templates, and platform. Flowcharting user interactions is also part of this phase. Sometimes, a prototype is developed to visualize the product and make necessary changes before development.

4. Development

During development, the team breaks down the project into modules and writes the necessary code. It can be time-consuming, so having a timeline and milestones helps manage expectations and track progress. Sometimes, the development and testing stages overlap to catch any critical bugs.

5. Testing

Before launching the system, the quality assurance team performs validation testing to ensure proper functionality. This process also helps identify user experience and security issues. Simulated environments or automated tests may be used. Testing includes performance, functional, usability, and acceptance testing. The final stage confirms if the software delivers as promised.

6. Deployment

The final product is delivered to the intended user during the deployment phase.

7. Maintenance and Operations

The team continuously identifies technical and functional enhancements to improve the product.

Life Cycle Phase	Deliverable	Level 3 Deliverables	User ID
Initiation Phase	Project Charter	- Stakeholder Analysis	U1
		- Business Case	U2
Planning Phase	Project Management Plan	- Scope Management Plan	U3
		- Schedule Management Plan	U4
	Requirements Documentation	- Functional Requirements Specification	U5
		- Technical Requirements Specification	U6
	Risk Management Plan	- Risk Identification and Assessment	U7
		- Risk Mitigation Plan	U8
Execution Phase	Design and Development	- System Design	U9
		- Software Development	U10
	Quality Assurance	- Test Plan	U11
		- Test Cases	U12
	Deployment	- Installation Plan	U13
		- User Training	U14
	Performance Monitoring and Control	- Performance Metrics Tracking	U15
		- Issue Resolution	U16
Closing Phase	Project Acceptance	- Acceptance Criteria	U17
		- Client Sign-off	U18
	Lessons Learned Report	- Lessons Identified	U19
		- Recommendations for Future Projects	U20

The table is divided into two main areas, the deliverables and the life cycle phases, as you can see. The deliverables are stated in the left-hand column, and the life cycle phases are given at the top of the table. Below each deliverable is a list of the level 3 deliverables. The final column contains a list of the user ID