This link has been bookmarked by 21 people . It was first bookmarked on 30 Mar 2008, by Ashok Srinivaspur.
-
16 Feb 14
-
27 Sep 12
-
The first is that is helps more accurately and specifically define and organise the scope of the total project
-
Each level of this structure breaks the project deliverables or objectives down to more specific and measurable chunks
-
to help with assigning responsibilities, resource allocation, monitoring the project, and controlling the project
-
This also allows for better estimating of cost, risk, and time because you can work from the smaller tasks back up to the level of the entire project
-
it allows you double check all the deliverables' specifics with the stakeholders and make sure there is nothing missing or overlapping
-
-
16 Jun 12
-
08 Jun 12
-
06 Sep 11
-
that is helps more accurately and specifically define and organise the scope of the total project.
-
first is
-
The second reason for using a WBS in your projects is to help with assigning responsibilities, resource allocation, monitoring the project, and controlling the project.
-
Finally, it allows you double check all the deliverables' specifics with the stakeholders and make sure there is nothing missing or overlapping.
-
-
18 Mar 11
-
25 Feb 11
-
15 Nov 10
-
05 Oct 09
-
you must be careful to not get too detailed.
-
It is NOT a list of specific activities and tasks used to accomplish the deliverables. How the work is completed (tasks and activities) can vary and change throughout the project, but deliverables cannot without a change request, so you do not want to list activities and tasks in the WBS.
-
project plan or schedule.
-
-
30 Mar 09
-
22 Oct 08
-
09 Apr 08
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.