During academic year 2006–07, a family of four closely related multi-disciplinary senior design projects was initiated. Each project team consisted of eight undergraduate students. The family of projects has continued during the academic year 2007–08, with three additional design projects comprised of 19 students. The intent of the family of design projects is two-fold. The first objective is to introduce students to the concept of designing a product within the context of a family of closely related products, similar to the approach that a corporation may use in its strategic approach to the marketplace. The second objective is to provide an open-source, open-architecture, modular, and scalable robotic vehicle platform usable by a wide range of researchers within the Kate Gleason College of Engineering looking for a vehicle to position cameras, sensors in networks, and for other data-gathering tasks. Students were given the challenge to design and manufacture a platform based on a single design, scalable across four payload orders of magnitude from 1kg to 1,000kg. The 10kg and 100kg variants were studied in AY2006–07, and the 1kg variant was introduced in AY2007–08. The largest, 1,000kg, planned for the future, will be about the size of a Honda Civic, so safety and fail-safe engineering is important. Each project in the family is expected to build on the technology used and lessons learned from prior and concurrent projects, much like the “next model year” in the auto industry, and information sharing requirements among concurrent engineering teams. Hardware, software, and design methods are reused whenever possible, and students are expected to develop their subsystem in the context of an evolutionary platform design. In this manner, the end-product from one design group becomes the starting point for another team. Responsibilities overlap so teams must work cooperatively, which mimics the industrial environment. Starting times on various projects may be staggered, and students must deal with documentation sharing issues, and preservation of design intent across multiple-project teams and academic terms. The paper will discuss the current status of the program, the lessons learned to-date, and future plans for the program.