A work breakdown structure (WBS) is a conceptual framework within the project management setup that identifies the main tasks to be performed, their predecessors, and likely duration. This work breakdown structure is drawn on the assumption that some tasks will proceed sequentially, whereas others will be carried out concurrently. The framework, however, has a minimal allowance for iterative processes. Based on this understanding, we can infer that the work breakdown structure as a traditional project management tool will not work with XP. This is because the XP approach is mainly an iterative approach where the developer codes and tests applications as they are built incorporating the most current user requirements being submitted.
Moreover, for XP, the developers will produce the dichotomy for the test units, which are mostly automated. This implies that the duration of producing a component will depend on the developer’s ability and may not be predefined before the project commences, as is the case when using the work breakdown structure. The customers, on the other hand, offer broader definitions and criteria for acceptance testing. These are adjusted according to the user stories, which are the user requirements through an iterative process. On the other hand, a work breakdown structure is a rigid framework, and its structure may not allow for iterations, which makes it unsuitable as an application with XP. The XP approach focuses more on the programmers’ productivity, which is also not the case with the traditional project management tools such as a work breakdown structure.