Tuesday, July 20, 2010
Internship-week6
WBS is the thing I learn recently from MBA course. WBS means work breakdown structure. Because a good WBS is easy to read, people often assume that it is also easy to write. This, however, is a false assumption, I used to deliver poor WBS before. But now I am trying to use what I learn to write accurate WBS, and it is really useful in planning, communicating and tracking the project. I and Sammy are really happy about the results. We followed those three criteria for a successful WBS. First, the WBS must be broken down starting at the top. we even put very little small things into WBS. Second, work packages must add up to the summary task. We used to omit necessary tasks, but now we are trying to avoid this problem by taking extra care when adding up the products of all the work packages below any summary task. Third, Each summary task and work package must be named as an activity that produces a product, giving each task a descriptive name that includes a stron very-the activity-and a strong noun. I and Sammy applied those rules to our work, and we find wer are in absolut control of our each project, break the project into small, meaningful, manageable units of work.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment