Glossary

Mura | Glossary

Definition:

In Japanese, the term ‘Mura’ means unevenness or inconsistency in physical matter or human spiritual condition. In Kanban, Mura is reduced by equipping the process with the exact part, at the exact time, in the exact amount. Mura in Japanese means irregularity, lack of uniformity or non-uniformity, inequality and it is also included as a key concept in Toyota Production System (TPS). Mudra is one of the three types of waste i.e., (Muda, Mura and Muri).

In Toyota waste reduction is one of the effective to increase profitability and eliminate the less profitable resources. Toyota has adopted these three words as part of their process of product improvement program,as they are very familiar with the common Japanese word usage.

Further Reading:

The Toyota Way Fieldbook by Liker, David Meier, Liker

Outside-in Software Development | Glossary

Definition:

A quintessential project requires a successful product that is delivered as per client’s expectations. At the end, the goal is the product should reach potential customers, and become a sales reference for the customers to buy, the very next day of the product shipment. This indicates the successful project delivery.  To become successful at product development, outside-in software development can be a good approach, to start with.

Outside-in development techniques are intended to help re-create this success on every software product you work on. Out of all the Agile software development methodologies, outside–in software development takes a different approach in optimizing the software development process. Unlike other approaches, outside–in development focuses on satisfying the needs of stakeholders. The underlying theory behind this method is to create successful software with a clear understanding of the goals and motivations of the stakeholders. Ultimately, the outcome is produce a highly consumable product that exceeds the needs of a client.

Further Reading:

Outside-in Software Development: A Practical Approach to Building Successful Stakeholder Products by Carl Kessler, John Sweitzer