Introduction
The key to a good WBS and WBS Dictionary is the engagement of project team members to comprehensively identify and discuss activities for the project. A Project Manager must ensure that all the work that needs to be accomplished for the project is contained within the WBS Dictionary and is understood by team members. All work should have clearly defined duration, resources, dependencies, and level of effort (Cleland, 1990). A Project Manager should elicit feedback from all team members to ensure that the WBS and WBS Dictionary are valid and comprehensive prior to developing the detailed schedule. The project manager, has been asked to plan the wedding for his niece.

Explain why you chose to organize your WBS in the manner you did.
There are three reasons why the WBS is setup in the manner it is for this wedding project. The first is that is helps more accurately and specifically define and organize the scope of the total project. The most common way this is done is by using a hierarchical tree structure. See figure 1 below for a graphical representation of the WBS. The figure shows two level due to size of the project. Appendix A contains the WBS showing all three levels in a tabular format as a requisite for this assignment. Each level of this structure breaks the project deliverables or objectives down to more specific and measurable chunks. The second reason for using a WBS in your projects is to help with assigning responsibilities, resource allocation, monitoring the project, and controlling the project. The WBS makes the deliverables more precise and concrete so that the project team knows exactly what has to be accomplished within each deliverable. This also allows for better estimating of cost, risk, and time because you can work from the smaller tasks back up to the level of the entire project (Cleland and King, 1983). Finally, it