icon

Usetutoringspotscode to get 8% OFF on your first order!

Work Breakdown Structure

Project description
Regarding Work Breakdown Structure, you need to create a level 3 WBS for the given case study, which means that we want a block structure similar to the one presented on page 9 of the Work Breakdown Structure lecture notes (Module 4 – Topic 4). Each “part” constitutes a subsystem of your overall system. Thus, you have to name your subsystems the way that I showed in class. Also, as I mentioned in class, you have to explicitly write down the % work that each system represents in order to show the 100% Representation Rule.

As far as Functional Block Diagram is concerned, you need to pick two functional requirements, and then in a block form you have to provide the sub-functions that are required in order to achieve the task associated with each requirement. So, you need to replicate the sample Functional Block Diagram (under Module 4 – Topic 6), and modify it based on the given case study.

You can leave a response, or trackback from your own site.

Leave a Reply

Work breakdown structure

Work breakdown structure
Paper details:
: Work Breakdown Structure
According to the PMBOK® Guide, “the WBS is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team, to accomplish the project objectives and create the required deliverables.” In other words, it lists the project’s deliverables and work packages. For this week, you will create a work breakdown structure (WBS) for the project you selected during Week 1.
Remember that the WBS starts with your major deliverables (that you stated in your scope management plan) at the highest level. The lower levels have the work package required to complete those deliverables. Review the textbook (and the PMBOK® Guide, if you have it) for some suggestions on how to create a WBS. From your work breakdown structure, develop a project task list with dependencies and add durations, using MS Project.
Develop the Work Breakdown Structure
• Your WBS should have a minimum of 100–150 line items in MS Project and be three levels deep.
• Make sure to use verb-object task names (for example, “Develop software”).
• Enter tasks in MS Project.
• Create the predecessor relationships.
• DO NOT LINK SUMMARY TASKS OR ASSIGN RESOURCES!
Deliverables for Week 4:
• Statement of Participation and status update
The MS Project file (.mpp) saved from the Tracking Gantt chart screen

PLACE THIS ORDER OR A SIMIRAL ONE AND GET AN AMAZING DISCOUNT):-

You can leave a response, or trackback from your own site.

Leave a Reply

Powered by WordPress | Designed by: Premium WordPress Themes | Thanks to Themes Gallery, Bromoney and Wordpress Themes