At the lowest level of a WBS tree are individual work packages (WP). When first planning a project you don’t have to identify every single one of these, but you will have to by the time you’re ready to baseline your project. Progressive elaboration is the key to tackling this job of identifying WPs. The purpose of breaking down the WBS into WPs is that you will use these to produce realistic cost estimates and schedule activities for the project. You have to break the work down to this level of granularity to create these things, but it makes no sense to go further than this. The sweet spot the lies between too little and too much detail is something that is different on every project–and something that every project manager has to determine.
Did you find this post useful? Sign up here for our free email list to help ensure more like it are created. Thanks!
You can also email me directly at Mark@TheProjectManagementBlueprint.com