100%(9)9 out of 9 people found this document helpful
This preview shows page 1 - 2 out of 8 pages.
WBS DictionaryWBS CodeTask NameResource to Complete the Task11 Overall Project21.1 Project Management31.1.1 Manage ProjectChris Johnson (Project Manager)12741.2 System Requirements51.2.1861.2.24571.2.3Rick Burke (Infrasructure Lead)681.2.4155, 691.2.5Rick Burke (Infrasructure Lead)27, 8101.3Software Requirements111.3.15, 6, 8184.108.40.206Capture Customer ProfileRyan Neff (Functional Lead)4220.127.116.11Ryan Neff (Functional Lead)618.104.22.168Ryan Neff (Functional Lead)31322.214.171.124Taking PaymentsStacy Lyle (Functional Analyst)6126.96.36.199Submit OrderRyan Neff (Functional Lead)412,13, 14, 15188.8.131.52Ryan Neff (Functional Lead)316181.3.2Create Data RequirementsStacy Lyle (Functional Analyst)312, 13191.3.3Stacy Lyle (Functional Analyst)7201.3.4Stacy Lyle (Functional Analyst)4211.4Detailed Design10The WBS dictionary contains all the details of the WBS necessary to successfully complete the project. Most importantly, it contains a definition of each work package, which can be thought of as a mini scope statement. Resources on the project will look at the WBS dictionary to determine the scope of the work package they have been assigned, so it is important to be clear when writing the definition. Most WBS dictionaries contain more information than we show in our sample. These things usually include Level of Effort, Cost Control Numbers, Resource Assignments, and Responsibility Assignments, just to name a few.