ICTPMG613 Project Portfolio

ICTPMG613
MANAGE ICT PROJECT

PLANNING
PROJECT PORTFOLIO ASSESSOR
© MILCOM Communications Pty Ltd trading as MILCOM Institute | RTO No. 6859 | CRICOS Provider Code:03491G
Head Office: Unit 12/1866 Princes Highway Clayton VIC 3168 | Phone: 1300 369 320 | Email: International@milcom.edu.au
CRICOS Campus (QLD): Construction Training Centre, Ian Barclay Building (Room 1.9) Beaudesert Road, Salisbury 4107, QLD
CRICOS Campus (VIC): Ground Floor, 355 Spencer Street, West Melbourne 3003, VIC
Project Portfolio Assessor for ICTPMG613|v 1.0 |Last reviewed: June 2021 | Not controlled when printed Page 3 of 28
CONTENTS
Section 1: Project Management Plan 5
Section 2: Project schedule 7
Section 3: Project budget 11
Student name: Gurdeep Singh
Assessor: Mr. Anil Adhikari
Date:
Business this assessment is Boutique Business

based on:
Project descriptions: This Project is for a website design and to upgrade hardware and
software.
Section 1: Project Management Plan
PROJECT 1: Upgrade Hardware and Software
Project management models 1. The most suitable project management model for the project
“Upgrade Hardware and Software" is Agile Software Development
Discuss the most suitable
Model.
project management
model/systems development
approach for this project.
2. The Agile Software Development Model is suitable for this project
Consider the following in your for several reasons:
response:
Flexibility: The Agile model allows for flexible and iterative
 Why is this methodology development, which is beneficial when dealing with technology
suitable rather than upgrades. Since hardware and software technology can evolve rapidly,
others? Agile allows for continuous adaptation and adjustment throughout the
project.
Stakeholder Collaboration: Agile emphasizes frequent communication

and collaboration with stakeholders, including end-users. This is
advantageous for capturing their feedback, ensuring that the upgraded
hardware and software meet their specific needs and requirements.
Quality Assurance: Agile methodology incorporates continuous testing,

feedback, and improvement, resulting in a high-quality end product.
This is important for a website as it should be visually appealing, user-
friendly, and functional.
 What tailoring is Tailoring the chosen Agile methodology appropriately can help
appropriate in regards to address some of these challenges. However, it is important to
the project methodology monitor scope, manage resources effectively, and ensure effective
you have chosen? communication and collaboration with stakeholders to ensure
successful website design project execution.
Project Size and Complexity: If your project is large and complex,

you may need a methodology that provides more structure and
documentation, such as waterfall or PRINCE2. For smaller, less
complex projects, agile or iterative methodologies may be more
suitable.
Organizational Culture: Consider the culture of your organization.

Some methodologies, like agile, require a high degree of
collaboration and flexibility, while others, like waterfall, are more
structured and hierarchical. Choose a methodology that aligns with
your organization's values and norms.
Stakeholder Preferences: Take into account the preferences of key

stakeholders, such as sponsors, clients, and team members. If
stakeholders have experience or preferences for a particular
methodology, it may be beneficial to tailor your approach to
accommodate their needs.
Risk Tolerance: Assess the level of risk tolerance for your project.
Agile methodologies are often better suited for projects where
requirements are likely to change or evolve, whereas waterfall may
be more appropriate for projects with well-defined requirements
and low tolerance for change.
Resource Constraints: Consider the availability of resources,

including budget, time, and personnel. Some methodologies may
require more resources than others, so choose a methodology that
can be implemented within your constraints.
Previous Project Experience: Reflect on past project experiences

within your organization. If certain methodologies have been
successful in the past, consider leveraging similar approaches for
your current project.
Flexibility: Ultimately, aim for a methodology that provides enough

flexibility to adapt to changing circumstances while still providing
sufficient structure to ensure project success
Project Management Plan
Write a Project Management

Plan using the template in the
Simulation Pack.
List the name of your

document here and attach
your Project Management Plan
to this section of your portfolio.
If you are completing this for a
project in your workplace, you
must also use the template in
the Simulation Pack for your
Project Management Plan.
Attach:
Project Management Plan ☒
PROJECT 2: Website Design
Project management models Project Management Models: For the website design project at
Boutique Build Australia, the most suitable project management
Discuss the most suitable
model/systems development approach is the Waterfall Model. The
project management
Waterfall Model is a linear and sequential approach, which is
model/systems development
appropriate for projects with well-defined requirements and a clear,
approach for this project.
fixed scope. In the case of website design, where the client's
Consider the following in your expectations can be precisely outlined, and changes are less likely to
response: occur during development, Waterfall provides a structured and
 Why is this methodology systematic method.
