<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<title>Selected Works</title>
<link href="https://hdl.handle.net/1721.1/70040" rel="alternate"/>
<subtitle/>
<id>https://hdl.handle.net/1721.1/70040</id>
<updated>2026-04-03T21:29:51Z</updated>
<dc:date>2026-04-03T21:29:51Z</dc:date>
<entry>
<title>Risk Management in Lean Product Development</title>
<link href="https://hdl.handle.net/1721.1/79840" rel="alternate"/>
<author>
<name>Oehmen, Josef</name>
</author>
<author>
<name>Rebentisch, Eric</name>
</author>
<id>https://hdl.handle.net/1721.1/79840</id>
<updated>2019-04-10T20:26:08Z</updated>
<published>2010-03-01T00:00:00Z</published>
<summary type="text">Risk Management in Lean Product Development
Oehmen, Josef; Rebentisch, Eric
This whitepaper summarizes 15 years of research conducted at MIT's Lean Advancement Initiative on the topic of risk management in product design and development. It discusses current challenges in risk management for product development, presents a risk management process for PD based on ISO 31000, and summarizes 10 papers published of LAI research on risk management.
</summary>
<dc:date>2010-03-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Program Management for Large Scale Engineering Programs</title>
<link href="https://hdl.handle.net/1721.1/79839" rel="alternate"/>
<author>
<name>Oehmen, Josef</name>
</author>
<author>
<name>Rebentisch, Eric</name>
</author>
<author>
<name>Kinscher, Kristian</name>
</author>
<id>https://hdl.handle.net/1721.1/79839</id>
<updated>2019-04-11T11:23:53Z</updated>
<published>2011-12-01T00:00:00Z</published>
<summary type="text">Program Management for Large Scale Engineering Programs
Oehmen, Josef; Rebentisch, Eric; Kinscher, Kristian
The goal of this whitepaper is to summarize the LAI research that applies to program management. The context of most of the research discussed in this whitepaper are large-scale engineering programs, particularly in the aerospace &amp; defense sector.&#13;
The main objective is to make a large number of LAI publications – around 120 – accessible to industry practitioners by grouping them along major program management activities. Our goal is to provide starting points for program managers, program management staff and system engineers to explore the knowledge accumulated by LAI and discover new thoughts and practical guidance for their everyday challenges.&#13;
The whitepaper begins by introducing the challenges of programs in section 4, proceeds to define program management in section 5 and then gives an overview of existing program management frameworks in section 6. In section 7, we introduce a new program management framework that is tailored towards describing the early program management phases – up to the start of production. This framework is used in section 8 to summarize the relevant LAI research.
</summary>
<dc:date>2011-12-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Waste in Lean Product Development</title>
<link href="https://hdl.handle.net/1721.1/79838" rel="alternate"/>
<author>
<name>Oehmen, Josef</name>
</author>
<author>
<name>Rebentisch, Eric</name>
</author>
<id>https://hdl.handle.net/1721.1/79838</id>
<updated>2019-04-11T11:23:53Z</updated>
<published>2010-07-01T00:00:00Z</published>
<summary type="text">Waste in Lean Product Development
Oehmen, Josef; Rebentisch, Eric
The main objective of this paper is to make the work that has been done at LAI in the area of waste in product development easily accessible to the consortium members. The focus of the discussion in this paper is therefore on past LAI work. Non-LAI work is integrated into the presentation where it is necessary to complete the picture.&#13;
The intended readership is engineers and managers in the areas of product development, product design, systems engineering and program management. The paper is also intended to provide a first overview to students and others interested in the field.&#13;
Reading this whitepaper provides a concise overview of the most important waste drivers in product development, that is, the most common project deficiencies that lead to cost and schedule overrun, as well as to performance issues. It will enable those involved in process improvement initiatives to include specific lean-related factors into their process analysis. It provides both managers and engineers with a common language and concepts to enhance the efficiency of their product development projects.
</summary>
<dc:date>2010-07-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Survey Report: Improving Integration of Program Management and Systems Engineering</title>
<link href="https://hdl.handle.net/1721.1/79681" rel="alternate"/>
<author>
<name>Conforto, Edivandro</name>
</author>
<author>
<name>Rossi, Monica</name>
</author>
<author>
<name>Rebentisch, Eric</name>
</author>
<author>
<name>Oehmen, Josef</name>
</author>
<author>
<name>Pacenza, Maria</name>
</author>
<id>https://hdl.handle.net/1721.1/79681</id>
<updated>2019-04-10T15:22:17Z</updated>
<published>2013-06-01T00:00:00Z</published>
<summary type="text">Survey Report: Improving Integration of Program Management and Systems Engineering
Conforto, Edivandro; Rossi, Monica; Rebentisch, Eric; Oehmen, Josef; Pacenza, Maria
For many years, a cultural barrier has existed between practitioners of systems engineering and of program management.  Some systems engineers and program managers have developed the mindset that their work activities are separate from each other rather than part of an organic whole.  Consequently, work often costs more, takes longer, and provides a suboptimal solution for the customer or end user.  The leaders of INCOSE and PMI believe this cultural barrier and mindset can and must be overcome. By working together, the organizations hope to foster a team approach that will benefit their members and their organizations, and ultimately the stakeholders who depend on them.  The survey findings reported in this whitepaper highlight 4 key elements to reduce unproductive tension between program managers and system engineers and support the integration of these roles: 1. Use standards from both domains; 2. Formally define the integration of the roles; 3. Conducted integrated program assessments; and 4. Share responsibilities in select key areas.
</summary>
<dc:date>2013-06-01T00:00:00Z</dc:date>
</entry>
</feed>
