Lean integration

Last updated

Lean integration is a management system that emphasizes creating value for customers, continuous improvement, and eliminating waste as a sustainable data integration and system integration practice. Lean integration has parallels with other lean disciplines such as lean manufacturing, lean IT, and lean software development. It is a specialized collection of tools and techniques that address the unique challenges associated with seamlessly combining information and processes from systems that were independently developed, are based on incompatible data models, and remain independently managed, to achieve a cohesive holistic operation.

Contents

History

Lean integration was first introduced by John Schmidt in a series of blog articles starting in January 2009 entitled 10 Weeks To Lean Integration. [1] This was followed by a white paper [2] on the topic in April 2009 and the book Lean Integration, An Integration Factory Approach to Business Agility [3] in May 2010.

Overview

Lean integration builds on the same set of principles that were developed for lean manufacturing and lean software development which is based on the Toyota Production System. Integration solutions can be broadly categorized as either Process Integration or Data Integration.

The book [3] is based on the premise that Integration is an ongoing activity and not a one-time activity; therefore integration should be viewed as a long term strategy for an organization. John Schmidt and David Lyle initially articulated in their book the reasons for maintaining an efficient and sustainable integration team. Lean integration as an integration approach must be sustainable and holistic unlike other integration approaches that either tackle only a part of the problem or tackle the problem for a short period of time. Lean integration drives elimination of waste by adopting reusable elements, high automation and quality improvements. Lean is a data-driven, fact-based methodology that relies on metrics to ensure that the quality and performance are maintained at a high level.

An organizational focus is required for the implementation of lean integration principles. The predominant organizational model is the Integration Competency Center which may be structured as a central group or a more loosely coupled federated team.

Lean integration principles

The principles of Lean Integration may at first glance appear similar to that of Six Sigma but there are some very clear differences between them. Six-Sigma is an analytical technique that focuses on quality and reduction of defects while Lean is a management system that focuses on delivering value to the end customer by continuously improving value delivery processes. Lean provides a robust framework that facilitates improving efficiency and effectiveness by focusing on critical customer requirements.

As mentioned in lean integration there are seven core lean integration principles vital for deriving significant and sustainable business benefits. They are as below:

  1. Focus on the customer and eliminate waste: Waste elimination should be viewed from the customer perspective and all activities that do not add value to the customer needs to be looked at closely and eliminated or reduced. In an integration context, the customer is often an internal sponsor or group within an organization that uses, benefits from, or pays for, the integrated capabilities.
  2. Continuously improve: A data driven cycle of hypothesis-validation-implementation should be used to drive innovation and continuously improve the end-to-end process. Adopting and institutionalizing lessons learned and sustaining integration knowledge are related concepts that assist in the establishment of this principle.
  3. Empower the team: Creating cross-functional teams and sharing commitments across individuals empower the teams and individuals who have a clear understanding of their roles and the needs of their customers. The team is also provided the support by senior management to innovate and try new ideas without fear of failure.
  4. Optimize the whole: Adopt a big-picture perspective of the end-to-end process and optimize the whole to maximize the customer value. This may at times require performing individual steps and activities that appear to be sub-optimal when viewed in isolation, but aid in streamlining the end-to-end process.
  5. Plan for change: Application of mass customization techniques like leveraging automated tools, structured processes, and reusable and parameterized integration elements leads to reduction in cost and time in both the build and run stages of the integration life-cycle. Another key technique is a middleware services layer that presents applications with enduring abstractions of data through standardized interfaces, allowing the underlying data structures to change without necessarily impacting the dependent applications.
  6. Automate processes: Automation of tasks increases the ability to respond to large integration projects as effectively as small changes. In its ultimate form, automation eliminates integration dependencies from the critical implementation path of projects.
  7. Build quality in : Process excellence is emphasized and quality is built in rather than inspected in. A key metric for this principle is First Time Through (FTT) percentage which is a measure of the number of times an end-to-end process is executed without having to do any rework or repeat any of the steps.

Benefits of lean integration

The Lean integration practices transforms integration from an art into a science, a repeatable and teachable methodology that shifts the focus from integration as a point-in-time activity to integration as a sustainable activity that enables organizational agility. Once an organization adopts the integration as a science it enhances the organization’s ability to change rapidly without comprising on the IT risk or quality thereby transforming the organization into an agile data driven enterprise. The following are the advantages derived by adopting the lean integration practices:

  1. Efficiency: typical improvements are in the scale of 50% labor productivity improvements and 90% lead-time reduction through continuous efforts to eliminate waste.
  2. Agility: Reusable components, highly automated processes and self-service delivery models improve the agility of the organization.
  3. Data quality: quality and reliability of data is enhanced and data becomes a real asset.
  4. Governance: metrics are established that drive continuous improvement.
  5. Innovation: innovation is facilitated by using fact-based approach.
  6. Staff Morale: IT staff is kept engaged with high morale driving bottom-up improvements.

See also

Related Research Articles

The Toyota Production System (TPS) is an integrated socio-technical system, developed by Toyota, that comprises its management philosophy and practices. The TPS is a management system that organizes manufacturing and logistics for the automobile manufacturer, including interaction with suppliers and customers. The system is a major precursor of the more generic "lean manufacturing". Taiichi Ohno and Eiji Toyoda, Japanese industrial engineers, developed the system between 1948 and 1975.

A business process, business method or business function is a collection of related, structured activities or tasks performed by people or equipment in which a specific sequence produces a service or product for a particular customer or customers. Business processes occur at all organizational levels and may or may not be visible to the customers. A business process may often be visualized (modeled) as a flowchart of a sequence of activities with interleaving decision points or as a process matrix of a sequence of activities with relevance rules based on data in the process. The benefits of using business processes include improved customer satisfaction and improved agility for reacting to rapid market change. Process-oriented organizations break down the barriers of structural departments and try to avoid functional silos.

