Need help in building a Project WBS based on the project charter I have built and will send that below the details of the overall summary. As an example of a Project WBS just for clarity:

(Sample WBS) The wedding project

1.0 Event programming

Finalize wedding date

Develop wedding timeline

Plan ceremony and reception sequence

2.0 Guest arrangements

Compile guest list

Design, print, and send invitations

Monitor RSVPs

3.0 Catering

Select a caterer

Determine menu (appetizers, main course, desserts)

Organize beverages

4.0 Musical entertainment

Hire a band or DJ

Curate song list for ceremony and reception

5.0 Floral displays

 Here are the overall details of the assignment:

The purpose of this to:
• Determine the work required to build Mamma Mia’s IT system (Case Study).
• List all deliverable end items in the form of Summary Tasks.
• Define and list sub-tasks under each Summary Task.
• Produce a final WBS.

At this stage, the Project WBS should not include:
• Duration estimates (just leave it at the “1d” default value)
• Predecessor-successor links (aka dependencies)
• Resource data (cost, names, etc.).
Project Work Breakdown Structure

Here are some Level 2 WBS elements you should include (among others), not necessarily in the order
shown:
• IT System Design
• System Hardware
• System Software
• System Networking
• System Test
• Project Management
• System Transition

With respect to hardware, software, and networking – lower level WBS elements will deal with Orders,
Delivery, Receiving, Installation, etc. Make sure that your WBS (and .mpp file) include the following tasks
as part of your WBS. These are necessary but more tasks may well be needed. This also does not mean
that a single task will necessarily suffice for each of these. Rather, include as many tasks as it takes to do
the job, but include at least the following kinds of tasks in addition to whatever else you were
planning for your WBS:

• Ordering, and receiving hardware
• Ordering, and receiving software
• Ordering, and receiving networking
• Installing hardware
• Installing software
• Installing networking
• Managing, controlling, and monitoring the project and the team
• Project status reports
A good size for this WBS  would be no more than 10 Level 2 elements. Decompose these to Level 3
elements (or Level 4 if absolutely necessary). Remember, the lowest level elements (those with indented
sub-tasks, not indented summary tasks) will be the work packages. Finally, define and list sub-tasks within each work package.

The format for the WBS for what shows is 

Indicators (column shows )
• Task Mode
• Constraint Type
• Constraint Date
• Outline Level
• WBS
• Task Name
• Duration
• Start
• Finish
• Predecessors
• Successors
• Type

My Project Charter I have

Implementation of The Shoppe’s IT System Project Charter
Executive Summary
An integrated information technology (IT) system for The Shoppe, owned by Mamma Mia, is being designed, developed, and installed. This document outlines the project strategy and proposal for this project. With the addition of sandwiches, café seats, and bakery goods, the expansion project intends to make the bakery a more effective and user-friendly business. The suggested IT system will support online ordering, point-of-sale, inventory management, bookkeeping, and payment processing. The objectives, restrictions, team, hazards, communication strategy, change threshold, completion requirements, and finance of the project are all included in this document. Modern, user-friendly, and tailored to Mamma’s particular needs, the IT system will be.

Problem Statement
The Shoppe’s present manual and paper-based procedures are restricting its ability to expand and become more effective. By implementing an integrated IT system, Mamma Mia hopes to increase the size of her bakery, provide additional services, and improve the efficiency of her operational procedures. Significant obstacles stand in the way of attaining these objectives, including a lack of IT expertise and the absence of essential technological infrastructure.

Project Scope
The suggested IT system will support online ordering, point-of-sale, inventory management, bookkeeping, and payment processing. The objectives, restrictions, team, hazards, communication strategy, change threshold, completion requirements, and finance of the project are all included in this document. Modern, user-friendly, and tailored to Mamma’s particular needs, the IT system will be.

Project Goals: 
• Design and deploy a cutting-edge IT system that is specifically suited to The Shoppe’s needs.
• Make it possible for effective point-of-sale operations, inventory control, and bookkeeping.
• Support the processing of payments, client relationship management, and online ordering.
• For Mamma and her staff to use the system effectively, provide training and assistance.
• Maximize client happiness, revenue growth, and overall corporate efficiency.