suitable rather than Why Waterfall is Suitable:
others?
1.Clear Requirements: The project involves designing a website with
 What tailoring is well-defined features, such as company information, product details,
appropriate in regards to videos, a contact page, and a blog. The clear and stable requirements
the project methodology make the Waterfall Model suitable.
you have chosen?
2.Client Approval: Waterfall emphasizes client involvement at the
beginning and end of the project. This aligns with the nature of website
design, where client feedback and approval are crucial.
3.Sequential Development: The sequential phases of Waterfall -

requirements, design, implementation, testing, deployment - fit well
with the linear nature of website development.
Tailoring for Boutique Build:
While Waterfall is a well-structured model, some tailoring is necessary

to suit the specific needs of Boutique Build's website design project:
1.Client Feedback Points:
Increase client involvement by incorporating more frequent feedback

points, especially during the design and implementation phases. This
ensures alignment with the client's vision.
2.Iterative Design:
Although Waterfall is typically linear, introducing some iteration in the

design phase allows for adjustments based on client feedback without
disrupting later stages.
3.Regular Progress Updates:
Implement a robust communication plan to provide regular updates to

the client, ensuring transparency and allowing for early identification of
any deviations from the initial plan.
Project Management Plan
Write a Project Management

Plan using the template in the
Simulation Pack.

document here and attach
your Project Management Plan
to this section of your portfolio.
If you are completing this for a
project in your workplace, you
must also use the template in
the Simulation Pack for your
Project Management Plan.
Attach:
Project Management Plan ☒
Section 2: Project schedule
Complete this section for each project. If you are completing this for the case study organisation, use the
Simulation Pack information. If you are completing this for your own workplace projects, you will need to
include the information based on this.
PROJECT 1: IT Systems and Hardware Upgrade
Work Breakdown Structure Work Breakdown Structure (WBS) –
Include the title of your Work Hardware and Software Upgrade

Breakdown Structure here and
1.Project Initiation
attach it to your Portfolio.
1.1 Define Project Scope
1.2 Identify Stakeholders
1.3 Develop Project Charter
2.Planning
2.1 Develop Project Management Plan
2.2 Define Project Objectives
2.3 Create Budget
2.4 Develop Risk Management Plan
3.Hardware Procurement
3.1 Identify Hardware Requirements
3.2 Source and Order Hardware
3.3 Receive and Inspect Hardware
4.Software Procurement
4.1 Identify Software Requirements
4.2 Source and Order Software Licenses
4.3 Receive and Validate Software Licenses
5.Hardware Installation and Configuration
5.1 Install Desktop Computers for Customer Service Staff
5.2 Install Monitors for Three Customer Service Officers
5.3 Distribute New Laptops for Managers
6.Software Implementation
6.1 Install Xero Accounting Software
6.2 Set Up Microsoft Office 365 Business Premium
6.3 Install Webroot Secure Anywhere Anti-virus
6.4 Configure Dropbox for File Management
6.5 Implement Wrike for Project Management
7.User Account Setup
7.1 Create User Accounts for All Staff
7.2 Set Permissions and Access Levels
8.Data Backup and Migration
8.1 Backup Existing Data
8.2 Migrate Data to New Systems
9.Testing
9.1 Hardware Testing
9.2 Software Testing
9.3 User Acceptance Testing
10.Rollout
10.1 Communicate Changes to Staff
10.2 Monitor Rollout
10.3 Provide Post-Implementation Support
Project 1 Schedule: The project will follow a timeline with each task
aligned to the respective phase. The duration of each task will be
determined during the planning phase.
Project effort and duration PERT Formula: PERT Estimate=Optimistic+(4×Most Likely)

+Pessimistic6PERT Estimate=6 Optimistic+(4×Most Likely) +Pessimistic
Use your WBS to go through
the project activities required Activity Time Estimations:
and identify the following:
 Optimistic estimation of
each activity (best case
scenario).  Optimistic: 2 days
 Pessimistic estimation of  Most Likely: 4 days

each activity (worst case  Pessimistic: 6 days
scenario).
1.2 Identify Stakeholders
 Most likely time (best
guess).  Optimistic: 1 day
Also use the PERT formula to  Most Likely: 2 days

