As you have learnt about Work Breakdown Structure (WBS) in this course, on the basis of your knowledge, can WBS be considered as a plan/schedule? Justify your answer with solid reasons.
yes, WBS be considered as a plan/schedule?
Reasons:
Using a WBS provides a number of benefits to the management and to the
development teams.
First, it gives the management an idea about the size and complexity of the
project.
Second, it helps in planning, scheduling, and monitoring a project realistically.
This is possible because all the tasks in the project can be preformed measurable
targets for each task.
To aid planning, scheduling, and monitoring a project, you can use tools such as:
– Program Evaluation and Review Techniques (PERT)
– Critical Path Method (CPM)
– Timeline charts
– Gantt charts
The WBS is commonly used at the beginning of a project for defining project
scope, organizing Gantt schedules and estimating costs.
It lives on, throughout the project, in the project schedule and often is the main
path for reporting project costs.
WBS is related to planning and scheduling a project
It is a functional decomposition of the tasks of the project.
Software Project Management (CS615)
It starts with the end objective required and successively subdividing it into
manageable components in terms of size and complexity of:
– Program,
– Project,
– System,
– Subsystem,
– Components,
– tasks, subtasks, and
– work elements
get the idea and post.
don't copy paste , just get the idea and write in your own words.
reference handouts page number 241, 242
