Aug 1, 2013

Lean and Six Sigma – Are they related!!!!


Previous month, we were undergoing Six Sigma Training and many members like me had different opinion on the difference between Six Sigma & Lean and we requested trainer to explain the difference between two methodologies/tools.

After the discussions, I really wanted to come up with my own idea on how the differences can be articulated and referred few blogs/sites (Obvious that it has been defined and articulated by many guru’s….Nothing to re-invent J)

Thought, Lets articulate (Of course not more than one page!!!) in my perception and also might help my team members & share my thoughts to broader audience J

Let’s get on to the business… Hopefully this information will be useful for a number of people.
Simple words - Lean is an overall philosophy for continuous improvement which is based on the Toyota Business System.

The six sigma methodology was developed by individuals at Motorola with some outside help.
Lean is about delivering value in the eyes of the customer through the continuous efforts to eliminate waste (Any 8 wastes – Over Production, Waiting, Transport, Poor Process Design, Inventory, Motion, Defects, Under Resource Utilization & Skill).

At this stage, I am sure my team will come back to me with - “Chetan, How wastes can be related/interpreted with respect to Software Industry”  

Lean focuses on continuous improvement while demonstrating respect for people. Lean is also a mindset and an enabling strategy which helps organizations to effectively implement business strategies and initiatives to achieve overall objectives.

Lean is about getting the entire organization to make improvements on a daily basis – Its Cultural Change.

I feel that if lean is implemented correctly - Implemented Correctly - Is this a right word --- YES

Lean Implementer's/Lean Leaders should ask right questions in helping the people who they work for, to learn and discover the right solutions to the problems they are trying to solve. Lean requires employee/member engagement, continuous learning and employee empowerment.

Six sigma is a statistical methodology for improvement and focuses on eliminating variation.
Six sigma and lean both utilize the scientific method to solve problems.
Six sigma is primarily a project based and top down approach.

Belts are trained to lead projects and When i discuss with my domain friends on six sigma; friends advise me; often in many organization we end up in doing things to people versus people.

There are many people who view the belt approach as elitist when applied broadly. It does not promote truly effective employee engagement at all levels of the organization.

A large number of companies have found that they have struggled in successfully sustaining the momentum in their six sigma deployments.  My observation is six sigma tends to be a push approach.
In my view what we should be aiming to create is pull for continuous improvement throughout the organization.

Six sigma, from my standpoint/perspective, is a methodology that compliments and enhances lean.

Many of my friends who implemented Six Sigma and now started using lean sigma approach have told me they wish they had started with lean and enhanced their deployment with six sigma.

I feel it makes more sense to eliminate as much waste as possible upfront and then focuses on eliminating variation.

As read somewhere, Toyota has always used statistical methods in the appropriate situations. Currently the trend is a major emphasis on lean implementations and a decrease in new six sigma deployments.

I am sure that many people have perspectives that are different from mine. Open to suggestions and we can discuss….

Jul 30, 2013

The waiting is over… Updates announced for ISO 9001 & ISO 14001

Updates have finally been announced for the current ISO 9001:2008 Quality & ISO 14001:2004 Environmental Management Standards With both of the updates widely overdue, they have been announced to be expected in the year 2015.

The last update for the ISO 9001 was 2008, ISO 9001:2008 basically re-narrates ISO 9001:2000. The 2008 version only introduced clarifications to the existing requirements of ISO 9001:2000 and some changes intended to improve consistency with ISO 14001:2004.

The ISO 14001 was last updated in 2004, the revision of the standard is in it’s early stages and the earliest date expected for the final version is January 2015. In total, there are 25 recommendations in consideration, for the new revision of ISO 14001.

Since the standard was first published in 1996, ISO 14001:2004, Environmental management systems – Requirements with guidance for use, has been adopted by over 250 000 certified, with the users in 155 countries (worldwide).

*Source

http://www.iso.org/iso/home/news_index/news_archive/news.htm?refid=Ref1547

http://www.isoqsltd.com/waiting-over-updates-announced-iso-9001-iso-14001/