develop and document the
 Pessimistic: 3 days
task estimation here.
1.3 Develop Project Charter
Hint: Remember you will need
to have watched the video in  Optimistic: 3 days
your learning materials about  Most Likely: 5 days
estimating tasks and
dependence.  Pessimistic: 7 days
2.Planning
2.1 Develop Project Management Plan
 Optimistic: 4 days
 Most Likely: 6 days
2.2 Define Project Objectives
2.3 Create Budget
2.4 Develop Risk Management Plan
3.Hardware Procurement
3.1 Identify Hardware Requirements
3.2 Source and Order Hardware
3.3 Receive and Inspect Hardware
 Optimistic: 1 day
4.Software Procurement
4.1 Identify Software Requirements
4.2 Source and Order Software Licenses
4.3 Receive and Validate Software Licenses
 Optimistic: 1 day
Optimistic Time (O): 1 day Most Likely Time (M): 2 days
Pessimistic Time (P): 3 days using the PERT formula:
PERT Estimate==1+(4×2)+36PERTEstimate=61+(4×2)+3 PERT

Estimate==1+8+36PERTEstimate=61+8+3 PERT
Estimate==126PERTEstimate=612 PERT Estimate==2 days PERT
Estimate=2 days
Gantt Chart
Create a Gantt Chart based on

your work. This will be the
Project Schedule.

document here and attach it to
your Portfolio.
Schedule control Schedule Control Measures for IT Systems and Hardware Upgrade
Project:
Document here how you will
ensure that the schedule you 1.Regular Progress Meetings:
have developed is kept to i.e.
 Conduct regular progress meetings to review the status of each
schedule controls.
task.
 Discuss any delays or obstacles faced by team members.
 Adjust the schedule if necessary based on real-time

information.
2.Task Monitoring and Tracking:
 Utilize project management tools like Wrike to track task

progress.
 Monitor task completion against the planned schedule.
 Identify any deviations and take corrective actions promptly.
3.Critical Path Analysis:
 Identify and monitor the critical path of the project.
 Focus on tasks critical to project completion.
 Allocate additional resources if needed to ensure critical tasks

stay on schedule.
4.Resource Management:
 Ensure that resources are allocated efficiently.
 Address any resource constraints promptly.
 Consider resource leveling to avoid overloading team

members.
5.Regular Updates to Stakeholders:
 Provide regular updates to key stakeholders.
 Communicate any changes in the schedule.
 Share revised timelines and reasons for changes.
6.Risk Management:
 Continuously assess and manage project risks.
 Have contingency plans for potential schedule disruptions.
 Mitigate risks that could impact the project timeline.
7.Change Control Procedures:
 Implement a change control process to manage scope
 Assess the impact of changes on the schedule.
 Obtain approvals before incorporating changes into the project

timeline.
8.Performance Metrics and KPIs:
 Define and track key performance indicators (KPIs) related to

schedule adherence.
 Use metrics such as earned value analysis to measure project

performance.
 Compare planned vs. actual progress.
9.Client and Team Communication:
 Foster open communication with the client and project team.
 Encourage team members to report potential delays early.
 Address any client-related dependencies promptly.
10.Continuous Improvement:
 Regularly evaluate the effectiveness of the schedule control

measures.
 Implement lessons learned to enhance future project planning.
 Foster a culture of continuous improvement within the project

team.
11.Automated Alerts and Notifications:
 Utilize project management tools that provide automated

alerts.
 Set up notifications for approaching deadlines or potential
delays.
 Ensure prompt attention to any issues raised by automated

alerts.
12.Schedule Baseline Comparison:
 Regularly compare the current project schedule with the

baseline.
 Investigate and address any variances between the planned

and actual schedule.
 Use this information for future project planning and estimation.
