Skip to main content

Juran and Quality

Several key individuals played a significant part in the creation of the movement to develop the ideas and usage of quality in the production of goods and services. Joseph Juran was one of these main contributors. His main efforts came in the form of the Quality Trilogy and the Quality Roadmap. Each of these approaches helped to set the foundational concepts and practices of achieving quality for customers.

Juran began with a basic definition of quality:
“Quality is conformance or fulfillment of customer requirements”
The Quality Trilogy states that there exist three basic stages or aspects of achieving quality:

  • Quality Planning: quality does not happen by accident
  • Quality Control: checks and balances, structure and governance ensure quality
  • Quality Improvement: we must always seek a better way to do things
Once we have our basic aspects laid out we can then create a “roadmap” or plan for attaining quality. For the delivery of goods and services we could try to create this roadmap each and every time we produce a good or service. However, in the spirit of following best practices, why not use the roadmap that Juran laid out for us?

  • Identify the customers
    • This can be more difficult than it seems. Begin with the end user and work backwards towards Operations
  • Determine the needs of those customers
    • Differentiate between needs (requirements) and demand (frequencies, volumes and durations)
  •  Translate those needs into our language 
    • In the context of ITSM that is a combination of business and technical languages
  • Develop a product that can respond to those needs
    • Design with the end user in mind
  • Optimize the product features so as to meet our needs as well as customer needs
    • Find a win-win balance for both parties
  • Develop a process which is able to produce the product
    • Make it repeatable, standardized, consistent and controlled
  • Optimize the process
    • Continual Service and Process Improvement help here
  • Prove that the process can produce the product under operating conditions
    • Gather data once the process is running , not before, then use it for improvement not punishment
  • Transfer the process to Operations
    • Follow these steps in an iterative approach to continue to drive towards quality
Many of you may recognize these steps since they are woven into ITIL best practices. ITIL serves us not only because it has been proven in the modern day, but it finds its basis in long-standing proven methods such as the work of Joseph Juran.

Comments

Juran Institute said…
Thanks for this excellent overview of Dr. Juran and his work! My name is Brian Solomon, and I'm the Communications Director for the Juran Institute, the quality consulting firm founded by Dr. Juran. Your readers can find out more about what we're doing by visiting our website, Juran.com, or our blog, The Big Q.

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…