WBS is needed by decomposing the scope for your project into deliverables and enter these as "tasks" in your project file. You must have at least 5 deliverables.

Decompose the deliverables further into work packages (tasks) and enter them under your deliverables. It is helpful to keep your deliverables as nouns, and to use verbs for each task. Include enough detail to have 20-25 unique tasks.

Code the project following the 1.1, 1.1.1, 1.2 format. Establish the project schedule by estimating time durations for all of your individual tasks. Enter the duration (in days) for each task. Using a task's Notes feature, justify the time estimates for at least 5 tasks. For example, you might make the following note: "This will take 3 days to allow the paint to dry before applying the trim." Enter at least 3 milestones for your project. Milestones typically use passive verbs (i.e. Phase 1 completed) and do not have any duration assigned to them (0 days).

Not all tasks start immediately after a task ends (they "lag") or wait until a task is completely finished before starting (they "lead"). Therefore, have at least 1 task include lead time or lag time. In the Notes section for this task, indicate why there would be a lead/lag for that particular task.

For every task, assign the appropriate resource(s). Do not assign resources to summary tasks (your deliverables) or milestones (event markers).

1If a resource can be over-allocated, justify the "why" in the task's Notes.to assign workers and estimate your resource costs. Enter at least 6 human resources on the Resource Sheet.

When tasks, costs, and resources are entered correctly and you have double-checked for accuracy, set the project baseline. This sets the budget and schedule for the project. Next, display the project as a network diagram to show the critical path in your project.

PROJECT DURATION 2 MONTHS OCTOBER 26, 2020 TO December 29, 2020

POS Implementation: Work Breakdown Structure

1.1. Project Management: POS Implementation

1.2. Requirements

1.2.1. Technical

1.2.1.1. Hardware and peripherals

1.2.1.2. Software

1.2.1.2.1. POS support software

1.2.1.2.1.1.1. Custom inventory interconnect

1.2.1.2.1.1.2. Custom accounting interconnect

1.2.1.2.1.1.3. Backup software licenses

1.2.1.3. Networking

1.2.1.3.1. VPN

1.2.1.3.2. Security

1.2.1.3.3. Redundancy / DR

1.2.2.Business

1.2.2.1. Existing systems integration

1.2.2.2. Card processing

1.2.2.3. Custom reporting

1.2.3.Human Resources

1.2.3.1. Internal Resource identification

1.2.3.2. Vendor resource identification

1.3. Acquisition

1.3.1.Hardware and peripherals

1.3.1.1. Vendor selection

1.3.1.2. Purchase

1.3.1.3. Shipping

1.3.2.Software

1.3.2.1. Allocate application development resource

1.3.2.2. Purchase other support software

1.4. Implementation

1.4.1. Hardware

1.4.1.1. Rack space allocation

1.4.2.Software

1.4.2.1. Platform

1.4.2.2. POS

1.4.2.3. Supporting

1.4.3.Communications

1.4.3.1. Cabling

1.4.3.2. Core routing and switching

1.4.3.3. Internet connectivity

1.4.3.4. Phone connectivity

1.4.3.5. Connectivity testing

1.4.4.Preliminary testing

1.5. Inventory

1.5.1.Process management workflow

1.5.2.SKU scanning

1.5.2.1. Gift cards

1.5.2.2. Gen Merchandise

1.6. Application deployment

1.6.1.System Integration

1.6.1.1. Inventory system

1.6.1.2. Accounting system

1.6.1.3. Card processing

1.6.1.3.1. Merchant account

1.6.2.System configuration

1.6.2.1. User accounts

1.6.2.2. Reporting

1.6.2.3. Data exports

1.6.2.4. Backup schedule

1.6.3.Initial Testing

1.6.4.Operations Handover

1.6.4.1. Vendor support details

1.7. Implementation Testing

1.7.1.Test Plan

1.7.2.Acquire test cards

1.7.3.UAT

1.7.3.1. Transactions

1.7.3.2. Scanning

1.7.3.3. Card swipe

1.7.3.4. Reconciliation

1.7.4.Test Reporting

1.8. Training

1.8.1.Documentation

1.8.2.User Training