Attach: Work Breakdown Structure ☐
Gantt Chart ☐
PROJECT 2: Website Design and Development
Work Breakdown Structure Work Breakdown Structure (WBS) - Website Design and Development
1.2 Identify Target Audience and User Persona
1.3 Develop Project Charter for Website Design
2.Planning
2.1 Research Competitor Websites
2.2 Define Website Objectives and Key Features
2.3 Create Budget for Website Design
2.4 Develop Risk Management Plan for Website Development
3.Design Phase
3.1 Create Wireframes and Mock-ups
3.2 Finalize Colour Palette and Typography
3.3 Develop High-Fidelity Design Mock-ups
3.4 Obtain Client Approval on Design
4.Content Creation
4.1 Develop Website Content Outline
4.2 Write and Edit Website Copy
4.3 Create or Source Visual Content (Images, Videos)
5.Development
5.1 Set Up Website Hosting
5.2 Install Content Management System (CMS)
5.3 Develop Front-End Structure and Layout
5.4 Implement Back-End Functionality
5.5 Integrate Contact Form and Database
5.6 Implement Blog Page Functionality
5.7 Ensure Responsive Design for Mobile Compatibility
6.Testing
6.1 Functional Testing
6.2 Cross-Browser Compatibility Testing
6.3 User Acceptance Testing (UAT)
6.4 Performance Testing
7.Launch
7.1 Notify Stakeholders of Website Launch
7.2 Deploy Website to Live Server
7.3 Monitor Website Performance Post-Launch
8.Post-Launch Activities
8.1 Conduct User Training (if required)
Include the title of your Work Schedule Control Measures for Website Design and Development
Breakdown Structure here and Project:
attach it to your Portfolio.
1.Regular Progress Meetings:
 Conduct bi-weekly progress meetings to review task

completion.
 Discuss any challenges faced by team members.
 Adjust the schedule if necessary based on real-time

information.
2.Task Tracking and Monitoring:
 Utilize project management tools to track task progress.
 Monitor task completion against the planned schedule.
 Identify and address any deviations promptly.
3.Milestone Reviews:
 Define key project milestones (e.g., design approval, content

completion).
 Regularly review and assess progress against milestones.
 Celebrate achievements and address any delays.
4.Client Collaboration:
 Engage the client in regular check-ins and reviews.
 Gather feedback on completed tasks promptly.
 Ensure client approvals align with the project schedule.
5.Resource Management:
 Regularly assess resource availability.
 Adjust task assignments based on workload and capacity.
 Consider resource leveling to prevent overallocation.
6.Risk Management:
 Continuously assess and manage project risks.
 Have contingency plans for potential schedule disruptions.
 Mitigate risks that could impact the project timeline.
 Implement a change control process for scope changes.
 Assess the impact of changes on the schedule.
 Obtain client approvals before incorporating changes.
8.Performance Metrics and KPIs:
 Define and track key performance indicators related to

schedule adherence.
 Use metrics such as earned value analysis to measure project

performance.
 Compare planned vs. actual progress.
9.Regular Client Updates:
 Provide regular updates to the client on project progress.
 Communicate any changes in the schedule promptly.
 Share revised timelines and reasons for changes
 Regularly evaluate the effectiveness of schedule control

measures.
 Implement lessons learned to enhance future project

planning.

team.
11.Automated Reminders and Notifications:
 Use project management tools that provide automated

reminders.
 Set up notifications for approaching deadlines or potential

delays.
 Ensure prompt attention to any issues raised by automated

alerts.
12.Schedule Baseline Comparison:
 Regularly compare the current project schedule with the

baseline.
 Investigate and address any variances between the planned

and actual schedule.
 Use this information for future project planning and

estimation.
Project effort and duration
Use your WBS to go through

the project activities required
and identify the following:
 Optimistic estimation of
each activity (best case
scenario).
 Pessimistic estimation of
each activity (worst case
scenario).
 Most likely time (best
guess).
Also use the PERT formula to

develop and document the
task estimation here.
Gantt Chart
Create a Gantt Chart based on

your work. This will be the
Project Schedule.

document here and attach it to
your Portfolio.
Schedule control
Document here how you will

ensure that the schedule you
schedule controls.
Attach: Work Breakdown Structure ☐
Gantt Chart ☐
Section 3: Project budget
Complete this section for each project. If you are completing this for the case study organisation, use the
Simulation Pack information. If you are completing this for your own workplace projects, you will need to
include the information based on this.
PROJECT 1: IT Systems and Hardware Upgrade Project
Areas of project spend 1.Hardware Procurement:
List all the resources that are  Desktop Computers for Customer Service Staff
required for the project and
 Monitors for Three Customer Service Officers
that will incur costs.
 Laptops for All Managers
Remember to include physical
resources, as well as human  Tablet Devices (Apple iPad 32GB, Wi-Fi and cellular
resources. connectivity)
2.Software Licenses:
 Xero Accounting Software
 Microsoft Office 365 Business Premium
 Webroot Secure Anywhere Anti-virus
 Dropbox (File Management)
 Wrike (Project Management Application)
