www.KeenEtik.com [email_address] ERADICATE WASTE AND ALL SOURCE OF INEFFICIENCIES Lean Services applied to IT activities

TOO MUCH… TOO MUCH MONEY… TOO MUCH TIME… TOO MUCH BUGS… TOO MUCH PEOPLE COMPLYING

… BUT YOU WORKED SO HARD

HOW TO MAKE EVERYBODY HAPPY ? (CUSTOMERS AND TEAMS)

… THINK LEAN LISTEN TO THE VOICE OF CUSTOMERS ERADICATE WASTE AND ALL SOURCE OF INEFFICIENCIES SUPPORT THE OPERATIONAL SYSTEM MAKE THE RESULTS INVOLVE YOUR TEAMS IN THE QUEST FOR PERFORMANCE

LEAN IS MUCH MORE THAN INDUSTRIAL METHODS LEAN WAS BORN IN THE AUTOMOTIVE INDUSTRY IN JAPAN BUT THE CONCEPTS ARE UNIVERSAL AND COULD BE APPLIED TO ALL KIND OF ACTIVITIES

LISTEN TO THE VOICE OF CUSTOMERS

ERADICATE WASTE PROCESSING UNDEFINED PROCESS, OVERPROCESSING, FAILURE PROCESS WAITING UNAVAILABLE RESOURCES, UNAVAILABLE USERS BOTTLENECK MOTION REWORKS, MISALLOCATION MAKING DEFECTS BUGS, RECURRENT ISSUES, BACKLOG OF DEMAND (Partially done work) BAD OWNERSHIP OF APPLICATIONS BY USERS INVENTORY APPLICATION, SOFTWARE OR MACHINE NOT USED DUPLICATION OF SOFTWARE OR APPLICATION FOR THE SAME NEED OVERPRODUCTION DEMAND NOT TIED TO BUSINESS PRIORITIES TRANSPORT FLUIDITY ACROSS THE ORGANIZATIONS ANY ACTIVITY THAT CONSUMES RESOURCES BUT DOES NOT CREATE VALUE

PROCESSING

UNDEFINED PROCESS, OVERPROCESSING, FAILURE PROCESS

WAITING

UNAVAILABLE RESOURCES, UNAVAILABLE USERS

BOTTLENECK

MOTION

REWORKS, MISALLOCATION

MAKING DEFECTS

BUGS, RECURRENT ISSUES, BACKLOG OF DEMAND (Partially done work)

BAD OWNERSHIP OF APPLICATIONS BY USERS

INVENTORY

APPLICATION, SOFTWARE OR MACHINE NOT USED

DUPLICATION OF SOFTWARE OR APPLICATION FOR THE SAME NEED

OVERPRODUCTION

DEMAND NOT TIED TO BUSINESS PRIORITIES

TRANSPORT

FLUIDITY ACROSS THE ORGANIZATIONS

CONTROL THE VARIABILITY GAP BETWEEN CURRENT AND TARGET PERFORMANCE INPUT QUALITY REQUIREMENT (COMPLETENESS, CLARITY, UNDERSTANDING, FEASIBILITY) INCIDENT QUALIFICATION STABILITY OF THE SOFTWARE ENVIRONMENT FAILURE PROCESS PREDICTABILITY, RISKS ESTIMATE SCHEDULING BUDGET DESIGN CODING TESTING TRAINING CHANGE MANAGEMENT INCIDENT MANAGEMENT SKILLS LEVEL Depending on the IT activities

INPUT QUALITY

REQUIREMENT (COMPLETENESS, CLARITY, UNDERSTANDING, FEASIBILITY)

INCIDENT QUALIFICATION

STABILITY OF THE SOFTWARE

ENVIRONMENT

FAILURE PROCESS

PREDICTABILITY, RISKS

ESTIMATE

SCHEDULING

BUDGET

DESIGN

CODING

TESTING

TRAINING

CHANGE MANAGEMENT

INCIDENT MANAGEMENT

SKILLS

LEVEL

INCREASE THE FLEXIBILITY ANYTHING THAT DOES NOT ALLOW THE SYSTEM TO RESPOND QUICKLY TO THE CUSTOMER DEMAND CAPACITY BOTTLENECK ORGANIZATION RELATIONSHIP WITH USERS PROXIMITY AND FLUIDITY BETWEEN TEAMS ROLES AND RESPONSIBILITIES SIZE OF TEAMS SKILLS MULTIPLE SKILLS COLLABORATIVE WORK

CAPACITY

BOTTLENECK

ORGANIZATION

RELATIONSHIP WITH USERS

PROXIMITY AND FLUIDITY BETWEEN TEAMS

ROLES AND RESPONSIBILITIES

SIZE OF TEAMS

SKILLS

MULTIPLE SKILLS

BUILD YOUR MEASUREMENT SYSTEM TO ENTER IN A CONTINOUS IMPROVEMENT LOGIC

INITIATE DIALOG BETWEEN MANAGEMENT AND TEAMS ON THE FLOOR

GIVE A CLEAR DIRECTION TO YOUR TEAMS

IDENTIFY LEADERS TO SHOW THE WAY

DEVELOP VALUES SHARING

SET INCENTIVES TO CAPTURE THE MOTIVATION OF YOUR TEAMS

MAP YOUR PROCESS HOW TO START…CONDUCT KAIZEN WORKSHOPS IDENTIFY YOUR DYSFUNCTIONS DESIGN YOUR TARGET PROCESS BUILD YOUR ACTION PLAN

MAP YOUR PROCESS

Ahmed EL MIR VP KeenEtik Contact.keen @ gmail.com www.KeenEtik.com Contact

Ahmed EL MIR

VP KeenEtik

Contact.keen @ gmail.com

www.KeenEtik.com