In an earlier article, we dissected the project scope and explored the work breakdown structure (WBS). The WBS is the disaggregation of the scope into the work products that are required to meet the defined scope. Now, we are going explore setting about doing the work, from a schedule, or perhaps we will not even build a schedule.

Vehicles have become increasingly electrical over the years. This is not just power electronics, but also sensor data, communications and many other coordinated electrical signals. For aircraft or commercial vehicles, wire harnesses can be even more complex with hundreds of interconnection points.

The fundamental start of any project is a scope of work document, which specifies what we want the project to achieve. The project scope may start out broadly described based upon business objectives, but it will become increasingly detailed over time.

Raptor Performance in Concord, NC, designs and manufactures custom electronics for racing motorcycles and automobiles. The company's products are not for hobbyists, these are professional-grade parts.

When I first started my engineering career, I did not know much about configuration management. In fact, my introduction to configuration management was more about what happens when it is missing.

In my first job after I received my engineering degree, I was designing hardware and writing software for embedded products for industrial applications. I had a simulator for the microcontroller.

Despite a persistent and incremental march toward automation, people are still necessary for much of manufacturing. Perhaps that will always be true for certain segments.

Project quality and product quality are different things, but they are inextricably linked—or they should be. It is possible for a project to seem successful and deliver the anticipated result, only to find out later the product is not what was expected.