PROJ302 EduStream Project Milestones and Stakeholder Roles
- Subject Code :
PROJ302
- University :
university of technology sydney (UTS) Exam Question Bank is not sponsored or endorsed by this college or university.
- Country :
Australia
Key Schedule Milestones
The following table lists the key project milestones that have been identified. Meeting these milestones will help to ensure that the project can be delivered on time.
Date |
Event/Milestone |
22 Feb 2023 |
We would start by contacting stakeholders and contractors and building relations |
31 Mar 2023 |
Send a copy of the EduStream Project to the Board and await their decision on whether the project can proceed. |
26 Apr 2023 |
Once approved by the Board, the project will commence and funding will be distributed to pay staff and contractors. |
27 Aug 2023 |
By a certain date, engage at least one IT contractor to develop the IT specifications for EduStream, as well as collocated datacentres and service desk facilities. Complete the final step of the RFO process, which is to negotiate and sign contracts. |
30 Aug 2023 |
Finalize all technical designs to ensure so that Pilot 1 can commence |
6 Sep 2023 |
Implement all technological development, such as buying products for testing, operational, and development environments. |
6 Sep 2023 |
Teach the marketing staff and sales team through their training on how to sell new products to clients and attract participants for beta testing. |
13 Sep 2023 |
By a certain date, sign the service desk contract, which includes identifying the requirements for the service desk, investigating options, and negotiating with contractors. |
24 Sep 2023 |
Convert educational videos and games, making them available for testing by a specific date. |
8 Nov 2023 |
By a certain date, sign the datacentre contract, which includes identifying the requirements for the datacentre and investigating options |
19 Nov 2023 |
Initiate the client database and Perth CDN node's system testing. |
3 Dec 2023 |
Set the Service Desk Management System (SDMS) to work and go live on a specific date. |
31 Dec 2023 |
Begin beta testing for Pilot 1 in Perth. Fix any identified problems before commencing Sydney beta training for Pilot 2. start client database and Perth Pilot 1 acceptance testing. |
5 Jan 2024 |
Complete acceptance testing for the client database and Pilot 1 in Perth. |
4 Feb 2024 |
After rectifying problems identified in Pilot 1 Testing, commence system testing for Pilot 2 in Sydney. |
25 Feb 2024 |
Begin beta testing for Pilot 2 in Sydney. Rectify problems identified in Perth testing and test the load-sharing between the CDN servers in Sydney and Perth. Identify potential problems following Perth Node Tests. |
7 Mar 2024 |
Finalise Sydney's approval testing for Pilot 2. |
29 Apr 2024 |
After rectifying problems identified in Pilot 2 Testing, commence system testing for Pilot 3 in Melbourne. |
15 Apr 2024 |
Complete acceptance testing for Pilot 3 in Melbourne. |
29 Apr 2024 |
Begin beta testing for Pilot 3 in Melbourne to test multi-node acceptance. Rectify any issues identified during testing for all three sites and retest. |
3 Jun 2024 |
Have a full market opening of EduStream Service on a specific date that cannot be altered, per the Board's directive. Start a one-month publicity blitz to win over the general public. |
Suppliers |
|
EXTERNAL PROJECT TEAM STAKEHOLDERS |
|
Role |
Responsibilities |
Technical Team |
1) Web Server team - Creating/planning the front-end UI. - Configuring the network for the application - Install operating systems on new machines in the company. - Troubleshooting. 2) Client Database Team - Server gear maintenance and procurement - set defensive strategies in place to safeguard client/company data. - Resolve storage problems. - Setup, manage, and update software. - Client/company personnel authentication. - Data handling in a professional way. 3) Games Server Team - Responsible for server development. - Create a game concept. - Integrate the gaming code with the server. - Record and distribution of the work. 4) Client Software Team - Interact with the beta testers and the staff. - Keep project finances under control. - Produce calculations and flowcharts. - Create and compose effective code that adheres to requirements. 5) Quality Control and Testing Team - Verify the accuracy of test findings from the data. - Record and evaluate results of tests. - Collaborate with technical staff to improve outcomes by developing accurate tests. 6) System Health Management Team - Monitor network utilisation - Monitor Client feedback - Monitor traffic in the nodes - Monitor server CPU loads |
Service Desk Team |
|
Project Office Team |
|