WBS TIP: Headers...What's right for me?

Mook

Mr. Manager
Staff member
Admin
May 23, 2007
207,174
118,999
Elgin
Real Name
Mike
With all of the headers available on the market today what's the right setup for you? Exhaust system components should be chosen with care as they can make or break your track times. Read on for the skinny on the various brands of headers and what's best for you. As these cars continue to find their place in a large aftermarket world more and more options begin to open up. While three years ago there were generally only two brands of headers considered acceptable we now have more selection: more brands, more sizes, more confusion.

There are several variables to consider when buying a header kit. Some are obvious such as name brand, quality, warranty and others not so obvious. What primary size is right for my setup? What collector size is right for my setup? Is one "kit" more complete than another? We hope to take the confusion out of your header purchase with this article. Grab a bag of popcorn and sit in your favorite E-Z chair while we educate you on the various header setups available for your 3800 powered vehicle.

To continue reading, please use the following link

http://www.wbodystore.com/grandprix....html?osCsid=119c7b57a0983dfe91f486146c07f483

sigpic.jpg
 

GLIKENNY

Hooligan
Oct 7, 2008
815
4
Darien, Illinois
Real Name
Kenny
A Work Breakdown Structure (WBS) is the best way to understand the detailed work of the project when you have to build a schedule from scratch. It's used to break the project down into the major phases, deliverables, and work components that will be built by the project. These work components can then be broken down into the activities that are required to build them. The WBS is not the same as the final schedule (which requires sequencing, resources, estimated effort, estimated duration, etc.)

Use the following five tips when building your work breakdown structure.
Create a WBS dictionary for large projects

Normally you wouldn't need a WBS dictionary, but if your WBS has hundreds (or thousands) of detailed activities, there may just be too much to keep track of by hand. In this case, it might make sense to place all of the important information in a WBS dictionary. The dictionary helps keep track of all of the summary and detailed activities, including a short description, the WBS numeric identifier (1.1, 1.1.1, 1.1.2, etc.) and the estimated effort. If you enter your WBS dictionary into a specialized tool, the tool can also help to keep track of changes to the WBS as well.
Use the summary activities as milestones

Your WBS should contain both detail and summary activities. (A summary activity is one that is broken down further. A detailed activity is one that is not broken down further.) Although a schedule usually includes only detailed activities, it makes sense to include the summary activities as milestones (markers signifying that a deliverable or set of deliverables is complete). A summary activity can be used as a milestone since it would indicate that all of the underlying detailed work has been completed.
Break activities into two or more detailed activities.

I've seen teams that break one activity in the WBS into only one activity at the next level. In my opinion, this doesn't make sense because then the detailed activity represents the same work as the prior summary activity. This doesn't buy you anything.
Make the final detailed activities action oriented

The detailed activities on your WBS (the ones that are not broken down further) are ultimately moved to your schedule. For that reason, it's easier if the detailed activities in your WBS are action oriented – just as activities in your schedule would be. For example instead of describing a detailed WBS activity as ""meeting," you should state it as "schedule a weekly meeting." Instead of having a WBS detailed activity for "Testing Plan," you should state it instead as "Create Testing Plan." In this way, the detailed activities can be moved to the schedule with a minimum of wording changes.
Don't place requirements on the WBS

If you place a deliverable on your WBS, you can break this deliverable down into the activities that are required to create it. You don't break a deliverable down into the requirements that describe it. Requirements do not belong on a WBS. Only deliverables and activities belong on the WBS.

Using these techniques will save you time and rework on your next WBS.
________________
Homeowners Insurance Quotes
adoption lawyers in knoxville

what does this have to do with headers??
 
Old Thread: Hello . There have been no replies in this thread for 90 days.
Content in this thread may no longer be relevant. Consider starting a new thread to get fresh replies.

Thread Info