Computer Science Question

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