DOCSLIB.ORG

An Executive View of Lean and Agile IT for Cfos

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
An Executive View of Lean and Agile IT for Cfos An Executive View of Lean and Agile IT for CFOs Mark Schwartz, Enterprise Strategist at Amazon Web Services Over the last two decades, the Lean Lean IT delivery is based on the same concepts as Lean IT profession has developed new Manufacturing and Lean Six Sigma, all imported from the Toyota Production System that pioneered them. The general ways of working that are intended idea of Lean is to eliminate waste by concentrating on reducing lead times. When an enterprise adopts a Lean point to deliver better business value of view, it maps out the processes it uses to deliver value and examines each step to find waste that makes the process take faster and at lower risk. longer than necessary. By eliminating each type of waste, a business can shorten its lead times and reduce its costs. There are buzzwords associated with these techniques, of IT delivery is amenable to a Lean approach, although IT must course, as with everything in IT—in this case, Agile, Lean, be thought of as a product development process rather than and DevOps are the terms to know. Unfortunately, these a manufacturing process (that is, a process that is different techniques are often presented as IT-focused, with unclear every time it is performed). For this reason, Six Sigma techniques, which try to reduce variance, are not generally benefits for the enterprise. They even seem to bring with applicable. But as with other business processes, delivering them a danger that they might undermine the CFO’s or IT capabilities involves a series of steps, each of which often CEO’s ability to oversee IT-related initiatives. contains waste. The typical sources of waste in an IT process correspond fairly closely to those in a manufacturing process. As the CFO’s role continues to expand, new approaches Authors Mary and Tom Poppendieck have identified them to technology are becoming critical to delivering business as partially done work, extra processes, extra features, task value. This eBook shows how Agile, Lean, and DevOps switching, waiting, motion, and defects.1 streamline digital delivery, foster innovation, and make the enterprise nimbler. These practices could very well be the best thing that has happened to CFOs since the invention of the spreadsheet, helping them to increase returns, oversee investments, implement controls, gain transparency, provide better data to the enterprise, and, of course, manage costs. So, why is it so important to eliminate users are trained, and the capability is waste and shorten lead times in IT delivery? launched. This is a long process—and it One reason is to reduce time-to-market, can hide a great deal of waste. Much of of course; or for internal use capabilities, the process (and the potential for waste) the time until value can be harvested from is outside the direct control of the IT an investment. Another reason is that organization, or it is at the interface between speed helps make sure IT capabilities are it and the rest of the business. A careful look as effective as possible. IT teams can now at the processes informed by Lean software quickly deliver minimal viable products delivery techniques can make a substantial to users, check to make sure they are difference in business outcomes. accomplishing what they should, and then continue adding features or make changes. Speed creates business agility. Agile Because capabilities are constantly being Agile IT delivery is based on a simple finished, IT is able to pivot and work on principle: in a complex environment (which other things that become more important IT delivery certainly is) it is better to learn without wasting any of their previous and adjust than to strictly follow a plan work. And finally, speed reduces risk, both made in advance. (I’ll explain in a moment because unforeseen events can be quickly how this is connected with Lean). The idea addressed and because the delivery risk of of deliberately diverging from a plan might IT capabilities is reduced. sound dangerous. It seems like it would be The idea of deliberately impossible to control and impossible to hold diverging from a plan The value stream for delivering an IT people accountable. But in fact, it is not. It might sound dangerous. capability is different in every organization, is rigorously controlled but through very different mechanisms. It seems like it would be but typically it includes steps like this: the business need is recognized and expressed, impossible to control requirements are written, a plan is created I sometimes like to think of Agile techniques and impossible to hold based on the requirements, a business plan in terms of risk mitigation. If we make a people accountable. is prepared, a governance process acts on detailed plan that covers—let’s say—a three- But in fact, it is not.” the business plan, resources are acquired, year project and then try to implement it, software is developed, software is tested, we are accepting a number of large risks, security is verified, software is deployed, notably: 1. The risk that the plan will have mistakes. • The amount of change we expect over the 2. The risk that circumstances will change three years depends on the amount of over those three years. uncertainty in the business and technical environments, and we happen to be in a time 3. The delivery risk that in three years the of fast change and high uncertainty. In the Agility is the ability product will not have been completed. course of three years, startups are launched of the business to and disrupt entire industries. Agility is the In the traditional way of delivering IT respond to change, ability of the business to respond to change, (the so-called Waterfall, or Gantt chart- and it is contrary and it is contrary to sticking with a plan, yet obsessed approach), the product is not extremely valuable. to sticking with a delivered until the end of the project, so plan, yet extremely the entire amount of the investment is at risk until the end of the three years when • A Microsoft study showed that only one-third valuable.” the results become visible (or not). of ideas actually have the intended result, another one-third have the opposite effect, and the last third are neutral. We have all seen How serious are these risks? Very. cases where an IT system was supposed to • Detailed plans for IT systems are reduce costs but didn’t, or was supposed to 2 always wrong, as we have found in our increase revenues but didn’t. Another study experience over multiple decades. Studies found that companies are wasting nearly $400 have also shown that more than half billion per year on digital initiatives that don’t 3 of the features requested will rarely or deliver their expected return. never be used. And even if everything is delivered according to plan, it still • Numerous studies have shown that the larger might not meet the business need it an IT project is, the higher its risk of not was intended to address. delivering. A short increment of work is more likely to accomplish its goal and is more predictable. Agile practices allow for constant learning Large batch sizes in IT are large groups of and adjustment, working in small cycles requirements. A DevOps team processes to finish a product and give it to users only a small set of requirements at a time, for feedback. It is practiced by small, using a highly automated process to deploy autonomous, self-contained teams that capabilities to users quickly before moving can quickly learn and adjust with minimal on to another small set of requirements. ceremony. Because Agile teams are trying As a result, DevOps teams deploy code very to finish the product quickly, it is natural often—sometime hundreds or thousands to combine Agile principles with Lean of times a day. practices, which focus on reducing cycle The heavy use of automation in DevOps times. The combination of the two gives has benefits for controls and compliance. businesses agility, risk mitigation, and cost- Many of the organizational controls that effectiveness. would have been operated manually can now be automated, making them more DevOps reliable and easily documentable, and allowing them to be applied continuously In Lean theory, two important sources of rather than periodically. waste are handoffs (motion and waiting) and large batch sizes. Traditional IT DevOps is an excellent way to foster practices were based on handoffs between innovation. With it, new ideas can be development, testing, and operations, who tested quickly, inexpensively, and at deployed the product. DevOps, the state- low risk. Working in the cloud enhances of-the-art set of practices in Lean and Agile these benefits: infrastructure can be IT, addresses these handoffs by combining provisioned instantly and then later be development, testing, and operations skills de-provisioned. IT capabilities that would on a single, small team accountable as a take the enterprise a long time to build whole for results. can be accessed as pre-created building blocks and incorporated into experiments. The business implications of Agile, the picture at intervals but otherwise absent. Lean, and DevOps You can think of the Agile approach as one of continuous oversight and transparency. • Fast time to market or time to value The project team delivers frequently and for internal use products results are apparent as those deliveries are Agile is a continuous • Less waste from producing unneeded made. Because of the agility of the process, investment process capabilities the oversight body can choose to change where the business • Less waste from producing capabilities direction at any moment, end the investment, that do not accomplish objectives case is (effectively) increase it, or substitute other objectives.
Load more

