Executive Summary Concurrent engineering is a method of breaking down the product progress of a large supply into smaller cycles. The reason for working iteratively is to allow more adaptability for progressions. The main preference is that this methodology allows engineers to break down the task of forming a structure into a set of more modest tasks. However, this approach provides an unorganized project management structure and sometimes requires rework of documentation. Therefore, this approach is useful when the project scope is small. Introduction Concurrent engineering is a method of breaking down the product advancement of a large supply into smaller lumps. In iterative or concurrent engineering, characteristic code is outlined, created, and tested in repeated cycles. With each emphasis, you can outline, create, and test additional features until you have prepared a fully useful programming request to send to customers. Iterative engineering looks differently in relation to an accepted waterfall system in which each period of the product advancement life cycle is "fenced". Coding does not begin until the setup of the entire programming supply is finished and a stage threshold survey has been made. Additionally, testing doesn't begin until coding is finished and has passed vital stage door surveys. The reason for working iteratively is to allow more adaptability for progressions. By the time the prerequisites and configuration of a real supply are done in the conventional system (sometimes referred to as BDUF or Big Design Up Front), there may be unexpected problems that do not emerge until improvements begin. Working iteratively, the ventur...... half of the paper......and overhead. In any case, there is a risk that insufficient documentation could lead to unnecessary duplication of effort and wasted time by creating a poorly characterized extension within an enterprise (Beck & Fowler, 2000). When to use the iterative model? • Requirements of the complete model the structure is unambiguously characterized and taken into account.• When the scope of work of the project is large.• The main needs must be characterized; however, some points of interest may develop over time. Conclusion To make Concurrent Engineering a true success, all the necessary information regarding products, parts and processes must be available at the right time. Much partially released information must be exchanged under strictly controlled conditions. If management fails to get it right, the benefits of this model can turn into some limitations.