3.Human Resources:
 Senior IT Project Manager (GURDEEP SINGH)
 Assistant Project Manager (Roland Morris)
 Hardware Specialist (Zakary Pineda)
 Software Specialist (Dani Chen)
4.Physical Resources:
 Desktop computers, monitors, laptops
 Tablet devices (Apple iPad)
 Necessary hardware components for system upgrades
5.Training and User Support:
 Costs associated with training staff on new systems and

software
 User support during the transition phase
6.Data Backup and Migration:
 Tools and services for data backup
 Resources for data migration
7.Testing Tools:
 Tools for hardware and software testing
 User acceptance testing tools
8.Communication and Documentation:
 Communication tools for team collaboration
 Documentation tools for project reporting and documentation
9.Miscellaneous Expenses:
 Unforeseen expenses and contingencies
 Travel expenses (if required)
 Any other miscellaneous project-related costs
Project costs estimation
For each of the items you have The total project budget is $40,000, and it will be allocated across the
listed above, include the dollar above- mentioned areas based on the specific requirements and costs
amount. associated with each component. Detailed budget breakdowns for each
category will be provided in the comprehensive project budget
Further, outline when the
document.
budget for the project will be
received so as to be clear on
cash flow.
Budget control 1.Regular Budget Reviews:
Document here how you will  Conduct regular reviews of the project budget at predefined
ensure that the budget you intervals.
 Compare actual expenses against the planned budget for each
budget controls.
category.
List at least three actions that
 Identify any discrepancies or overages promptly.
you will take to ensure budget
control. 2.Expense Tracking and Reporting:
 Utilize project management and accounting tools for expense

tracking.
 Implement a system for real-time reporting of expenses.
 Generate and analyse financial reports to monitor budget

status.
3.Budget Contingency Planning:
 Allocate a portion of the budget as a contingency fund for

unforeseen expenses.
 Clearly define the criteria for dipping into the contingency

fund.
 Obtain necessary approvals before utilizing the contingency

fund.
4.Vendor and Resource Management:
 Regularly review vendor contracts and agreements.
 Ensure that vendors adhere to agreed-upon pricing.
 Negotiate with vendors for favorable terms and discounts.
5.Resource Allocation Efficiency:
 Monitor the allocation of human and physical resources.
 Optimize resource allocation to prevent overutilization or idle

resources.
 Adjust resource assignments based on project needs and

timelines.
 Implement a change control process for any scope changes.
 Assess the impact of changes on the budget.
 Obtain approvals before incorporating changes that affect
costs.
7.Budget Communication:
 Maintain open communication with project stakeholders

regarding budget status.
 Regularly update key stakeholders on budgetary concerns or

changes.
 Foster a transparent and collaborative approach to budget

management.
8.Training and Awareness:
 Provide training to project team members on budget

management.
 Ensure team members are aware of budget constraints and

guidelines.
 Encourage a cost-conscious mindset within the project team.
9.Invoice and Payment Verification:
 Implement a robust invoice verification process.
 Verify that invoices align with agreed-upon rates and services.
 Ensure accurate and timely payments to vendors and service

providers.
10.Financial Audits:
 Conduct periodic financial audits to validate budget adherence.
 Engage internal or external auditors to review project finances.
 Use audit findings to improve budget management processes.
 Regularly evaluate the effectiveness of budget control

measures.
 Implement lessons learned to enhance future project

budgeting.

team.
PROJECT 2: Website Design and Development
Areas of project spend Project 2: Website Design and Development Areas of Project Spend:
List all the resources that are 1.Human Resources:

required for the project and
 Senior IT Project Manager Me
that will incur costs.
 Project Assistant Ben Nguyen
Remember to include physical
resources, as well as human  Software Specialist Dani Chen
resources. 2.Software and Tools:
 Design Software Licenses
 Content Management System (CMS) License
 SEO Tools and Analytics Services
3.Content Creation:
 Copywriting Services
 Visual Content Creation (Images, Videos)
4.Website Hosting:
 Purchase and Setup Hosting Services
 User Training for Client's Staff (if required)
 Post-Launch User Support
6.Testing Tools:
 Testing Software and Tools
 Unforeseen Expenses and Contingencies
 Travel Expenses (if required)
Project costs estimation 1.Human Resources:
For each of the items you have  Senior IT Project Manager: $15,000
listed above, include the dollar
 Project Assistant: $8,000