Aug 17, 2010

General Comparison and Changes between ITIL V3 and ITIL V2

Most importantly, a detailed comparison between ITIL V3 and V2 reveals that all the main processes known from ITIL V2 are still there, with only few substantial changes. In many instances, however, ITIL V3 offers revised and enhanced process descriptions.

New ITIL Structure: The ITIL V3 Service Lifecycle

The main difference between ITIL V3 and V2 is the new ITIL V3 Service Lifecycle structure: ITIL V3 is best understood as seeking to implement feedback-loops by arranging processes in a circular way.

This means the old structure of Service Support and Service Delivery was replaced by a new one consisting of the five ITIL V3 core disciplines:

  • Service Strategy determines which types of services should be offered to which customers or markets
  • Service Design identifies service requirements and devises new service offerings as well as changes and improvements to existing ones
  • Service Transition builds and deploys new or modified services
  • Service Operation carries out operational tasks
  • Continual Service Improvement Improvement learns from past successes and failures and continually improves the effectiveness and efficiency of services and processes.

ITIL V3 complements the processes known from ITIL V2 with a number of new processes and puts more emphasis on producing value for the business.

Modifications to Process Interfaces

Due to the new Service Lifecycle structure, all interfaces between the ITIL processes were changed in order to reflect the new ITIL V3 process structure; so even if processes in ITIL V3 and V2 are broadly identical, their interfaces have changed. Example: The Incident Management process must now link to the Service Design processes, although a comparison between Incident Management in ITIL V2 and V3 reveals that the process itself did not change substantially.


http://wiki.en.it-processmaps.com/index.php/Comparison_between_ITIL_V3_and_ITIL_V2_-_The_Main_Changes



Jul 26, 2010

ITIL - The CMDB - The central IT repository

The configuration management database (CMDB) is not a database in the technical sense but a
conceptual IT model, which is indispensable for efficient IT service management. All IT components and inventories are managed in the CMDB.

Configuration management exceeds asset management, often incorrectly used as a synonym, as it does not only document assets from a financial point of view, but captures information regarding the relationship between components, specifications or their location.

Thus IT support can quickly access information on the interdependence of IT services and the IT components (= configuration items = CIs) necessary for them.

According to ITIL, a CMDB must feature the following functionalities:
• manual and, where applicable, automatic recording and modification of configuration items
• description of the relationship and/or interdependence between CIs
• change of CI attributes (e.g. serial numbers)
• location and user management for CIs
• integration via the ITIL processes represented in the system

Dec 26, 2008

What has changed in ISO 9001:2008?

Here's a summary of the changes to ISO 9001 in 2008.

  1. There are no new requirements in this version. This is significant, because a 'requirement' is something you must do.
  2. All the changes are minor. They consist of changes of wording: clarifications and modifications to words or phrases and a few extra notes or examples (see below). Most are small additions or changes, with a few deletions.
    The intent is to make the meaning of a requirement clearer, to improve compatibility with ISO 14001 and/or assist translation to other languages.
  3. The new version was published in mid-November 2008.
  4. From that date, for a new certification you can choose certification to the 2000 or 2008 version.
  5. After one year (from Nov 2008) all recertifications/new certifications will be to the 2008 version. Two years later, certifications to the 2000 version will no longer be valid.

Some examples of the changes, with clause numbers are:

4.2.1: modified to clarify that a single document can cover requirements for one or more procedures (eg, combine requirements for corrective action & preventive action into 1 procedure, or cover 'nonconformity' within another procedure rather than having a separate one)

6.4 Now clarifies what 'work environment' includes, and gives examples such as noise, temperature, humidity

8.2.1 Note added with some ideas on how customer satisfaction can be measured.

General advice: Get a copy of the new version, study the changes, and think about how (or if) the changes affect your system. Note, for example, the advice that you can address multiple requirements in a single procedure (we already have). Notice how the Standard has made it very clear that if you subcontract any part of your service or product out, this doesn't in any way remove or alter your responsibility to meet your customers' requirements.

ISO publishes new edition of ISO 9001 quality management system standard

