REFERENCE

INTRODUCTION

This project aims to upgrade all Australian Pacific College computer room computers to Windows 11 operating system and upgrade all computer parts such as font, memory, processor, graphics card to ensure compatibility with latest computer programs and improve performance. To ensure proper compatibility, each computer will need to be tested. Any computer found to be incompatible with Windows 11 and found to have old parts will be upgraded or replaced. No external resources or outsourcing is envisaged for this Project.

SCOPE MANAGEMENT APPROACH

For this project, scope management will be the sole responsibility of the Project Manager. The scope for this project is defined by the Scope Statement, Work Breakdown Structure (WBS) and WBS Dictionary. The Project Manager, Sponsor and Stakeholders will establish and approve documentation for measuring project scope which includes deliverable quality checklists and work performance measurements. Proposed scope changes may be initiated by the Project Manager, Stakeholders or any member of the project team. All change requests will be submitted to the Project Manager who will then evaluate the requested scope change. Upon acceptance of the scope change request the Project Manager will submit the scope change request to the Change Control Board and Project Sponsor for acceptance. Upon approval of scope changes by the Change Control Board and Project Sponsor the Project Manager will update all project documents and communicate the scope change to all stakeholders. Based on feedback and input from the Project Manager and Stakeholders, the Project Sponsor is responsible for the acceptance of the final project deliverables and project scope.

SCOPE DESCRIPTION

The scope of this project was defined through a comprehensive requirements collection process. First a thorough analysis was performed on APC.'s current operating system based on employee and student's feedback. From this information, the project team developed the project requirements documentation, the requirements management plan, and the requirements traceability matrix for what the new operating system must accomplish. The project description and deliverables were developed based on the requirements collection process and input from employees using the computers as well as the IT department. This process of expert judgment provided feedback on the most effective ways to meet the original requirements of providing a new operating system from which Australian Pacific College can improve its computer systems compatibility with the latest software applications.

Project Scope Statement

This project includes the testing of all 20 computers on the network for compatibility with Windows 11, the replacing of incompatible computer components, the replacement of nonupgradeable computers, and the installation of Windows 11. The deliverables for this project are the complete installation of Windows 11 on all 20 computers. This project will be accepted once all 20 computers are fully operational with Windows 11. Only internal personnel and resources may be used for this project. Additionally, the project is not to exceed 30 days in duration or $15,000 in spending. Assumptions for this project are that support will be provided by the Project sponsor and all department managers and the adequate internal resources are available for the successful completion of this project.

QUESTIONS

Q1 Explain the steps you will follow to communicate a shared understanding of the project and obtain agreement from stakeholders for the plan

PC 14 Contribute to achieving an agreed schedule baseline and communication of the schedule to stakeholders

PC11 Develop and confirm procedures for project authorisation with an appropriate authority

PC12 Obtain authorisation to expend resources

PC23 Establish a shared understanding of desired project outcomes with relevant stakeholders

Q2 - BOUNDARIES AND EXCLUSIONS

Explain what will be included in the project and also what will not be included in the project

KE - factors likely to impact the project scope

KE - problem areas likely to be encountered in scope management

Q3 - Time Management

• What time management issues arose in the project that caused the project not to meet the original timeline
• what recommendations would to make to reduce this from happening in the future
• Explain what tasks were managed well and demonstrated effective time management

PC31 Review schedule performance records to determine effectiveness of time management activities

PC32 Identify and document time management issues and recommend improvements

PE - conduct a review of project scheduling and recommend improvements for the future

Q4 - Explain the impact that these delays had on the schedule and the costings for the project

PC23 Analyse and forecast impact of changes to the schedule

Q5 - What scope changes have you had to implement so far in your project and explain what impact they have had on time, cost and quality for your project? Will you still maintain your project objectives?

PC25 Develop responses to potential or actual schedule changes and implement them to maintain project objectives

PC32 Monitor impact of scope changes within established time, cost and quality constraints according to change control procedures

Q6 - What scope management issues occurred in your project and what improvement recommendations would you make for future projects?

PC33 Identify and document scope management issues and recommend improvements for future projects

PE - review and document scope-management implementation and recommend improvements

Q7 - Explain two time management methodologies, their capabilities, limitations, applications and outcomes

KE - best-practice time management methodologies, their capabilities, limitations, applications and outcomes

Q8 - Explain the importance of managing scope throughout the project life cycle and the impact it can have on the project if it is not managed

KE - project life cycle and the significance of scope management

Q9 - Provide a list and brief explanation of the various documents that are created during the project initiation phase

KE - types of project initiation documentation