Project Organizational Design Summary and WBS For this assignment, you will the
ID: 3828040 • Letter: P
Question
Project Organizational Design Summary and WBS
For this assignment, you will the evaluate different types of project management organizations, describe the role and responsibilities of a project manager, and analyze various aspects of team collaboration and stakeholder influences. Additionally, you will develop a Work Breakdown Structure (WBS).
Part 1: Project Organizational Design Summary Analysis
Develop a 4–5-page summary, including the following:
Describe the project management organizational types and which one best describes the business or IT project that you selected in Part 1 of Assignment 2.
Describe the project management performance metrics associated with your organization type.
Describe the role and responsibilities of a project manager.
Evaluate the aspects of project team dynamics, project communication techniques, and stakeholder influences.
Evaluate project management software.
Part 2: Work Breakdown Structure (WBS)
Develop a Work Breakdown Structure (WBS) based on your selected business or IT project.
WBS should include, at a minimum, four levels.
Reminder: Examples of business or IT project types:
Examples of business projects include (but are not limited to): planning a company event, planning a traditional wedding, construction, or other projects with a business-oriented focus.
Examples of IT projects include (but are not limited to): ERP implementation, Web site development, WAN design, IT security, et cetera.
Additional Requirements
Written communication: Ensure written communication is free of errors that detract from the overall message.
Number of resources: At least 3 current scholarly or professional resources for Part 1.
Formatting: Resources and citations are formatted according to current APA guidelines for style and formatting.
Length: 4–5 double-spaced pages for Part 1. WBS requires, at a minimum, four levels.
Include a title page and reference page.
Explanation / Answer
A work breakdown structure (WBS) is a key project deliverable that organizes the team's work into manageable sections. The Project Management Body of Knowledge (PMBOK) defines the work breakdown structure as a "deliverable oriented hierarchical decomposition of the work to be executed by the project team." The work breakdown structure visually defines the scope into manageable chunks that a project team can understand, as each level of the work breakdown structure provides further definition and detail. Figure 1(below) depicts a sample work breakdown structure with three levels defined.The project team creates the project work breakdown structure by identifying the major functional deliverables and subdividing those deliverables into smaller systems and sub-deliverables. These sub-deliverables are further decomposed until a single person can be assigned. At this level, the specific work packages required to produce the sub- deliverable are identified and grouped together. The work package represents the list of tasks or "to-dos" to produce the specific unit of work. If you've seen detailed project schedules, then you'll recognize the tasks under the work package as the "stuff" people need to complete by a specific time and within a specific level of effort.
Project work breakdown structures can also be used to identify potential risks in a given project. If a work breakdown structure has a branch that is not well defined then it represents a scope definition risk. These risks should be tracked in a project log and reviewed as the project executes. By integrating the work breakdown structure with an organizational breakdown structure, the project manager can also identify communication points and formulate a communication plan across the project organization.
When a project is falling behind, referring the work breakdown structure will quickly identify the major deliverables impacted by a failing work package or late sub- deliverable. The work breakdown structure can also be color coded to represent sub- deliverable status. Assigning colors of red for late, yellow for at risk, green for on-target, and blue for completed deliverables is an effective way to produce a heat-map of project progress and draw management's attention to key areas of the work breakdown structure.
The following guidelines should be considered when creating a work breakdown structure:
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.