Concurrent engineering
Description
Unlike sequential engineering, where phases follow one another in strictly consecutive order, concurrent engineering overlaps the phases of the life cycle: while one part of the system is being designed, another is already under construction and another is being tested. This reduces overall development time and makes it possible to detect integration problems earlier.
Unlike agility, the quality of the result in concurrent engineering is based on the quality of the engineering processes used, rather than on people's tacit knowledge. It is therefore an evolutionary management approach rooted in process engineering.
Relationship with agility
Concurrent engineering occupies an intermediate position on the spectrum between sequential engineering (fully predictive and sequential) and agility (evolutionary and people-centered). It shares with agility the principle of overlapping phases and the continuous delivery of increments, but it maintains the emphasis on engineering processes as the guarantor of quality.
Frameworks such as the Unified Process (UP) and its variants are examples of methodologies based on concurrent engineering.
Common mistake
Confusing concurrent engineering with agility. They are different approaches within evolutionary management. Concurrent engineering bases quality on processes; agility bases it on people and their tacit knowledge. A team can do concurrent development without being agile: if its processes are rigid and collaboration with the customer is limited, running phases in parallel does not make the project agile.
See also
Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.