Project Management Methodology:
A structured methodology will be used for the project’s requirements collecting, design, development, testing, training, and deployment. The system’s alignment with Mamma Mia’s business requirements will be made possible through collaboration. Risk management, milestone reviews, and regular communication will be given top priority throughout the business.

Technical Fix: The suggested IT system will have the following components:
• Terminals at the point of sale for smooth client transactions.
• For effective tracking and ordering of goods, use inventory management software.
• For reliable financial records, use bookkeeping and finance management software.
• The website has an integrated online ordering mechanism that allows for advance orders.
• Debit and credit card payment processing capabilities.
a user-friendly interface made to be as comfortable for Mamma and her staff as possible.

ROM for the anticipated project schedule and cost:
Requirements 2 weeks for gathering
Design of the system: 4 weeks
12 weeks for both development and testing
4 weeks for training and deployment
Estimated duration overall: six months
Costs of the Project (ROM) Assumed: $190,000
Licensing and software: $40,000.
Hardware Purchase: $30,000.
$15,000 for training and assistance
Resources on-site: $10,000
Budget total projected: $95,000

Significant Stakeholder(s):
Owner of The Shoppe and the main user of the IT system is Mamma Mia.

Project Roles:
Team Member 1 PMO Description
• Develops Project Plan
• Manages Stakeholders, project team, risks, project schedule, budget, and any conflicts

Team Member 2 is a UI/UX designer. Gathering and evaluating user requirements, in collaboration with product managers and engineers. Illustrating design ideas using storyboards, process flows and sitemaps.
Team Member 3 is a software developer. Design, program, build, deploy and maintain software using many different skills and tools
Team Member 4 is Hardware Engineer Research, design, develop, and test computer systems and components such as processors, circuit boards, memory devices, networks, and routers.
Team Member 5 is the training coordinator. Responsible for managing, designing, developing, coordinating and conducting all training programs
Team Member 6 Quality Assurance Analyst Conduct testing on software, websites, and other technical products to identify and resolve bugs, defects, and other potential issues

Assumptions and Project Restraints
Restraints: Budget of $100,000, deadline of six months, lack of networking, limited IT expertise—these are the restrictions.

Assumptions: Mamma’s readiness to pick up new skills and adapt to the new IT system; accessibility of necessary technological resources.

Risk Statement in Brief:
Risks: Scheduling delays for projects because of unanticipated technological difficulties.  During the system implementation, there was employee resistance to change.
Integration difficulties with outside systems, such suppliers’ and the health departments.

Risk Reduction Techniques:
To quickly resolve problems, conduct regular technical evaluations.
A thorough training program for staff members to aid changeover.
testing in-depth and working with other partners to ensure seamless integration.

Plan for Initial Communications:
Mamma Mia and weekly project status conferences.
team standups every two weeks to talk about accomplishments and problems.
Monthly project status updates that list accomplishments and approaching deadlines.
Change Threshold: Any modifications that materially affect budget, availability of resources, or timeline will need the creation of a new project charter and require Mamma Mia’s consent.

Project completion is defined as the moment the new IT system is completely operational, all staff members have received the necessary training, and the system achieves the set goals. Successful integration with suppliers, operational online ordering, payment processing, and efficient point-of-sale operations are among the completion requirements.

We, the undersigned, accept the conditions and goals stated in this project charter:
Mamma Mia (Sign) Date: _______________
Manager of the project Date: _______________

Final Remarks:
• The Shoppe will become a more contemporary and effective business thanks to the suggested IT system.
• Throughout the project, Mamma Mia’s involvement will be essential to ensure that it is in line with her requirements.
• The project team provides an affordable and user-friendly solution.
• Mamma’s budget of $100,000 and the expected budget of $95,000 are in line.
Within the allotted six months, the project will be finished.

Please study this Project Charter and offer any clarifications or comments required to move the project forward. Your participation and feedback are crucial for the new IT system’s effective deployment