Title:
-------
Case Study: Lean Manufacturing plant level continuous improvement
How can DevOps be implemented with Lean and Agile?
Description:
-----------------
How can we leverage our knowledge of Lean Manufacturing and TPS (Toyota Production System) to implement Agile & DevOps in organizations?
My topic is about "how DevOps can be implemented with Lean and Agile", by implementing Enterprise Kanban system that has this value stream:
“Portfolio Kanban (upstream “Epics”) -> Scrum / ScrumBan / Kanban “In the middle” -> Release Engineering Kanban(Downstream “Deployable Artifacts”),
Presentation History:
Agile2016, PechaKuchaLightening Talk on July 27, 2016
Reference:
---------------
Slides 21-27 in my preso:
http://www.slideshare.net/RaviTadwalkar/devops-approach-point-of-view-by-ravi-tadwalkar
Drafted presentation to encourage changes to Development processes considering the crises brought on by injecting a start-up into an enterprise environment
In Agile Development, Testing is meant to be a part of the development process, right along with coding, but many “Agile Teams” are missing this vital component and experiencing degregated quality. In this presentation, we will discuss how to integrate Agile Testing in Kanban processes by discussing the following:
• Introduction to Agile and Lean
• How testers add value to cross-functional Agile Development Teams
• How testers participate in Agile ceremonies
• How to test in an Agile Environment
• The Four Environments (Dev, Test, Stage, Production)
• The types of testing that occurs in each environmen
Resource Planning is one of the biggest headaches for medium to large organizations. Creating a detailed resource plan that is meaningful is very difficult, and keeping it up to date is almost impossible. Plans that look good are often an attractive fiction, full of unrealistic assumptions, over-allocations, and the spreading of too-few people in too many ways.
Agile Resource Planning provides a very different approach to the classic model. It produces realistic plans that are simple to maintain, and effective for planning work over time. In this webinar, Dr. Kevin Thompson will present new concepts in Agile Resource Planning, which provide a practical and easy-to-use approach to Resource Planning that can be used for Agile and classic environments.
Introduction to Kanban for Knowledge Work: Kanban is emerging in Software Development and IT Operations as a method of improving transparency, predictability, and value. Learn how to get started with Kanban. See how Kanban can help you achieve the benefits of Pull, Value-Focus, and Capability-Improvement. Find out if Kanban is right for you.
Scrumban Demystified. Talk from Agile New England.
A few of the Scrumban Evolutions from Mamamoth bank from the upcoming book on Scrumban.
More excerpts can be found at facebook.com/scrumban
Learn more at scrumban.io
Do you have a case study of applying the Kanban Method in a Scrum context. We want to learn more from your experiments and results. Contact us at info@codegenesys.com
Life Has Not Been That Rosy With Agile : Rahul SudameoGuild .
In my experience, Agile adoption started in some of the organizations with lot of hype and inflated expectations. And in such cases, if Agile transformation is not handled properly, it can result in multiple challenges rather than providing the expected benefits.
This practical experience sharing session would cover some such problems I faced while applying Agile in different environments. The audience practicing Agile can relate some of these challenges with their own environment as well. The attendees who are on their path to Agile transformation can learn from the lessons and mistakes shared by the speaker.
The session would cover challenges observed due to nature of the project, customer-vendor engagement model, application of processes, attitude of people rolling out agile, unrealistic expectations, conflict in roles and responsibilities. It would also highlight challenges introduced to some of the roles (like Project/QA Manager/Manual Tester etc.) in Agile environment and impact on billing / project contracts / SOW etc.
Drafted presentation to encourage changes to Development processes considering the crises brought on by injecting a start-up into an enterprise environment
In Agile Development, Testing is meant to be a part of the development process, right along with coding, but many “Agile Teams” are missing this vital component and experiencing degregated quality. In this presentation, we will discuss how to integrate Agile Testing in Kanban processes by discussing the following:
• Introduction to Agile and Lean
• How testers add value to cross-functional Agile Development Teams
• How testers participate in Agile ceremonies
• How to test in an Agile Environment
• The Four Environments (Dev, Test, Stage, Production)
• The types of testing that occurs in each environmen
Resource Planning is one of the biggest headaches for medium to large organizations. Creating a detailed resource plan that is meaningful is very difficult, and keeping it up to date is almost impossible. Plans that look good are often an attractive fiction, full of unrealistic assumptions, over-allocations, and the spreading of too-few people in too many ways.
Agile Resource Planning provides a very different approach to the classic model. It produces realistic plans that are simple to maintain, and effective for planning work over time. In this webinar, Dr. Kevin Thompson will present new concepts in Agile Resource Planning, which provide a practical and easy-to-use approach to Resource Planning that can be used for Agile and classic environments.
Introduction to Kanban for Knowledge Work: Kanban is emerging in Software Development and IT Operations as a method of improving transparency, predictability, and value. Learn how to get started with Kanban. See how Kanban can help you achieve the benefits of Pull, Value-Focus, and Capability-Improvement. Find out if Kanban is right for you.
Scrumban Demystified. Talk from Agile New England.
A few of the Scrumban Evolutions from Mamamoth bank from the upcoming book on Scrumban.
More excerpts can be found at facebook.com/scrumban
Learn more at scrumban.io
Do you have a case study of applying the Kanban Method in a Scrum context. We want to learn more from your experiments and results. Contact us at info@codegenesys.com
Life Has Not Been That Rosy With Agile : Rahul SudameoGuild .
In my experience, Agile adoption started in some of the organizations with lot of hype and inflated expectations. And in such cases, if Agile transformation is not handled properly, it can result in multiple challenges rather than providing the expected benefits.
This practical experience sharing session would cover some such problems I faced while applying Agile in different environments. The audience practicing Agile can relate some of these challenges with their own environment as well. The attendees who are on their path to Agile transformation can learn from the lessons and mistakes shared by the speaker.
The session would cover challenges observed due to nature of the project, customer-vendor engagement model, application of processes, attitude of people rolling out agile, unrealistic expectations, conflict in roles and responsibilities. It would also highlight challenges introduced to some of the roles (like Project/QA Manager/Manual Tester etc.) in Agile environment and impact on billing / project contracts / SOW etc.
Kanban Development And The Paradigm Of FlowAlisson Vale
That was the title of my presentation on Oct 8th 2009 at Agiles 2009, 2nd Latin-American conference on Agile Development Methodologies. I have designed this presentation trying to summarize what the Kanban community is trying to spread recently as a new way to manage knowledge work.
In my consultancy, I’ve come to realise that most clients/teams I’ve coach don’t care too much about the theories - they just want to work.
This presentation, therefore, takes a standpoint in the practical parts.I will also mimic my experience with most teams I’ve introduced kanban too, and do the introduction in small iterations.This means that the presentation also is a template for anyone that will need to introduce kanban to others.
Como revelar suas habilidades como um gestor eficaz para identificar o problema que o cliente realmente tem para só depois encaixar a solução que ele precisa.
Hacking getKanban v2.0: Advanced Game Mechanics to Illuminate Lean by Cheryl ...Cheryl M Hammond
Even more than other methodologies ("frameworks", whatever), Kanban requires deep understanding in order to bring about real change and measurable results. Too many teams struggle, even after they understand the "rules" of Kanban—failing to recognize visible problems on their own boards, or not knowing how to replace old bad habits with better ones.
I see the same struggle, in microcosm, when I train teams using the open-source getKanban Version 2.0. Even though the game urges teams to limit work in progress (WIP)—the linchpin of Lean and Kanban—I found that my players inevitably wanted to raise it. Over numerous classes and diverse groups of players, I tried hints, then rants, about how limiting WIP reduces cycle time. But there was a problem: play teams who took my advice and lowered their WIP weren't seeing better outcomes.
In this session, I'll show you the adjustments I've made to getKanban Version 2.0 to guide players to their "a-ha" moment—a deep, personal experience they feel and remember. Now, instead of just the basics of how a Kanban board works, my students understand how to detect and solve problems that impede their flow. I see the difference when they leave the game and go back to work. For players and coaches who are already familiar with the basics of Kanban, my new open-source hacks to Version 2.0 will help you go deeper and illuminate Lean principles for your clients and teams—and yourselves!—so you can achieve real results faster.
Instructions slides for the GetKanban.com Kanban Board GameYuval Yeret
some slides that help a group "get" the getkanban kanban game.
I usually introduce the game verbally but find this kind of visual introduction useful. let me know if you have the game and tried this... or if it gives you the urge to try the game ;-)
This is another game that I have had great fun playing and also thought me an my clients a great deal. I use it as staple for all my intros to Lean and agile.
The goal of the game is to move 20 coins through a series of process step (aka players). Each player flips the coins once before it can be passed over.
The game shows very effectively how limiting the work in process (WIP) increases the throughput and improves lead times, both for the first coin and the total time for all 20 coins.
If you move through the game slides quickly a nice little animation effect takes place. Watching that actually gave me a new understanding of what Flow means. Compare the first and last iterations and see the coins flow through the process, each step creating value.
If you like this presentation you will find more like this in Kanban In Action (http://bit.ly/theKanbanBook) where we have dedicated a whole chapter on agile games.
Lean Kanban India 2018 | Leveraging Lean and Kanban to implement Continuous ...LeanKanbanIndia
Session Overview :
How can continuous improvement culture and mindset be "transformed" with Lean and Kanban? What can corporate culture derive from and expand on cultures that still exist in Lean Manufacturing movement that began with TPS (Toyota Product System)? How can we leverage our knowledge of Lean and Kanban to transform organization's fitness for purpose? This is a workshop about a pictorial case study that shows how to apply Lean Manufacturing values, principles & best practices for continuous improvement in today's fast-paced IT landscape.
Jan de Vries - How to convince your boss that it is DevOps that he wantsAgile Lietuva
- We all know that we could implement DevOps a lot faster if we only would have commitment from our boss. We all know that there is a shiny business case for almost every DevOps implementation
- And we all know that the whole company will reap the benefits regarding speed, agility and stability once we implemented DevOps. Actually, it provides good, fast and cheap at the same time. So, what are we waiting for? What is your boss waiting for? What is C-level waiting for?
- That’s something we will do research on in this workshop. We will also share our research on this from the recent past.
- The workshop starts with a presentation about 7 practices that a company should adopt to be able to apply DevOps.
- The technique that we use is called Appreciative Inquiry. To tackle a problem, it discovers the best practices that work, the reason they work and how these combined practices can be used to avoid the problem ahead and create a strategic change. The aim is to build – or even rebuild – organizations around what works, rather than trying to fix what doesn’t.
- So we want to know what your boss is afraid of and what you have already tried to convince him that he is better off with DevOps. You will leave the workshop with the combined Appreciative Inquiry insights of all the attendees
Lean IT provides transparency.
Avoids the old games between development and business.
Shows how business and development processes do not have to be poles apart.
Synerzip's Top 12 from AGILE2017:
- We Are Going Back Full Circle
- Agile Executive Leadership
- Whole Team Does UX
- Agile Beyond Engineering
- Containerized Microservices=NoOps
- ATDD/BDD Holy Grail
- Dynamic Re-Teaming!
- Estimating Time/Cost
- Get Them Hooked!
- Scaling Agile / SAFe 4.5
- Surprises at Spotify!
- Architect/Architecture
AGILE2017 Conference Overview:
- August 7-11th in Orlando, FL
- 2,200 participants from 40+ countries
- 18 tracks, 284 sessions
- 4 Special Tracks
- Stalwarts
- Experience Reports
- 3-7 min Lightning Talks
- Audacious Salon
- Inspiring Keynotes
- David Marquet, best-selling author of Turn the Ship Around
- Jez Humble, Founder and CTO, DevOps Research and -
- Assessment LLC, UC Berkeley
- Denise Jacobs, Founder and CEO, The Creative Dose
DevOps provides competitive advantage to businesses through faster time to market by breaking down silos between business, development, testing and operations. They combine the Development and Operations teams leveraging automation of processes to enable rapid release cycles.
DevOps - an Agile Perspective (at Scale)Brad Appleton
by Brad Appleton, Agile Day Chicago 2018, October 26 2018;
This presentation gives a comprehensive introduction to DevOps, for Agile development practitioners. In 2018, there are many misunderstandings about Agile & DevOps and how they relate to one another. Too many think of Agile (development) as primarily "Scrum", and that DevOps is Continuous Integration & Delivery (both of which are wrong). This presentation describes the meaning, origin & history of DevOps from an Agile development perspective.
Agile is a very popular project management method. It is especially useful in managing rapid deployment of new product features in measured cycles. SharePoint 2013 can be leveraged as a platform for managing Agile
My talk about DevOps in Knowit Developer Summit 2018 in Oslo. This talk is a condensed version of the DevOps workshop I run for management teams and technical teams to start their journey as an organization towards DevOps. We refer to DASA DevOps Agile Skills Association's definitions of DevOps. The talk includes also Knowit DevOps Maturity Model high level description.
IIT Academy: Agile. What is Lean? Isn't it a manufacturing thing? How do we apply it to software engineering practices?
Understand Lean in the context of modern Agile practices. Harness lean thinking and an updated look at the Toyota Production System (TPS). Designed for operational teams, maintenance teams, high availability teams, sales teams, management teams, project and portfolio management.
Capital One DevOps Case Study: A Bank with the Heart of Tech CompanySimform
Many organizations want to adopt DevOps to work their way through digital transformation. This case study of Capital One's journey of adopting DevOps and what distinctive tools and methods they introduced to stay ahead of the competition.
This presentation, created by Syed Faiz ul Hassan, explores the profound influence of media on public perception and behavior. It delves into the evolution of media from oral traditions to modern digital and social media platforms. Key topics include the role of media in information propagation, socialization, crisis awareness, globalization, and education. The presentation also examines media influence through agenda setting, propaganda, and manipulative techniques used by advertisers and marketers. Furthermore, it highlights the impact of surveillance enabled by media technologies on personal behavior and preferences. Through this comprehensive overview, the presentation aims to shed light on how media shapes collective consciousness and public opinion.
Collapsing Narratives: Exploring Non-Linearity • a micro report by Rosie WellsRosie Wells
Insight: In a landscape where traditional narrative structures are giving way to fragmented and non-linear forms of storytelling, there lies immense potential for creativity and exploration.
'Collapsing Narratives: Exploring Non-Linearity' is a micro report from Rosie Wells.
Rosie Wells is an Arts & Cultural Strategist uniquely positioned at the intersection of grassroots and mainstream storytelling.
Their work is focused on developing meaningful and lasting connections that can drive social change.
Please download this presentation to enjoy the hyperlinks!
Obesity causes and management and associated medical conditions
Pecha kucha format- how can devops be implemented with lean and agile
1. Case Study: Lean Manufacturing plant level continuous improvement
How can DevOps
be implemented with
Lean and Agile?
LKNA2017 (Lean Kanban India 2017), September 16, 2017
Agile2016, Pecha Kucha Lightening Talk on July 27, 2016
by Ravi Tadwalkar
in/rtadwalkar @tadwalkar rtadwalkar@gmail.com
2. This is a story of Lean Manufacturing Plant Manager Shari,
seeking plant value stream level continuous improvement.
Shari intends to improve overall plant level visibility on
SLAs, batch sizes (volumes) and WIP. Here are some
pictures from the Lean Manufacturing plant she manages.
3. 3
Plant Manager Shari is trained
by Lean Enterprise Institute.
She has read Taiichi Ohno’s
“TPS”, Eli Goldratt’s “Goal”,
Gene Kim’s “Phoenix Project”!
You can say that Shari is big
on Lean, in just 10 pictures!
4. 4
Shari implemented Lean manufacturing at this
Plant she manages, influencing other 5 plants.
She implemented Lean, starting with Lean House
for tracking plant level continuous improvement
on a daily and weekly basis! RED means “needs
improvement”; GREEN means “sustaining it”!
6. 6
In all manufacturing cells,
Shari implemented visual
kanban boards to visualize
work in progress. She even
added kanban board for
continuous improvement of
the process for doing work!
7. 7
Here Shari shows an
example of kanban
card that is attached
to a product across
workstations in a cell.
She says plant has JIT
(Just-In-Time)
inventory almost, with
at most 2 days of raw
materials in case of
DVDs as end products!
11. 1
1
Here is the
“synergy” cell
Shari proudly
shows during
a plant tour.
Here she
pilots ways to
improve
visibility of
plant level
value stream
specific to
monitoring
SLAs, batch
sizes and
WIP.
12. We saw some pictures from this Lean Manufacturing plant.
We will see how DevOps can be implemented to seek plant level
continuous improvements with Lean and Agile.
13. Upstream Kanban:
Downstream Kanban:
13
• Begin with the end in mind!
• Use Portfolio Kanban board across Org Design (Team of Teams)
• Use a simple Kanban board with “ToDo->Doing->Done”, “Plan->Build->Run” or similar workflow
• Visualize portfolio feature level bottlenecks to "Stop Starting, Start Finishing"!
• Supplement Portfolio Kanban system (“Upstream”) with Release Engineering Kanban system (“Downstream Kanban”)
Run
F
E
I
Idea Deploy to Prod
G
D
GY
PB
MN
2
∞
AB
Biz Design
Plan Build (Dev & QA)
Architecture,
resource plan
Core team OMS …
3 3
DE
Explicit policy:
Feature is “done”
only when last
team working on
it has completed
“Deploy to Prod” Lead time ends at
1st infinite queue!
There could be
additional queues
with no WIP limit.
Lead time “clock”
starts at 1st queue
i.e. WIP limited
input queue!
3 3
Deployed
(Note touch time)
NPD
(New Prod
Dev) (60%)
Defect&
Tech Debt
(30%)
Innovation
(10%)
5
2
1
Expedite 1
3
Fixed
Date
Standard
Intangible
2
2
3
WIP Limits
based on
classes of service
(Release Engineering)
WIP Limits
based on
work types
(feature teams)
Lean Portfolio Management and Release Engineering
14. 1
4
Solutioning started with Shari
organizing process simulation
of scenarios for plant level
process improvements.
15. 1
5
Shari participated in solutioning as Plant Manager
during User Story Mapping for plant simulations
about improving Lean Manufacturing value stream
with visibility on SLAs, batch sizes and WIP.
Note how her persona shows up on a slide in this
picture showing this user story map as well☺
16. Compare & Contrast: Lean Manufacturing & IT
1
6
Like Lean manufacturing plant, for continuous improvements, IT
uses Kaizen events e.g. open spaces in corporate setting:
17. 1
7
Compare & Contrast: Lean Manufacturing & IT
Like Lean manufacturing plant, for continuous improvements, IT
uses Deming’s PDCA loop on a Kanban board like this:
Example of
continuous
improvement
about
introducing
DevOps via
feature toggle
18. 1
8
In summary: Solutioning is an end-to-end
process, starting with process simulation & story
mapping, to visualize epics on Portfolio Kanban,
to big room planning, to open space “kaizen”
events, to implementation based on DoD, and to
visualize deployable artifacts on DevOps Kanban!
19. During planning, create org alignment to improve flow (1st way of DevOps), using Portfolio Kanban system.
19
Lean Governance Model- Applying 3 ways of DevOps
Enable managers in shaping various communities of practice: create culture of continual experimentation & learning (3rd way of DevOps).
• Begin with succinctly defined portfolio hierarchy or swim lanes that consist
of strategic (CAPEX) and tactical (OPEX) investments:
• Themes
• Initiatives
• Features
• Create single-piece flow of portfolio items with Portfolio Kanban board.
Apply lean metrics for continuous improvement.
• Apply first way of DevOps: emphasize on performance of entire system by
analyzing value streams, WIP, lead times & due date performance.
During execution, enable continuous feedback loops (2nd
way of DevOps) with obstacle boards to act on
impediments & dysfunctions.
• This requires low-fidelity obstacle escalation process.
This can be a 2-level (team->management) process, or
a 3-level (team->program>portfolio) process.
• Example of obstacle board and related workflow:
20. In Summary:
20
We looked at Lean Manufacturing workflow related continuous improvement case
study. Implementing DevOps means creating DevOps mindset & culture. That
requires lots of Lean, Six Sigma, TQM, Lean Startup, and yes, Bit of Agile with Lots of
“Respect for People”:
Top down approach:
30-60-90 strategic plan for
continuous improvement
with baseline assessment
of DevOps capability
maturity
Bottom up approach:
Crowd sourcing tactical
plan for continuous
improvement with
assessment based open
space events
Inside out approach:
PDCA Kanban board for
feedback driven visibility
with Lean Startup method
(build-measure-learn loop)
and TQM (PDCA loop)
Implementing DevOps requires mindset & culture open to all approaches
21. Appendix slide: Integrated ALM & Atlassian Tool Chains for DevOps
Development Tools
Atlassian BitBucket (GIT)
Developer writes code and
check-in
Associate JIRA Issue Types
(Tasks / Bugs)
Build gets triggered
✓ Microsoft Visual Studio (For .NET)
✓ Eclipse (For JAVA)
Atlassian BAMBOO for CI
Build Definitions for:
✓ Database
✓ .NET
✓ Java
Atlassian BAMBOO for Continuous Deployment (CD)
Approve / Reject
Build
DIT1
Functional
Testing
• Continuous Integration
• Scheduled Build
Approve / Reject
Build
DIT2
Approve / Reject
Build
SIT
Regression
Testing
Selenium
Approve / Reject
Build
UAT
UAT Testing
Approve / Reject
Build
PROD
Functional
Testing
DEVELOPMENT Branch
QA Branch
MASTER Branch
FEATURE Branch
Service & Data Mock
Epics
e.g. Ship to Home Pre-pay
(JIRA Issue Type)
User Stories
(JIRA Issue Type)
Monitoring
Ngaios
Initiatives
e.g. Sports on Spectrum
(JIRA Issue Type)
Release Stream aka Agile Release Train (ART)
Themes
(Strategic Goals)
✓ prevent defects related to
Requirements problems
✓ Test Planning
✓ Test Execution
✓ Traceability & Reporting
✓ Defect Creation in JIRA
✓ Track Coverage & Quality Metrics
UX Team DB Team ART Engineer Product Managers
Note: Integrate Atlassian Bamboo with “Chef” for non-windows deployments
DevelopmentTasks
Visualize Portfolio Timeline by Releases
Swift-Kanban Metrics
and/or
EasyBI plugin
(Reporting & Charting)
On top of existing JQL queries
Visualize Investment by Themes
PMO-level
Status Reporting
Testing Tasks
21
Kanplan: backlog
for Kanban and
Scrumban teams
21
Editor's Notes
We will look at pictures about a case study from Lean Manufacturing Plant Level Perspective, to realize that:
Implementing DevOps means creating DevOps mindset & culture
It requires new ways of thinking about people, process & tools
It requires lots of Lean, Six Sigma, TQM (PDCA Cycle), Lean Startup, and yes…bit of Agile with Lots of Love (as in “Respect for People”)
We will look at pictures about a case study from Lean Manufacturing Plant Level Perspective, to realize that:
Implementing DevOps means creating DevOps mindset & culture
It requires new ways of thinking about people, process & tools
It requires lots of Lean, Six Sigma, TQM (PDCA Cycle), Lean Startup, and yes…bit of Agile with Lots of Love (as in “Respect for People”)
Here is our Plant Manager Shari. She has read Goal, even The Phoenix Project, I am not joking! She intends to improve Lean Manufacturing value stream level visibility on SLAs, batch sizes and WIP. Here is some pictures from her plant.
Here is our Plant Manager “Shari”. She intends to improve Lean Manufacturing value stream level visibility on SLAs, batch sizes and WIP. Here is some pictures from her plant.
Here is our Plant Manager Shari. She intends to improve Lean Manufacturing value stream level visibility on SLAs, batch sizes and WIP. Here is some pictures from her plant.
Here is our Plant Manager Shari. She intends to improve Lean Manufacturing value stream level visibility on SLAs, batch sizes and WIP. Here is some pictures from her plant.
Here is our Plant Manager Shari. She intends to improve Lean Manufacturing value stream level visibility on SLAs, batch sizes and WIP. Here is some pictures from her plant.
Here is our Plant Manager Shari. She intends to improve Lean Manufacturing value stream level visibility on SLAs, batch sizes and WIP. Here is some pictures from her plant.
Here is our Plant Manager Shari. She intends to improve Lean Manufacturing value stream level visibility on SLAs, batch sizes and WIP. Here is some pictures from her plant.
Here is our Plant Manager Shari. She intends to improve Lean Manufacturing value stream level visibility on SLAs, batch sizes and WIP. Here is some pictures from her plant.
Here is our Plant Manager Shari. She intends to improve Lean Manufacturing value stream level visibility on SLAs, batch sizes and WIP. Here is some pictures from her plant.
Here are some pictures from Planning & Solutioning meetings for plant level continuous improvement.
We will look at these pictures about this case study from Lean Manufacturing Plant Level Perspective, to realize that:
Implementing DevOps means creating DevOps mindset & culture
It requires new ways of thinking about people, process & tools
It requires lots of Lean, Six Sigma, TQM (PDCA Cycle), Lean Startup, and yes…bit of Agile with Lots of Love (as in “Respect for People”)
Here are some pictures from Planning & Solutioning meetings for plant level continuous improvement.
Here are some pictures from Planning & Solutioning meetings for plant level continuous improvement.
Here are some pictures from Planning & Solutioning meetings for plant level continuous improvement.
Here are some pictures from Planning & Solutioning meetings for plant level continuous improvement.
Here are some pictures from Planning & Solutioning meetings for plant level continuous improvement.