ISO published ISO 9001:2008, the latest edition of the International Standard used by organizations in 175 countries as the framework for their quality management systems (QMS).

ISO 9001:2008, Quality management system – Requirements, is the fourth edition of the standard first published in 1987 and which has become the global benchmark for providing assurance about the ability to satisfy quality requirements and to enhance customer satisfaction in supplier-customer relationships.

ISO 9001:2008 contains no new requirements compared to the 2000 edition, which it replaces. It provides clarifications to the existing requirements of ISO 9001:2000 based on eight years’ experience of implementing the standard worldwide and introduces changes intended to improve consistency with the environmental management system standard, ISO 14001:2004.

All ISO standards – currently more than 17 400 – are periodically reviewed. Several factors combine to render a standard out of date, such as technological evolution, new methods and materials, new quality and safety requirements, or questions of interpretation and application. To take account of such factors and to ensure that ISO standards are maintained at the state of the art, ISO has a rule requiring them to be periodically reviewed and a decision taken to confirm, withdraw or revise the documents.

ISO/TC 176, which is responsible for the ISO 9000 family, unites expertise from 80 participating countries and 19 international or regional organizations, plus other technical committees. The review of ISO 9001 resulting in the 2008 edition was carried out by subcommittee SC 2 of ISO/TC 176.

This review has benefited from a number of inputs, including the following: a justification study against the criteria of ISO Guide 72:2001, Guidelines for the justification and development of management system standards; feedback from the ISO/TC 176 interpretations process; a two-year systematic review of ISO 9001:2000 within ISO/TC 176/SC2; a worldwide user survey carried out by ISO/TC 176/SC 2, and further data from national surveys.

ISO Secretary-General Alan Bryden commented: “The revised ISO 9001 results from a structured process giving weight to the needs of users and to the likely impacts and benefits of the revisions. ISO 9001:2008 is therefore the outcome of a rigorous examination confirming its fitness for use as the international benchmark for quality management.”

ISO/TC 176/SC 2 has also developed an introduction and support package of documents explaining what the differences are between ISO 9001:2008 and the year 2000 version, why and what they mean for users. These documents are available on the ISO Web site.

Although certification of conformity to ISO 9001 is not a requirement of the standard, it is frequently used in both public and private sectors to increase confidence in the products and services provided by certified organizations, between partners in business-to-business relations, in the selection of suppliers in supply chains and in the right to tender for procurement contracts. Up to the end of December 2007, at least 951 486 ISO 9001:2000 certificates had been issued in 175 countries and economies.


ISO (which does not itself carry out certification) and the International Accreditation Forum (IAF) have agreed on an implementation plan to ensure a smooth transition of accredited certification to ISO 9001:2008. The details of the plan are given in a joint communiqué by the two organizations which is available on the ISO Web site.
ISO 9001:2008, Quality management system – Requirements, costs 114 Swiss francs and is available from ISO national member institutes (see the complete list with contact details) and from ISO Central Secretariat through the ISO Store or by contacting the Marketing & Communication department.

Nov 20, 2008

CMMI - Misunderstandings and Abuses

I was reading White paper, CMM & CMMI - Show me the value! by Mr.Alan Koch, Global Knowledge Instructor, PMP. found very intresting and Thought of sharing some of the very known CMMI Misunderstandings and Abuses.

Misunderstandings

Many people who open the CMMI book are immediately overwhelmed by the volume of information: five Maturity Levels, two Generic Goals, 12 Generic Practices, 25 Process Areas, 55
Specific Goals, 185 Specific Practices, hundreds of Sub-Practices—nearly a thousand pages
in all! It is hard to blame them for feeling that this model must be way too restrictive to be
applicable to a real-life organization.

Yes, the CMMI contains a lot of information. But the majority of it is just that, only information.
For organizations that must achieve a CMMI rating, the Goals are most important. In order to
receive a Maturity Level 2 rating, the organization must achieve only the 16 Goals for the
seven Maturity Level 2 Process Areas.

