Tpm Quotes

We've searched our database for all the quotes and captions related to Tpm. Here they are! All 4 of them:

In about 1951, a quality approach called Total Productive Maintenance (TPM) came on the Japanese scene. Its focus is on maintenance rather than on production. One of the major pillars of TPM is the set of so-called 5S principles. 5S is a set of disciplines—and here I use the term “discipline” instructively. These 5S principles are in fact at the foundations of Lean—another buzzword on the Western scene, and an increasingly prominent buzzword in software circles. These principles are not an option. As Uncle Bob relates in his front matter, good software practice requires such discipline: focus, presence of mind, and thinking. It is not always just about doing, about pushing the factory equipment to produce at the optimal velocity. The 5S philosophy comprises these concepts: • Seiri, or organization (think “sort” in English). Knowing where things are—using approaches such as suitable naming—is crucial. You think naming identifiers isn’t important? Read on in the following chapters. • Seiton, or tidiness (think “systematize” in English). There is an old American saying: A place for everything, and everything in its place. A piece of code should be where you expect to find it—and, if not, you should re-factor to get it there. • Seiso, or cleaning (think “shine” in English): Keep the workplace free of hanging wires, grease, scraps, and waste. What do the authors here say about littering your code with comments and commented-out code lines that capture history or wishes for the future? Get rid of them. • Seiketsu, or standardization: The group agrees about how to keep the workplace clean. Do you think this book says anything about having a consistent coding style and set of practices within the group? Where do those standards come from? Read on. • Shutsuke, or discipline (self-discipline). This means having the discipline to follow the practices and to frequently reflect on one’s work and be willing to change.
Robert C. Martin (Clean Code: A Handbook of Agile Software Craftsmanship)
By design, flow systems have an everything-works-or-nothing-works quality which must be respected and anticipated. This means that the production team must be cross-skilled in every task (in case someone is absent or needed for another task) and that the machinery must be made 100 percent available and accurate through a series of techniques called Total Productive Maintenance (TPM). It also means that work must be rigorously standardized (by the work team, not by some remote industrial engineering group) and that employees and machines must be taught to monitor their own work through a series of techniques commonly called poka-yoke, or mistake-proofing, which make it impossible for even one defective part to be sent ahead to the next step.7
James P. Womack (Lean Thinking: Banish Waste And Create Wealth In Your Corporation)
People who are the most successful in Google will have a fierce position. They’ll argue and stress their point of view based on the data they have. But when they see new data which proves them wrong, they are ready to accept other’s point of view immediately.
Abraham Chackungal (Cracking the TPM Code: Technical Program Manager Interview Guide)
Leaders are right a lot. They have strong judgment and good instincts. They seek diverse perspectives and work to disconfirm their beliefs.
Abraham Chackungal (Cracking the TPM Code: Technical Program Manager Interview Guide)