amount.
 Software Specialist: $10,000
Further, outline when the
budget for the project will be 2.Software and Tools:
received so as to be clear on  Design Software Licenses: $3,000
cash flow.  CMS License: $1,500
 SEO Tools and Analytics Services: $2,000
3.Content Creation:
 Copywriting Services: $5,000
 Visual Content Creation: $7,000
4.Website Hosting:
 Hosting Services: $2,500
 User Training: $3,000
 Post-Launch User Support: $2,000
6.Testing Tools:
 Testing Software and Tools: $1,500
 Unforeseen Expenses: $4,000
 Travel Expenses: $1,500
Total Project Budget: $70,500
Budget control 1.Regular Budget Reviews:
Document here how you will  Conduct bi-weekly budget reviews to monitor expenses.
ensure that the budget you
 Compare actual costs against the planned budget.
budget controls.  Address any budget overages promptly.
List at least three actions that 2.Expense Tracking and Reporting:

you will take to ensure budget  Utilize project management and accounting tools for expense
control. tracking.
 Implement real-time reporting of expenses.
 Generate financial reports for analysis.
3.Vendor and Resource Management:
 Regularly review vendor contracts and agreements.
 Ensure adherence to agreed-upon pricing.
 Negotiate with vendors for favourable terms.
 Implement a change control process for scope changes.
 Assess the impact of changes on the budget.
 Obtain approvals before incorporating changes.
5.Financial Audits:
 Conduct periodic financial audits to validate budget adherence.
 Engage internal or external auditors for reviews.
 Use audit findings to improve budget management processes.

ICTPMG613 Project Portfolio

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ICTPMG613 Project Portfolio

Uploaded by

Copyright:

Available Formats

ICTPMG613

MANAGE ICT PROJECT

Section 2: Project schedule 7

Section 3: Project budget 11

Assessor: Mr. Anil Adhikari

Business this assessment is Boutique Business

PROJECT 1: Upgrade Hardware and Software

Stakeholder Collaboration: Agile emphasizes frequent communication

Quality Assurance: Agile methodology incorporates continuous testing,

Project Size and Complexity: If your project is large and complex,

Organizational Culture: Consider the culture of your organization.

Stakeholder Preferences: Take into account the preferences of key

Resource Constraints: Consider the availability of resources,

Previous Project Experience: Reflect on past project experiences

Flexibility: Ultimately, aim for a methodology that provides enough

Project Management Plan

Write a Project Management

List the name of your

3.Sequential Development: The sequential phases of Waterfall -

Tailoring for Boutique Build:

While Waterfall is a well-structured model, some tailoring is necessary

1.Client Feedback Points:

Increase client involvement by incorporating more frequent feedback

Although Waterfall is typically linear, introducing some iteration in the

3.Regular Progress Updates:

Implement a robust communication plan to provide regular updates to

Write a Project Management

List the name of your

PROJECT 1: IT Systems and Hardware Upgrade

Work Breakdown Structure Work Breakdown Structure (WBS) –

Include the title of your Work Hardware and Software Upgrade

1.2 Identify Stakeholders

1.3 Develop Project Charter

2.1 Develop Project Management Plan

2.2 Define Project Objectives

2.3 Create Budget

2.4 Develop Risk Management Plan

3.1 Identify Hardware Requirements

3.2 Source and Order Hardware

3.3 Receive and Inspect Hardware

4.1 Identify Software Requirements

4.2 Source and Order Software Licenses

4.3 Receive and Validate Software Licenses

5.Hardware Installation and Configuration

5.1 Install Desktop Computers for Customer Service Staff

5.2 Install Monitors for Three Customer Service Officers

5.3 Distribute New Laptops for Managers

6.2 Set Up Microsoft Office 365 Business Premium

6.3 Install Webroot Secure Anywhere Anti-virus

6.4 Configure Dropbox for File Management

6.5 Implement Wrike for Project Management

7.User Account Setup

7.1 Create User Accounts for All Staff

7.2 Set Permissions and Access Levels

8.Data Backup and Migration

8.1 Backup Existing Data

8.2 Migrate Data to New Systems

9.1 Hardware Testing

9.2 Software Testing

9.3 User Acceptance Testing

10.1 Communicate Changes to Staff

10.2 Monitor Rollout

10.3 Provide Post-Implementation Support

Project effort and duration PERT Formula: PERT Estimate=Optimistic+(4×Most Likely)