In software development, agile practices include requirements discovery and solutions improvement through the collaborative effort of self-organizing and cross-functional teams with their customer(s)/end user(s), Popularized in the 2001 Manifesto for Agile Software Development, these values and principles were derived from and underpin a broad range of software development frameworks, including Scrum and Kanban.

Quality management ensures that an organization, product or service consistently functions well. It has four main components: quality planning, quality assurance, quality control and quality improvement. Quality management is focused not only on product and service quality, but also on the means to achieve it. Quality management, therefore, uses quality assurance and control of processes as well as products to achieve more consistent quality. Quality control is also part of quality management. What a customer wants and is willing to pay for it, determines quality. It is a written or unwritten commitment to a known or unknown consumer in the market. Quality can be defined as how well the product performs its intended function.

Agile manufacturing is a term applied to an organization that has created the processes, tools, and training to enable it to respond quickly to customer needs and market changes while still controlling costs and quality. It is mostly related to lean manufacturing.

Lean software development is a translation of lean manufacturing principles and practices to the software development domain. Adapted from the Toyota Production System, it is emerging with the support of a pro-lean subculture within the agile community. Lean offers a solid conceptual framework, values and principles, as well as good practices, derived from experience, that support agile organizations.

Lean thinking is a management framework made up of a philosophy, practices and principles which aim to help practitioners improve efficiency and the quality of work. Lean thinking encourages whole organisation participation. The goal is to organise human activities to deliver more benefits to society and value to individuals while eliminating waste.

Lean government refers to the application of Lean Manufacturing principles and methods to both identify and then implement the most efficient, value added way to provide government services. Government agencies have found that when Lean is implemented, they see an improved understanding of how their own processes work, that it facilitates the quick identification and implementation of improvements and that it builds a culture of continuous improvement.

Muda is a Japanese word meaning "futility", "uselessness", or "wastefulness", and is a key concept in lean process thinking such as in the Toyota Production System (TPS), denoting one of three types of deviation from optimal allocation of resources. The other types are known by the Japanese terms mura ("unevenness") and muri ("overload"). Waste in this context refers to the wasting of time or resources rather than wasteful by-products and should not be confused with Waste reduction.

The concept of operational excellence was first introduced in the early 1970s by Dr. Joseph M. Juran while teaching Japanese business leaders how to improve quality. It was formalized in the United States in the 1980s in response to "the crisis" among large companies whose market share was shrinking due to quality goods imported from Japan.

<span class="mw-page-title-main">Value-stream mapping</span> Lean-management method for analyzing the current state and designing a future state

Value-stream mapping, also known as material- and information-flow mapping, is a lean-management method for analyzing the current state and designing a future state for the series of events that take a product or service from the beginning of the specific process until it reaches the customer. A value stream map is a visual tool that displays all critical steps in a specific process and easily quantifies the time and volume taken at each stage. Value stream maps show the flow of both materials and information as they progress through the process.

An integration competency center (ICC), sometimes referred to as an integration center of excellence (COE), is a shared service function providing methodical data integration, system integration, or enterprise application integration within organizations, particularly large corporations and public sector institutions.

A lean laboratory is one which is focused on processes, procedures, and infrastructure that deliver results in the most efficient way in terms of cost, speed, or both. Lean laboratory is a management and organization process derived from the concept of lean manufacturing and the Toyota Production System (TPS). The goal of a lean laboratory is to reduce resource usage and costs while improving productivity, staff morale, and laboratory-driven outcomes.

Lean IT is the extension of lean manufacturing and lean services principles to the development and management of information technology (IT) products and services. Its central concern, applied in the context of IT, is the elimination of waste, where waste is work that adds no value to a product or service.

Business process management (BPM) is the discipline in which people use various methods to discover, model, analyze, measure, improve, optimize, and automate business processes. Any combination of methods used to manage a company's business processes is BPM. Processes can be structured and repeatable or unstructured and variable. Though not required, enabling technologies are often used with BPM.

Lean enterprise is a practice focused on value creation for the end customer with minimal waste and processes. The term has historically been associated with lean manufacturing and Six Sigma due to lean principles being popularized by Toyota in the automobile manufacturing industry and subsequently the electronics and internet software industries.

Continuous testing is the process of executing automated tests as part of the software delivery pipeline to obtain immediate feedback on the business risks associated with a software release candidate. Continuous testing was originally proposed as a way of reducing waiting time for feedback to developers by introducing development environment-triggered tests as well as more traditional developer/tester-triggered tests.

Continuous delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time and, following a pipeline through a "production-like environment", without doing so manually. It aims at building, testing, and releasing software with greater speed and frequency. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery.

Disciplined agile delivery (DAD) is the software development portion of the Disciplined Agile Toolkit. DAD enables teams to make simplified process decisions around incremental and iterative solution delivery. DAD builds on the many practices espoused by advocates of agile software development, including scrum, agile modeling, lean software development, and others.

<span class="mw-page-title-main">PinpointBPS</span>

PinpointBPS is a methodology for process improvement in laboratories. It is underpinned by eight principles that form the basis for decision-making in a laboratory. While its application is mainly in healthcare — particularly medical laboratories — it has also been applied in other industries. The methodology has been heralded as "groundbreaking" in the field of laboratory performance improvement.

References

  1. ↑ Original Lean Integration Blog Series Archived 2010-06-11 at the Wayback Machine
  2. ↑ Lean Integration White Paper [ dead link ]
  3. 1 2 John G.Schmidt, David Lyle (2010) Lean Integration: An Integration Factory Approach to Business Agility, Addison-Wesley Pearson Education, ISBN   0-321-71231-5
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.