Edudorm Facebook

WORK BREAKDOWN AND DEVELOPMENT OF INVENTORY SYSTEM PROJECT

WORK BREAKDOWN AND DEVELOPMENT OF INVENTORY SYSTEM PROJECT


Research work breakdown structures and compare one created with MS Project and one created without software.

Work breakdown structure is considered a being a key project deliverable which assist in organizing the work of a team into manageable section. It thus defines all the scope of the project into understandable manner or providing definition and clear details. Therefore, by considering the one created by MS Project, what is noted is that it starts with a sole box or just to say other graphics at the top as a way of representing the whole project (Haugan, 2002). With it, it ends up dividing them into components which their related activities (elements) which are listed under them.  This then implies that it is an efficient means.

Contrary to that, the work breakdown structures which is developed without the use of software largely depends on writing it on hardcopies/ paper. This means is not efficient in the sense that in case adjustments are to be made on the copy regarding something omitted, it will require it to be started afresh hence making it much tedious. 

Justify which work breakdown structure you prefer and support your reasons.

Work breakdown structures created with MS Project. The reason for this is because it is a faster means of coming up with the work breakdown structure. On the other hand, it easier to make adjustments with the structure if need arises as the work or project continues.

Analyze the WBS created by the private company

Let’s take an example of a private company which deals with the building of desktop computers. Therefore, in the process of building them, the work breakdown structure will be of much importance since it is the one which will dictate the manner in which the work will be executed. Thus, as a way of making the work of building the desktop computers go faster, the WBS will be used in assigning teams into various aspects of building them (Norman et al, 2008). In this way, for instance, one team will be required to work on the configuration of the chassis while the other will be dealing with the securing of the components as shown in the diagram below

 

Team 4

Software

 

Team 3

Components

 

Team 2

Mother board

 

Team 1

Chassis

 

                                                DESKTOP COMPUTERS

 

 

 

 

 

 

 

 

Reference

Haugan, G. T. (2002). Effective work breakdown structures. Vienna, Va: Management Concepts.

Norman, E. S., Brotherton, S. A., & Fried, R. T. (2008). Work breakdown structures: The foundation for project management excellence. Hoboken, N.J: John Wiley & Sons.

429 Words  1 Pages
Get in Touch

If you have any questions or suggestions, please feel free to inform us and we will gladly take care of it.

Email us at support@edudorm.com Discounts

LOGIN
Busy loading action
  Working. Please Wait...