Lean Applications in Product Development-A Synchronized Process
For concurrent engineering to be effective, it is important that each ensuing function should utilize the established information from the preceding function as and when it becomes available. The development teams should, therefore, work with the part of the design data (requirements) that is unlikely to change and try to check wastage and save time. Each function’s processes should be designed in a manner which moves forward and simultaneously builds established data around as and when it becomes available. This practice is referred to as simultaneous execution. You can now see how lean is creating an offshoot of a pro-lean subculture, and it is emerging from within the Agile project and development community. Classic Agile Methodology bases a large part of its development using concurrent engineering, building and testing at the same time in small teams or concurrently developing usable code with every iteration. Iterations are built on 2-week sprints so after each sprint you have usable code to display to the business, and when this works it gives the business a “warm and fuzzy” about the project and the methodology that you have deployed to complete the IT project.