Waste Mapping in Lean Manufacturing: PMI-ACP Agile Certification Training
Waste mapping is a major factor coming under lean manufacturing in agile project management. The lean methodologies have various guidelines based on waste identification and waste reduction. Lean methodologies propagate certain ways to identify and reduce waste in the manufacturing world. Mary Poppendieck, the writer of award winning book Lean Software Development has done host of work in terms of translating waste reduction methodologies for various software development activities.
Different forms of waste arising in Lean Manufacturing: Here are seven forms of waste that has been identified in software development by agile practitioners.
- Partially done work: Any work that started but was left out without completing can very soon lose value resulting in transforming to inducted waste. Examples of such waste can be code completed but not tested or specs written but waiting for development and so on.
- Extra processes: Within a project work there can be various extra processes that do not add any value to the customer. Such extra processes can be classified as waste. As for example: Documentation produced which are never referred or processes waiting for approval which are not at all necessary and so on.
- Extra features: Software that has features which the customer does not need and will never use. Example of extra features are reflected when the agile team tries to include features just to enhance technical coolness and not usability.
- Task switch: This is a big source of waste in lean manufacturing as software developers spend host of hours in switching from one task to another. Every time there is a context switch, there is overhead involved in getting back to the original task. This results when people are assigned to multiple projects.
- Waiting time: Valuable time spent on waiting on others too creates waste time. Such situation usually happens when there are dependencies that are not met on time or are waiting for answers, feedback or approvals to queries and ideas.
- Motion time: The effort that is required in order to communicate or move items from one location to the other results in waste. This happens usually in distributed teams as in the latter a lot of hand-offs are required.
- Defects: Defects in any project always needs correction for successful completion of the project. The time spent on defects introduced by the team is wasted. Examples of defects being the source of waste can be in the requirements or in software bugs and so on.
All these different types of waste sources in lean process should be controlled towards waste reduction and successful completion of lean development. To know more about lean methodologies and agile practices, you can join Simplilearn’s PMI-ACP training. You can also attend our agile certification classroom training in your city. Know the upcoming dates of agile certification training courses for your city.
About the On-Demand Webinar
About the Webinar