Recommended publications
  • Sep 0 1 2004
    AEROSPACE MERGERS AND ACQUISITIONS FROM A LEAN ENTERPRISE PERSPECTIVE by JUNHONG KIM B.S., Chemical Engineering Seoul National University (1998) SUBMITTED TO THE SYSTEM DESIGN AND MANAGEMENT PROGRAM IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE IN ENGINEERING AND MANAGEMENT at the MASSACHUSETTS INSTITUTE OF TECHNOLOGY June 2004 @0 2004 Junhong Kim. All rights reserved The author hereby grants to MIT permission to reproduce and to distribute publicly paper and electronic copies of this thesis document in whole or in part. Signature of Author......... ........................ Junhong Kim /ste7&Ies 'and Management Program February 2004 Certified by ... .........I . ...................... Joel Cutcher-Gershenfeld Executive Director, Engineering Systems Learning Center Senior Research Scientist, Sloan School of Management Accepted by ....................................................... -........................... Thomas J. Allen Co-Director, LFM/SDM Howard W. Johnson Professor of Management r A c c ep te d b y ............................. ......... ............................................................................................ David Simchi-Levi Co-Director, LFM/SDM MASSACHUSETTS INSTITUTE| Professor of Engineering Systems O.F TENL GYL.J SEP 0 1 2004 BARKER LIBRARIES Room 14-0551 77 Massachusetts Avenue Cambridge, MA 02139 Ph: 617.253.2800 MITL-ibries Email: [email protected] Document Services http://Iibraries.mit.eduldocs DISCLAIMER OF QUALITY Due to the condition of the original material, there
    [Show full text]
  • Opportunities for Lean Enterprise in Public Regional Transportation
    Cleveland State University EngagedScholarship@CSU ETD Archive 2010 Opportunities for Lean Enterprise in Public Regional Transportation Levent Baykut Cleveland State University Follow this and additional works at: https://engagedscholarship.csuohio.edu/etdarchive Part of the Mechanical Engineering Commons How does access to this work benefit ou?y Let us know! Recommended Citation Baykut, Levent, "Opportunities for Lean Enterprise in Public Regional Transportation" (2010). ETD Archive. 757. https://engagedscholarship.csuohio.edu/etdarchive/757 This Thesis is brought to you for free and open access by EngagedScholarship@CSU. It has been accepted for inclusion in ETD Archive by an authorized administrator of EngagedScholarship@CSU. For more information, please contact [email protected]. OPPORTUNITIES FOR LEAN ENTERPRISE IN PUBLIC REGIONAL TRANSPORTATION LEVENT BAYKUT Bachelor of Science in Physics Kocaeli University, Kocaeli, Turkey June, 2007 submitted in partial fulfillment of requirements for the degree MASTER OF SCIENCE IN INDUSTRIAL ENGINEERING at the CLEVELAND STATE UNIVERSITY July, 2010 This Thesis has been approved for the Department of Mechanical Engineering and the college of Graduate Studies by ____________________________________________________ Thesis Chairperson, Professor M. Brian Thomas, P.E. Mechanical Engineering / ____________________________________________________ Professor L. Ken Keys Mechanical Engineering / ____________________________________________________ Professor Taysir H. Nayfeh Mechanical Engineering / ____________________________________________________ Adjunct Professor John Van Blargan Mechanical Engineering / To my parents Kadir Turhan and Gülden Baykut, and my twin brother Mert Baykut. ACKNOWLEDGEMENT I am extending my most sincere appreciation to my thesis advisor Dr. M. Brian Thomas. Without his supervision and assistance, this thesis could never be completed. I am also thankful for my committee members‟, Dr. Taysir H. Nayfeh, Dr. L.
    [Show full text]
  • Lean Six Sigma
    Lean Six Sigma KIVI NetwerkCafe Regio Gelderland 5 oktober 2020 Ir Maarten van Beek TUE Scheikundige Technologie 1998 DuPont de Nemours AkzoNobel Diosynth MSD Nouryon Worley Introductie Continu verbeter technieken, overal worden ze met vlagen ingevoerd. Six Sigma Lean manufacturing Lean Six Sigma 5S Kaizen TRIZ Agile/Scrum 3 Wat is Six Sigma? 4 Wat is Six Sigma ? A statistical measure of process capability: Six Sigma means that a process produces fewer than 3.4 defects per million opportunities – i.e., a 99.99966% yield A set of tools , which takes human and technical components into account; the implementation of new, powerful (and easy-to-use) statistical methods Decision making based on facts as an integral part of the management system A methodology for the continuous improvement of the company’s processes and products A business philosophy and strategy, developed by recognized leaders in world class quality The objective is to align the entire performance of the company with the customer 5 What is Six Sigma – According to Industry “Six Sigma is a highly disciplined process that helps us focus on developing and delivering near perfect products and services.” “Six Sigma is an overall strategy to accelerate improvements in processes, products and services. It is also a measurement of total quality where focus is placed on eliminating defects and variation in any and all processes and products.” “Six Sigma has literal, conceptual, and practical definitions. At Motorola, we think about Six Sigma at three different levels: As a metric , As a methodology , As a management system Essentially, Six Sigma is all three at the same time.” 6 6 sigma backgrounds Lean 6 Sigma method is based on the PDSA cycle.
    [Show full text]
  • Lean Software Development – What Exactly Are We Talking About?
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by University of Limerick Institutional Repository Lean Software Development – What Exactly Are We Talking About? Oisín Cawley1, Xiaofeng Wang2, Ita Richardson1, 1Lero-The Irish Software Engineering Research Centre, University of Limerick, Ireland. 2Free University of Bozen/Bolzano, ominikanerplatz 3 piazza Domenicani, I-39100 Bozen/Bolzano, Italy. 1{Oisin.Cawley, Ita.Richardson}@lero.ie, [email protected] Abstract. As the Software Engineering landscape continues to evolve and new paradigms are introduced, there can be a tendency for both industry and academia to enthusiastically embrace new approaches and march forward under whatever banner conventional wisdom has decided to adopt. One such banner is Lean Software Development, a paradigm that continues to see a growth in interest driven by the need for cost reductions within industry. The term lean attracts the attention of business, but precisely how it applies within software development is still being debated. In addition, its relationship to the better understood agile methodologies is also a topic for debate. Having been drawn into this research area ourselves, we present here a review of Lean Software Development and try to distil out for the reader some understanding of this somewhat undefined topic. We conclude with some thoughts on where this subject might go to from here. Keywords: Software Engineering, Software Development, Lean, Agile. 1 Introduction We are living in a period of history which is witnessing a drive for cost reductions and efficiencies across almost every business segment in almost every developed country. Traditionally businesses have been able to find efficiencies and cost reductions through automation and organisational restructuring of the more routine and repeatable processes.
    [Show full text]
  • Page 1 of 8 Process Improvement Concepts and Terminology
    Process Improvement Concepts and Terminology (A Guide to the Jargon) Disclaimer: Some statements/definitions are broad generalities intended as an initial introduction to Lean and Six Sigma concepts. (Not in alphabetical order) Methodologies and Related Concepts Lean – Process improvement methodology focused on reducing waste in a system. It is based heavily on the teachings of W. Edwards Deming and the Toyota Production System. The term Lean is derived from the idea that the approach reduces “wastes” that contribute to inefficient processes and poor outcomes. It does NOT refer to the idea that it is a way to cut staff as in the management adage: “lean and mean.” Mura – Japanese term that means “waste.” Key concept in Lean, which focuses on the reduction of “waste.” Muda – Japanese term that means “unevenness.” Workaround – Temporary fix to a system or process breakdown – a reaction to an immediate problem. In some cases, may not work well. Equivalent to “Duct tape on a split on a car radiator hose.” Not a permanent solution. Sometimes the result of procedures created without input from those involved in the process. A workaround does nothing to improve the situation in the future. PDCA/PDSA – Plan, Do, Check or Study, Act – A change process originally developed by Walter Shewhart (PDCA) and later revised by W. Edwards Deming (PDSA). It is sometimes referred to as the Deming wheel. It is intended to be used in multiple, successive cycles. © 2015 PCPI. All rights reserved. Page 1 of 8 Process Improvement Terminology (Jargon) Handout Error-proofing (“poka yoke” Japanese term) – the practice of making a process error proof, or make errors more apparent.
    [Show full text]
  • Lean Manufacturing
    8 Lean manufacturing Lean manufacturing, lean enterprise, or lean production, often simply, "Lean", is a production practice that considers the expenditure of resources for any goal other than the creation of value for the end customer to be wasteful, and thus a target for elimination. Working from the perspective of the customer who consumes a product or service, "value" is defined as any action or process that a customer would be willing to pay for. Essentially, lean is centered on preserving value with less work. Lean manufacturing is a management philosophy derived mostly from the Toyota Production System (TPS) (hence the term Toyotism is also prevalent) and identified as "Lean" only in the 1990s. TPS is renowned for its focus on reduction of the original Toyota seven wastes to improve overall customer value, but there are varying perspectives on how this is best achieved. The steady growth of Toyota, from a small company to the world's largest automaker, has focused attention on how it has achieved this success. 8.1 Overview Lean principles are derived from the Japanese manufacturing industry. The term was first coined by John Krafcik in his 1988 article, "Triumph of the Lean Production System," based on his master's thesis at the MIT Sloan School of Management. Krafcik had been a quality engineer in the Toyota-GM NUMMI joint venture in California before coming to MIT for MBA studies. Krafcik's research was continued by the International Motor Vehicle Program (IMVP) at MIT, which produced the international best-seller book co-authored by Jim Womack, Daniel Jones, and Daniel Roos called The Machine That Changed the World.] A complete historical account of the IMVP and how the term "lean" was coined is given by Holweg (2007).
    [Show full text]
  • Application of Lean Enterprise and Six Sigma As an Amalgamated Improvement Strategy
    APPLICATION OF LEAN ENTERPRISE AND SIX SIGMA AS AN AMALGAMATED IMPROVEMENT STRATEGY Nicholas Loyd, University of Alabama in Huntsville Abstract rooted in the Toyota Production System (TPS), a Lean Enterprise and Six Sigma are two of the most philosophy pioneered by Taichii Ohno and Shigeo prominent improvement philosophies available to Shingo in post-World War II Japan at the now- organizations today. This article investigated how successful automotive company. After Toyota’s surge these two philosophies can be used cohesively as an in productivity and quality came to the global forefront improvement strategy. A comparison was performed in the mid-1970s, many American companies began to relative to the underlying principles, the respective study TPS and implement portions of it, such as tools used, and the implementation methodologies of kanban and 5S, into their own organizations. While each philosophy. A real world example was used to Lean has often become synonymous with these tools, illustrate how Lean Enterprise and Six Sigma can be Toyota described the objective of TPS as simply applied in unison. Finally, it was concluded that reducing the time line from the moment a customer although Lean and Six Sigma have differences, places an order to the point when the company collects primarily in the tools used, they do not have conflicting cash by removing non-value-added activities, or wastes objectives or implementation methodologies and can (Ohno, 1988). The term Lean originated after the 1990 be amalgamated, free of buzz words, to provide an book The Machine That Changed the World, in a study effective overall improvement strategy.
    [Show full text]
  • A Fusion of Pan-Pacific Process Improvement
    Lean Six Sigma: A Fusion of Pan-Pacific Process Improvement Malcolm T. Upton Master Black Belt, George Group [email protected] Charles Cox Master Black Belt, Lean Master, George Group [email protected] Abstract Statistical Process Control, Total Quality Management, The Toyota Production System, Just-in-Time, Lean Enterprise, and Six Sigma have roots and histories on both sides of the Pacific. Lately, the most recent of these, Lean Enterprise and Six Sigma, have begun to be fused into a more powerful and effective hybrid, addressing many of the weaknesses and retaining most of the strengths of previous traditions. Using TQM as a baseline, the strengths and threats of Lean Enterprise and Six Sigma are highlighted and a more powerful Lean Six Sigma fusion is discussed. Specific areas examined are organizational infrastructure, career path/incentives, analysis tools and methods favored, depth and type of organizational deployment, methods included in addition to process improvement, project identification strategy, project portfolio management, methodology for tool use, project review methods, speed-cost-quality focus, and methodology bias. Some additional discussion on the role of complexity management in augmenting the value of Lean Six Sigma will also be included. TQM, Lean, & Six Sigma: A Comparison The end of the 20th and beginning of the 21st century has seen increasing and continuing pressure from customers and competitors for greater value from their purchases whether based on higher quality, faster delivery, or lower cost (or some combination) in both manufactured products1 and services2. In many industries, this has encouraged companies to adopt Six Sigma as their process improvement approach.
    [Show full text]
  • Redalyc.TOYOTA PRODUCTION SYSTEM
    Independent Journal of Management & Production E-ISSN: 2236-269X [email protected] Instituto Federal de Educação, Ciência e Tecnologia de São Paulo Brasil Alves de Moura, Delmo TOYOTA PRODUCTION SYSTEM - ONE EXAMPLE TO SHIPBUILDING INDUSTRY Independent Journal of Management & Production, vol. 8, núm. 3, julio-septiembre, 2017, pp. 874-897 Instituto Federal de Educação, Ciência e Tecnologia de São Paulo Avaré, Brasil Available in: http://www.redalyc.org/articulo.oa?id=449552566004 How to cite Complete issue Scientific Information System More information about this article Network of Scientific Journals from Latin America, the Caribbean, Spain and Portugal Journal's homepage in redalyc.org Non-profit academic project, developed under the open access initiative INDEPENDENT JOURNAL OF MANAGEMENT & PRODUCTION (IJM&P) http://www.ijmp.jor.br v. 8, n. 3, July - September 2017 ISSN: 2236-269X DOI: 10.14807/ijmp.v8i3.626 TOYOTA PRODUCTION SYSTEM - ONE EXAMPLE TO SHIPBUILDING INDUSTRY Delmo Alves de Moura Federal University of ABC, Brazil E-mail: [email protected] Rui Carlos Botter University of São Paulo, Brazil E-mail: [email protected] Submission: 04/02/2017 Revision: 17/02/2017 Accept: 24/02/2017 ABSTRACT The objective is analysing the shipbuilding industry and their competitiveness to develop and apply Toyota Production System. The methodology consisted in the qualitative type research by means of personal interviews, with entrepreneurs, presidents, directors and managers of the maritime industry. The contribution of that work was several Toyota Production System technicians can and should be applied at shipyards to improve their vessel manufacturing and assembling systems. The shipbuilding system can use the techniques used in the Toyota Production System as an example for its production process.
    [Show full text]
  • 8 Lean Manufacturing, Lean Enterprise and Lean Production
    8 Lean Manufacturing, Lean enterprise and Lean Production Lean software development Lean software development (LSD) is a translation of lean manufacturing and lean IT principles and practices to the software development domain. Adapted from the Toyota Production System, a pro-lean subculture is emerging from within the Agile community. Origin The term lean software development originated in a book by the same name, written by Mary Poppendieck and Tom Poppendieck.The book presents the traditional lean principles in a modified form, as well as a set of 22 tools and compares the tools to agile practices. The Poppendiecks' involvement in the Agile software development community, including talks at several Agile conferences has resulted in such concepts being more widely accepted within the Agile community. Lean principles Lean development can be summarized by seven principles, very close in concept to lean manufacturing principles: 1.Eliminate waste 2.Amplify learning 3.Decide as late as possible 4.Deliver as fast as possible 5.Empower the team 6.Build integrity in 7.See the whole Eliminate waste Lean philosophy regards everything not adding value to the customer as waste (muda). Such waste may include: unnecessary code and functionality delay in the software development process unclear requirements insufficient testing (leading to avoidable process repetition) bureaucracy slow internal communication In order to eliminate waste, one should be able to recognize it. If some activity could be bypassed or the result could be achieved without it, it is waste. Partially done coding eventually abandoned during the development process is waste. Extra processes and features not often used by customers are waste.
    [Show full text]
  • "The Roots of Lean"
    Roots of Lean John Bicheno Lean Enterprise Research Centre Cardiff Business School What this talk is NOT A history of Lean or TPS LERC Conference, 2008 Some believe Lean started with The Machine.. in 1990, but Schonberger, World Class Hall, Zero Inventories, Manufacturing, 1986 1983 – Faster, Higher, Stronger – Basic concepts – Line operators – Results – Staff as supporting actors – Identifying problems – Overstated role of capital – Planning to execute a level – Economy of multiples schedule – Responsibility Centres – Converting for flow and – Quality: Zeroing in flexibility – – Design leverage Flow balancing – – Partners in Profit: Suppliers Quality systems – – Simple Models, Simple Product design Systems – Supplier networks – Managing the Transformation – Planning and measurement – Strategy revealed – Implementing .. – .. And manufacturing strategy LERC Conference, 2008 Schonberger on Production History Schonberger, in a 2006 article, traces the development of production including Quality, Maintenance, and Manufacturing in Japan He concludes by saying that, although there were huge early gains, Japanese industry in general has not kept up with the state of the art in production management. But, he says, there were three significant effects of Japanese manufacturing: – JIT/TQC brought a holistic, rather than silo, orientation – It was a wake up call on the necessity for continual improvement and training – It provided a proven counter to trade off theories that were just becoming popular in the 1980s. LERC Conference, 2008 What
    [Show full text]
  • IIBA Lean Six Sigma Introduction – Janet Lau
    IIBA Lean Six Sigma Introduction – Janet Lau Janet Lau is a certified Lean Six Sigma Master Black Belt with thirteen years of business improvement experience. She is also a recent Executive MBA graduate at the University of Alberta. Currently, Janet is the Principal Consultant and Owner of Breakthrough Solutions Consulting. She is specialized in delivering transformational business results for organizational effectiveness, productivity, and profitability. Janet successfully delivered over hundred projects ranging in complexity from simple Lean projects to complex technical projects across the full spectrum of the business - operations, supply chain management, HR, Finance, Health & Safety, IT, and cross-department level initiatives. She is passionate about developing the next generation of Lean Six Sigma practitioners and offers a variety of Lean Six Sigma training courses. Her key strategy for success is being people-oriented, data-driven, and taking a stand for making a difference. Presentation Topics: • What is ‘Lean’...and what is ‘Six Sigma’? 1. Introduction to Lean • What are the similarities and differences? and Six Sigma • How does this help me in my work? • Taking a data-driven approach to define the 2. Data! Data! Data! problem, identify defects, and validate the effectiveness of solutions. 3. Hands-on learning and real-world problem • How does experiential project engagement and solving create learning increase project ownership? engagement. Part 1: What is Lean Six Sigma? In the 1980s Lean and Six Sigma were two separate methodologies. Lean – known from Toyota Six Sigma – known from Motorola Both were derived from the manufacturing industry with same goal: improve customer improvement on improving the speed improve employee reduction in cost satisfaction, product quality of production engagement.
    [Show full text]