The Practices (which are much more numerous) are "expected" elements of the model. That
means that the SEI expects that an organization will have to perform all of those Practices in
order to achieve the Goals. But the Practices are not required. Organizations occasionally
employ "alternative practices" to achieve the Goals, and when they do, that is OK. As long as
each Goal is achieved, the actual Practices that are employed are not an issue.
The Sub-Practices and other information in the CMMI are merely "informative" elements of the
model. That is, they are there to provide additional information to help the reader to understand
the intent of the Goals and Practices. There is no requirement (or even expectation) that
an organization will perform all of the Sub-Practices.
Naturally, if your organization is not under a mandate to achieve a Maturity Level rating, then
the Practices, and even the Goals in the CMMI take on more of a suggestive flavor. Of course,
any organization would do well to take them as exceedingly strong suggestions, given the
CMMI’s solid research basis!

Abuses

The SEI designed the CMMI to be a roadmap for process improvement. But what we have seen in practice is organizations requiring their suppliers to achieve specific Maturity Level ratings. This in turn causes those suppliers to turn to the CMMI simply to achieve a rating, even if they have little or no interest in process improvement.

When the CMMI is used by an organization that has no interest in process improvement, its
use can (and often does) become abuse. Processes are written solely to satisfy a CMMI
Appraiser, but with little or no thought for how they will affect the organization's work. Paperwork grows seemingly without bounds, and people feel that they are drowning in "process for process' sake".

In these organizations, the CMMI's primary purpose (a roadmap to improvement) is lost, and it
becomes a straightjacket for the organization and its people. It becomes abusive as it is
abused by those whose primary objective is a Maturity Level rating. And many of these organizations end up with no more than they sought: a Maturity Level rating and process binders sitting on shelves gathering dust while business goes on little improved from its starting point.

For those of us who see the CMMI's potential to benefit those who use it, this is the saddest
and most frustrating thing: to see an organization that goes through the motions of process
improvement, but ends up with only a plaque on the wall and a bevy of disgruntled employees.

It is sad because the benefits are so great when the CMMI is used as a guide to process
improvement, as it was intended! Maturity Level 1 organizations can be frustrating and
exhausting to work in because even when "Heroic Effort" is put forth, project success is often
elusive. This contrasts sharply with moving up the maturity scale by truly improving processes,
which provides significant benefits to the organization.

Nov 12, 2008

ODC: Orthogonal Defect Classification

Ram Chillarege proposed a technique in the early ’90s called Orthogonal Defect
Classification (ODC), as a way of categorizing defects found both during the
development process and after customers receive and begin using the product.


In ODC, defects are classified according to key attributes and then data are
analyzed to form the basis for action plans and process improvement activities.
ODC is a technique mid-way between the traditional RCA (more qualitative and timeconsuming)
and Statistical Defect Models (more quantitative, but not easily translatable into corrective action).
Through the orthogonal classification of defects found (defect type) and their association with their trigger, it is possible to create consistent and meaningful characterizations of the problems that are found across all software development life cycle stages.

A list of strengths and possible limitations in applying ODC has been compiled from the
literature:

Strengths:
o It is an evolution of RCA from a qualitative to a quantitative approach.
o It has adopted a standard taxonomy (types; triggers), which allows
comparability across time and organizations.
o It helps in gathering defect data over time, enabling an organization to run
statistical analysis and – more generally – to look at defect data in a more
objective way.

Limitations:

o It is challenging to use Software Defect Removal, since a large part of the SPI
activity is focused on the code. Furthermore, the later a generic defect (not only
code) is detected, the more difficult and costly it is to remove [12].
o It is typically applied by organizations having a robust measurement system: ODC
needs the capability to consistently gather and analyze data over time; a number of
organizations are at lower maturity levels and do not have this capability, or the
payback period is too remote for its application to be economical.
o The updating of defect types and related defect triggers makes it difficult to
maintain a backward comparability of source defect data over a long period of
time.

Reference: Introducing Root-Cause Analysis and Orthogonal Defect Classification at Lower CMMI Maturity Levels by Luigi Buglione and Alain abran.