Original post:

Breaking work into smaller tasks is a common productivity technique used to make the work more manageable and approachable. For projects, the Work Breakdown Structure (WBS) is the tool that utilizes this technique and is one of the most important projects management documents. It singlehandedly integrates scope, cost, and schedule baselines ensuring that project plans are in alignment.

Work breakdown structure (WBS) helps in breaking down a project into pieces that are attainable with the purpose of identifying and covering all required elements for the completion of a project. The process of subdivision of activities and events that compose this structure can be very complicated or sometimes very manageable. Project leaders or managers can select one of the following approaches to start a process of designing work breakdown structures. There is an analogy approach which is often used by contractors as a starting point. This approach can be very effective and simple for a consultant firm or a construction firm that does similar or closely related projects for the same client. Another approach is a top-down approach where project leaders define all components that make up the largest deliverables. This approach continues to greater details until all work is identified. This approach requires leaders of projects to be knowledgeable of all the required components of a project. The final approach is the bottom-up approach which is illustrated from our scenario. It entails the whole project management team and is very accurate in the process as the specific tasks are identified and are combined into larger activities. It can be very effective for scope and time planning as it can involve input and consensus from the entire team.

As discussed in the Kerzner text, the reasons why at levels 4-6 of the work breakdown structures may not be appropriate is because at these levels of WBS templates are the technical levels and tend to be very expensive and time-consuming. To break work down into smaller work packages, there is a necessity for more databases creating a need for more manpower time and more capital used.

The role of a functional manager is very crucial to the entire project as they help in controlling the resources, budgets, schedules, and training need for a project to complete. Without all these, the project won't continue as it doesn't have a clearance. For a project to succeed, there must be plan implementations to enable all members to a recognition of their roles and also understand their wages and their working hours.

A work breaks down structure for a project may be created as a table. Such as using office software such as word or excel. Project planners have been using automated project management software which has increased its popularity. An example of this is the Microsoft project.

Response:

Thank you for identifying the three types of directives that the project could take. Do you have a "real-world" example of where this has been applied? Something from a current or past project experience?

Please answer the response