VU Projects Video Lectures Handouts Past Papers Quizzes Assignments & GDB border= Members Free SMS Service FB Page
VU Projects Video Lectures Handouts Past Papers Quizzes Assignment,GDB Members SMS Service FB Page

Assignment No. 04
Semester Spring 2015
Software Project Management – CS615

Graded Assignment


Total Marks: 10


Due Date: 17-08-2015




The objectives of this assignment are:

  • To understand the concepts of Work Breakdown Structure (WBS) in project management.
  • To develop basic-level WBS for a real life scenario using your own intuition.
  • To learn how to draw WBS in Microsoft Word.



  • This assignment is a Graded Assignment.
  • The assignment should be in .doc format.
  • Assignment in any format other than MS Word format will not be accepted.
  • The assignment submitted through email will not be accepted.
  • This assignment is covering Software Project Management Lectures 32 - 37.


For any query about the assignment, contact at


Question                                                                                                                                                      10 Marks

You are supposed to build product-oriented Word Breakdown Structure (WBS) for Motorbike.

Remember your WBS diagram must show activities as per level.





You are advised to study Sample:3

Work Breakdown Structure of Aircraft System at Page 256 in handouts, in Lecture 35.    





  • Ø Your answer MUST base upon your own intuition and understanding.


Best of Luck!



Views: 317


Replies to This Discussion

lets start discussion.......

A work breakdown structure (WBS) is a chart in which the critical work elements, called tasks, of a project are illustrated to portray their relationships to each other and to the project as a whole. The graphical nature of the WBS can help a project manager predict outcomes based on various scenarios, which can ensure that optimum decisions are made about whether or not to adopt suggested procedures or changes.

When creating a WBS, the project manager defines the key objectives first and then identifies the tasks required to reach those goals. A WBS takes the form of a tree diagram with the "trunk" at the top and the "branches" below. The primary requirement or objective is shown at the top, with increasingly specific details shown as the observer reads down.

When completed, a well-structured WBS resembles a flowchart in which all elements are logically connected, redundancy is avoided and no critical elements are left out. Elements can be rendered as plain text or as text within boxes. The elements at the bottom of the diagram represent tasks small enough to be easily understood and carried out. Interactions are shown as lines connecting the elements. A change in one of the critical elements may affect one or more of the others. If necessary, these lines can include arrowheads to indicate time progression or cause-and-effect.

A well-organized, detailed WBS can assist key personnel in the effective allocation of resources, project budgeting, procurement management, scheduling, quality assurance, quality control, risk management, product delivery and service oriented management.

Following are a few reasons for creating a WBS in a project:

  • Accurate and readable project organization.

  • Accurate assignment of responsibilities to the project team.

  • Indicates the project milestones and control points.

  • Helps to estimate the cost, time and risk.

  • Illustrate the project scope, so the stakeholders can have a better understanding of the same.

Is main Diagram b banni hai na?


© 2018   Created by Muhammad Anwar Tahseen.   Powered by

Badges  |  Report an Issue  |  Terms of Service