Project Work Breakdown Structure
(Team project)
Overview
The purpose of this Team assignment is to:
•
•
•
•
Determine the work required to build Mamma Mia’s IT system.
List all deliverable end items in the form of Summary Tasks.
Define and list sub-tasks under each Summary Task.
Produce a final WBS.
There are three parts to this assignment.
Part 1 – Team-reviewed Project Charter in Microsoft Word
In Week 2, each of your team members created a Project Charter. Your team needs only one Project
Charter. As a team, select one Charter to use for this assignment. Be sure to update it using the
assignment feedback from Week 2, the Case Study, and deliverable and task elements specified in Part 2
of this assignment. The Charter and the project WBS must align with each other.
IMPORTANT: The submission file should be named as “Group” “Team Name” “Deliverable for”
“Assignment Name”, such as – Group A Projecteers Charter for Project WBS.docx
Part 2 – Work Breakdown Structure in Microsoft Project
Re-read the following:
•
•
“How to Build Work Breakdown Structures” (Week 1 ? Reading), paying close attention to
o WBS Creation process
o Definitions
o Convention for WBS structure
o Considerations for building the WBS
o Schedule development process
o Naming Terminology
“What NOT to do in a WBS” (Week 1 ? Reading)
Before creating the WBS, open a blank project in Microsoft Project. Apply the settings from the Project
Configuration Settings section in “Project Tutorials” (Course Resources). As a team, develop and submit
a project work breakdown structure (WBS) in Microsoft Project’s .mpp format. Your WBS should include
all work necessary to complete the scope of the project, specifically including the technical IT work of
the project.
The WBS should include the project management effort as well. This is the work the Project Manager
(and team) must do to keep the project moving in the right direction. It would include such things as
team and customer meetings, briefs to the sponsor, status reports, and so on.
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 WBS Fall 2021
Page 1 of 6
Project Work Breakdown Structure
(Team project)
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 please 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
There is a lot more to the WBS than this. Do not spend too much time getting “down into the weeds”. A
good size for this class 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 your work packages.
Finally, define and list sub-tasks within each work package.
Project WBS Fall 2021
Page 2 of 6
Project Work Breakdown Structure
(Team project)
Formatting Your Project WBS
Use the Insert Column function (read about this in “Project Tutorials” ? Show the Project WBS
Numbers) so the Project WBS shows the following columns (in this order):
•
•
•
•
•
•
•
•
•
•
•
•
•
Indicators (column shows
Task Mode
Constraint Type
Constraint Date
Outline Level
WBS
Task Name
Duration
Start
Finish
Predecessors
Successors
Type
)
IMPORTANT: The submission file should be named as “Group” “Team Name” “Deliverable for”
“Assignment Name”, such as – Group A Projecteers Project File for Project WBS.mpp
Project WBS Fall 2021
Page 3 of 6
Project Work Breakdown Structure
(Team project)
Part 3. Answers to Questions in Microsoft Word
Read and think through the options and alternatives suggested by these questions before you build your
Project WBS. When your Project WBS is completed, answer the following questions, and submit them as
a Microsoft Word document. “Yes” or “No” answers with no explanations or discussions are not
appropriate answers.
1. Does the Project Schedule include everything in your team’s charter and all deliverables? If the WBS
includes tasks that were not part of the Project Charter, explain how the team determined the
additional tasks were necessary.
2. Does the WBS include project management tasks necessary to manage the project?
3. Explain the top-down and bottom-up approaches to building a WBS. Which approach did the team
decide to use and why did they make that decision?
4. Building the WBS as an outline in Word or Excel instead of Project can help team members visualize
the order of the tasks and how the tasks might decompose into lower levels. Did the team build an
outline outside of Project? If you only used Project, did the team need to rearrange tasks while
building the WBS?
5. Did the team approach the WBS graphically (like an organization chart) or tabularly (like a list or
table), or something else? Why?
6. Did the team work together to determine the major tasks or was only one team member responsible
for that? How well did it work?
Project WBS Fall 2021
Page 4 of 6
Project Work Breakdown Structure
(Team project)
Formatting Your Questions Document
•
•
•
•
•
•
•
•
•
•
•
Create an APA format title page that includes: The title of report (Questions for Project WBS),
your name, Course and Section number and date (use assignment due date); do not include
graphics or themes.
No running header required for this document.
The body of the paper should be double (or 1.5″) spaced, and no longer than 5 pages.
Answers should be formatted as normal sentences (no numbering, not a run-on sentence as
part of the question, no indenting).
Use 1″ margins on all sides.
Font should be 11-point Calibri, 11-point Arial, 10-point Lucida Sans Unicode, 12-point Times
New Roman, 11-point Georgia, or 10-point Computer Modern.
Font should remain consistent throughout the paper, i.e., not changing from one font to
another.
Use at least one external reference and one from the course content (from the class reading
content, not the assignment instructions or case study itself) with APA formatted citation and
reference. For information on general APA format and specifics related to citing from the class
content, refer to Content ? Course Resources ? Writing Resources. Resources must not use
Wikipedia, general information sites, blogs, or discussion groups.
The list of References must be its own page at the end of the document and it must be in APA
format, i.e., double spaced, .5″ hanging indent. No more than 10% of the paper may be in the
form of a direct citation from an external source. All in-text citations must appear in the
References list and all entries in the References list must be used as in-text citations.
Run Microsoft Word’s grammar/spell checker; there should be no errors in grammar, verb
tenses, pronouns, spelling, punctuation, first person usage, or contractions.
Submit your paper as a Word document, or a document that can be read in Word.
IMPORTANT: The submission file should be named as “Group” “Team Name” “Deliverable for”
“Assignment Name”, such as – Group A Projecteers Questions for Project WBS.docx
Project WBS Fall 2021
Page 5 of 6
Project Work Breakdown Structure
(Team project)
Grading Rubric
90-100%
80-89%
70-79%
60-69%
< 60% Far Above Standards Above Standards Meets Standards Below Standards Well Below Standards Criteria Team-reviewed Project Charter 5 Points 4 Points Updated Charter revised to match scope and WBS. Scope and deliverables fully updated and aligned with WBS. Scope and deliverables mostly updated and aligned with WBS. Configuration Settings Needed for producing consistent results in the Project WBS. Work Breakdown Structure WBS is decomposed to Level 4, uses Project's WBS numbering, rows are continuous, includes specified WBS elements, satisfies scope of the Project Charter. Schedule Structure No durations, resources, dependencies, or costs specified. Includes Project Start and Project Complete. Schedule Details Tasks describe work/deliverables (not a checklist) using provided naming conventions. 125 rows or less, columns reveal specified fields. No color-coding, special characters, or task names with full sentences. Questions Answers appropriately explain concepts (not yes/no). Research Use at least 2 references from academically credible sources with APA formatted citation (intext). Format Uses format provided. Includes Title Page and References Page. Project WBS Fall 2021 5 Points All configuration settings correct. 3 Points 4 Points Scope and deliverables moderately updated and aligned with WBS. 3 Points Missed 1-2 configuration settings. Missed 3-4 configuration settings. 2 Points Scope and deliverables somewhat updated and aligned with WBS. 2 Points Missed 4-5 configuration settings. 0-1 Points 5 Scope and deliverables not updated or aligned with WBS. 0-1 Points 5 Missed 5 or more configuration settings. 9-10 Points 8 Points 7 Points 6 Points 0-5 Points Correctly decomposed the schedule, no blank rows, included all specified WBS elements, all deliverables align to the Project Charter. Decomposed too little (Level 3), or too much (Level 5); included a few more (or less) than 10 Level 2 elements; most of the specified lower level elements, project management elements, and/or deliverables aligned to the Project Charter. Under-decomposition (Level 2), or over-decomposition (Level 6); missing several of the specified lower level elements, project management elements, and/or deliverables aligned to the Project Charter. Too much decomposition (beyond Level 6); only includes some of the specified lower level elements, project management elements, and/or deliverables aligned to the Project Charter. No decomposition at all (stopped at Level 1); left blank rows in the schedule, includes few of the specified lower level elements, project management elements, and/or deliverables aligned to the Project Charter. 18-20 Points 16-17 Points 14-15 Points 12-13 Points 0-11 Points No durations, resources, dependencies, or costs; First task is Project Start milestone, last task is Project Complete milestone. Applied some durations, resources, dependencies, or costs; Loaded most sub-task durations and some start/finish dates. Applied several durations, resources, dependencies, or costs; Loaded several subtask durations but also several start/finish dates. Applied many durations, resources, dependencies, or costs; Loaded some subtask durations and MSProject calculates some start/finish dates. Applied durations, resources, dependencies, and costs; Loaded all sub-task durations so MS-Project cannot calculate start/finish dates; First task is not Project Start milestone, and last task is not Project Complete milestone. 18-20 Points 16-17 Points 14-15 Points 12-13 Points 0-11 Points Row count is 125. All tasks follow correct naming convention, do not encompass multiple deliverables/actions, or use full sentences. Color-coding and special characters are not used. Columns reveal all specified fields. Row count is a little over 125. 1-2 Tasks use incorrect naming convention, use full sentences as names, or encompass multiple deliverables/actions. Columns reveal most specified fields. Row count is several more than 125. 3-4 Tasks use incorrect naming convention, use full sentences as names, or encompass multiple deliverables/actions. Columns reveal several specified fields. Row count is many more than 125. 5-6 Tasks use incorrect naming convention, use full sentences as names, or encompass multiple deliverables/actions. Columns reveal some specified fields. Row count is far more than 125. 7 or more Tasks use incorrect naming convention, use full sentences as names, or encompass multiple deliverables/actions. Specified fields not revealed. Color-coding or special characters used. Tasks read like a checklist. 18-20 Points 16-17 Points 14-15 Points 12-13 Points 0-11 Points All questions answered with appropriate explanations. 1 question not answered or does not use appropriate explanations. 2-3 questions not answered or do not use appropriate explanations. 4-5 questions not answered or do not use appropriate explanations. Questions not answered or do not use appropriate explanations. 9-10 Points 8 Points 7 Points 6 Points 0-5 Points Required references are incorporated, used effectively, and cited using APA style. References used are relevant and timely and contribute strongly to the analysis. Required references are relevant, and somewhat support the analysis. References are appropriately incorporated and cited using APA style. Only one reference is used and properly incorporated, and/or reference(s) lack correct APA style. A reference may be used, but is not properly incorporated or used, and/or is not effective or appropriate, and/or does not follow APA style for references and citations. No course content or external research incorporated, or reference listed is not cited within the text. 9-10 Points 8 Points 7 Points 6 Points 0-5 Points Well organized and easy to read. Very few or no errors in sentence structure, grammar, or spelling; doublespaced, written in third person, and presented in a professional format. Effective organization. Has few errors in sentence structure, grammar, and spelling; double-spaced, written in third person, and presented in a professional format. Some organization. May have some errors in sentence structure, grammar, and spelling; double spaced and written in third person. Not well organized, and/or contains several errors in grammar and/or spelling, and/or is not double-spaced and written in third person. Extremely poorly written, has many errors in grammar and/or spelling, or does not convey the information required. Page 6 of 6 Possible Points 10 20 20 20 10 10 1 Project Charter (Individual project) Student name University course Professor March 24, 2024 2 Executive Summary: This project charter delineates the strategy to conceptualize, construct, and deploy an information technology (IT) infrastructure for Mamma Mia's Bakery and Sandwich Shoppe. The core objective is optimizing operational workflows, refining procedures, and introducing contemporary features like point-of-sale systems, inventory monitoring, online ordering, and payment processing capabilities. The project harmonizes with Mamma's aspiration to broaden her enterprise and adapt to shifting customer preferences. Our methodology entails an intimate partnership with Mamma to grasp her needs, elucidate IT intricacies, and furnish a seamless solution (Noortman et al., 2022). This collaborative effort aims to propel Mamma's Bakery and Sandwich Shoppe into a technologically adept and customer-centric establishment. Project Scope: The project scope encompasses the comprehensive design, development, and implementation of an information technology (IT) system explicitly customized for Mamma Mia's Bakery and Sandwich Shoppe. This includes the following key components: • Integration of a robust point-of-sale system to streamline transaction processing and enhance customer checkout experience. • Implementation of advanced inventory management software to facilitate efficient tracking, monitoring, and replenishment of bakery supplies and products. • Development of a user-friendly online ordering platform, including website creation, to enable customers to place orders remotely and enhance accessibility. • Integration of secure payment processing capabilities to support various payment methods and ensure seamless customer transactions. This scope delineates the 3 essential functionalities and features that will be incorporated into the IT system to modernize operations and meet the evolving needs of Mamma Mia's Bakery and Sandwich Shoppe. Exclusions: • Networking infrastructure setup • LAN or internet installation • Comprehensive productivity software Project Objectives: 1. Implement a modern IT system to enhance operational efficiency: ? Introduce cutting-edge technology solutions tailored to the bakery's specific requirements. ? Streamline internal processes and workflows to optimize productivity and minimize manual tasks. 2. Facilitate online ordering and payment processing for customers: ? Develop a user-friendly online platform to enable customers to place orders remotely. ? Implement secure payment processing capabilities to accommodate various payment methods. 3. Enable inventory management and tracking to streamline operations: ? Integrate robust inventory management software to track and manage bakery supplies effectively. 4 ? Implement automated inventory tracking mechanisms to prevent stockouts and minimize wastage. 4. Provide training and support to Mamma Mia and her team for effective system utilization: ? Conduct comprehensive training sessions to familiarize Mamma Mia and her team with the new IT system. ? Offer ongoing technical support and assistance to ensure smooth adoption and utilization of the system. Project Management Approach: The project will follow a structured approach based on industry best practices (Bentley et al., 2000), including: Agile for iterative development and continuous feedback. The project will follow an Agile methodology, which allows for iterative development and continuous feedback loops. This method focuses on adaptability and responsiveness to changing needs, progressively allowing the project team to produce value. Breaking the project into digestible iterations or sprints enables the team to prioritize activities, address difficulties quickly, and include stakeholder feedback throughout development. This iterative approach ensures that the IT system evolves to Mamma Mia's changing needs and preferences, increasing the likelihood of success. 5 Regular communication and collaboration with stakeholders. Effective communication and engagement with stakeholders are critical for project success. The project team will keep open lines of communication with Mamma Mia, key decisionmakers, end users, and other stakeholders. Regular meetings, status updates, and progress reports will help to increase transparency and match expectations. By actively involving stakeholders throughout the project lifecycle, the team may identify possible difficulties early on, gain valuable insights, and ensure that the final deliverables fulfill stakeholders' needs and objectives. Adequate project documentation and milestone tracking ensure transparency, accountability, and traceability. The project team will record all requirements, plans, timetables, and progress. This paper acts as a reference point for all stakeholders and outlines a clear plan for project implementation. Milestones will be developed and tracked to track progress, identify dependencies, and compare performance to project goals. Regular review sessions will keep the project on track and swiftly handle any deviations from the plan. Continuous Risk Assessment and Mitigation Throughout the project lifecycle. Risk management is critical for project success, especially in complicated endeavors like IT system deployment. The project team will conduct risk assessments to identify potential threats and opportunities. Risks will be classified, assessed, and prioritized according to their significance and likelihood of occurrence. Mitigation plans will be devised and implemented to address identified risks, reduce their impact, and seize potential opportunities. By proactively managing risks throughout the project lifecycle, the team may mitigate uncertainties and boost the possibility of attaining project objectives within the defined restrictions. 6 Technical Solution: The IT system will comprise: Point-of-Sale Software with Inventory Management Integration: Integrating point-of-sale (POS) software with inventory management will transform Mamma Mia's Bakery's transaction processing. This system will allow for seamless synchronization of sales and inventory, ensuring that stock levels are automatically updated as things are sold. Staff will have real-time inventory visibility, allowing for timely replenishing and reducing the likelihood of stockouts or overstocking. Furthermore, proper inventory management improves order fulfillment and reduces discrepancies in stock counts, resulting in increased operational efficiency and customer satisfaction. Customized Online Ordering Platform for Secure Payment Processing: Creating a personalized online ordering platform will satisfy clients' desires for convenient and frictionless ordering choices. This platform will provide a user-friendly interface where clients can browse the bakery's menu, place orders, and make secure online payments. Integration with secure payment processing systems will give clients confidence in the security of their transactions. Mamma Mia's Bakery will increase its client base and revenue from online sales by providing this new ordering channel, resulting in increased profitability Centralized Database for Tracking Sales, and Inventory, market and competitiveness. Customer Information: Establishing a centralized database will serve as the backbone of the IT system, enabling 7 comprehensive tracking of sales, inventory, and customer information. This database will contain transaction data such as sales history, product information, customer profiles, and preferences. By centralizing this data, Mamma Mia's Bakery will obtain significant insights into purchasing trends, consumer behavior, and inventory turnover rates. This data-driven strategy will guide decisions such as menu planning, marketing initiatives, and inventory management methods, Resulting in increased business growth and profitability. User-Friendly Interface Accessible via Desktop and Mobile Devices: A user-friendly interface accessible via desktop and mobile devices will enhance accessibility and convenience for customers and staff members. This interface will have intuitive navigation, a visually appealing design, and responsive functioning across multiple devices. Customers will have a smooth ordering experience, whether they use desktop computers or mobile devices. Similarly, employees will benefit from having simple access to the POS system and inventory management tools from anywhere, allowing them to be more flexible and efficient in their daily operations. This user-friendly design will improve the client experience while streamlining internal operations, helping Mamma Mia's Bakery succeed. Project Estimates: Estimated Project Schedule: Milestones/Deliverables Requirements Gathering System Design Development and Testing Implementation and Training Estimated Project Costs: Forecasted Completion Date Month 1 Month 2 Months 3-4 Months 5-6 8 • Software: $30,000 • Hardware: $15,000 • Internal Resources: $10,000 • Contractor Resources: $5,000 Total ROM Budget Estimate: $40,000 Primary Stakeholder(s): Mamma Mia - Owner and Operator Project Team: i Project Manager: Clevin Wiliams ii System Designer: Andrew Johnson iii Software Developer: Buyole Umuoro iv Web Developer: Mwaniki John v Inventory Manager: Innesk Ian vi Finance Manager: Sharline Joy Project Constraints and Assumptions: Constraints: • Budget: $100,000 • Timeline: Completion within six months • Limited IT experience and staffing Assumptions: • Availability of internet connectivity • Cooperation and willingness to learn from Mamma Mia 9 Preliminary Risk Statement: Risks: • Potential budget overrun • Technical complexities during implementation • Adoption challenges due to lack of IT familiarity Mitigation Strategies: • Regular budget monitoring • Comprehensive testing and QA processes • Extensive user training and support Preliminary Communication Plan: Communication Methods: • Weekly progress meetings with Mamma Mia • Bi-weekly project status reports • Ad-hoc updates via email or phone Communication Frequency: Weekly Change Threshold: Any changes impacting cost, resources, or schedule exceeding 10% require reevaluation and a new project charter. Definition of Project Complete: Project completion is defined by the successful implementation of the IT system, including operational testing, training, and handover to Mamma Mia's Bakery and Sandwich Shoppe staff. 10 Signatures: [Clevin Wiliams (manager) sign] Date: 3/31/2024 [Mamma Mia (client) sign.] Date: 3/31/2024 11 References. Noortman, R., Lovei, P., Funk, M., Deckers, E., Wensveen, S., & Eggen, B. (2022). Breaking up data-enabled design: expanding and scaling up for the clinical context. Ai Edam, 36, e19. Bentley, L. D., Dittman, K. C., & Whitten, J. L. (2000). Systems analysis and design methods. Irwin/McGraw Hill.