Optimal deployment of parallel teams in new product development
Summary: Speed in product development is the thin line that determines success or failure in many fast growing industries today. Strategies like set-based concurrent engineering and parallel team deployment have been used to accelerate new product introduction by successful companies like Toyota. In this paper, these two strategies are combined to investigate the impact of generating sets of alternatives using parallel teams on the revenue generated from new product development. The trade-off between cost and speed of development due to deployment of parallel teams in product development using the multi-armed bandit (MAB) framework are also explored. Quantitative models to determine the optimum number of product development teams at different stages of development have been constructed using the Gittins Index strategy. These models are tested using hypothetical data and the results show that the higher flexibility induced quality results in higher rewards, despite the higher cost of deploying multiple teams.
- Overlapping and communication policies in product development
- Developing new products in a network with efficiency and innovation
- Balancing concurrent engineering environmental factors for improved product development performance
- Optimization and Neural Network in New Product Development
- Decisions on new product development under uncertainties
- Overlapping and communication policies in product development
- Lean holistic fuzzy methodology employing cross-functional worker teams for new product development projects: a real case study from high-tech industry
- Developing new products in a network with efficiency and innovation
- An approach to optimizing software development team size
This page was built for publication: Optimal deployment of parallel teams in new product development
Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q545873)
