Work Breakdown Structure Case Study

817 Words2 Pages

In this case study, the work breakdown structure is classified as a waterfall methodology where it is more rigid whereas eXtreme programming (XP) would be considered under the agile approach. The work breakdown structure (WBS) is a hierarchical structure that outlines tasks needed to deliver the product or service.

This traditional project management tool can provide many key benefits for Sabre because they have recently relied on a large modelling software package to help their company make flight schedules more profitable. When the WBS is used accurately,
However, the WBS is difficult to manage due to the rigidity of the model as each phase has specific deliverables and review processes and a schedule can be set with deadlines for each …show more content…

For example, XP requires the act of including small teams, applying the use of simple codes, reviewing the code frequently which will allow it to be tested and will only require working on XP for 4 hours per week.

Therefore it is best that Sabre shouldn’t use work breakdown structure when working on their latest project but can consider to use the work breakdown structure in the future. Sabre has already adopted XP into their business and has claimed that XP has dramatically improved the quality and productivity of its 300 developers. Releases are another important aspect which work breakdown structure cannot apply because releases can only be tested using XP approach which will allow developers to test, prioritize the application’s most important features.

Large or complex projects in big company often require some sort of leadership. In this case, by introducing traditional project management tools are obviously important for project leaders like Kent Black since the methods and tools that project leaders use can be helpful for …show more content…

Kent Beck, the project leader will find using the WBS to make complex projects more manageable as it is designed to help break down projects into manageable chunks that can be effectively estimated and supervised. By creating a WBS include several benefits. For example it can help assist with accurate project company, helps with assigning responsibilities, shows the control points, project milestones, and allows for more accurate estimation of the triple constraint (cost, risk, and time) therefore helping to explain the project scope to stakeholders.

Work breakdown structure can be used in XP because XP is more focus to planning in building work breakdown structure. WBS levels higher than in traditional management.
WBS on XP focuses on the function to be made compared to share duties in accordance with the responsibilities of the roles in the project. In addition WBS in XP also always perform acceptance test is always updated, level by level until the details, rather than planning everything at the

Open Document