<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>PMServicesNW &#187; Quality</title>
	<atom:link href="http://www.pmservicesnw.com/category/quality/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pmservicesnw.com</link>
	<description>Free project management information and downloads</description>
	<lastBuildDate>Tue, 03 May 2011 02:22:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Quality – Rule of 7</title>
		<link>http://www.pmservicesnw.com/2011/03/quality-%e2%80%93-rule-of-7/</link>
		<comments>http://www.pmservicesnw.com/2011/03/quality-%e2%80%93-rule-of-7/#comments</comments>
		<pubDate>Wed, 09 Mar 2011 05:36:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Quality]]></category>
		<category><![CDATA[quality rules]]></category>
		<category><![CDATA[Rule of 7]]></category>

		<guid isPermaLink="false">http://www.pmservicesnw.com/?p=2718</guid>
		<description><![CDATA[By Ray Myers, Jr., PMP Control charts are used in project quality to illustrate how a process behaves over time.  The data points on a control chart can be analyzed to determine if a process is within acceptable limits.  PMBOK states that when a process in within acceptable limits, it is in control and does not need to be adjusted.  When a process is outside acceptable limits, the process should be adjusted. The Rule of 7 states that when 7 consecutive points are above or below the central line, the process is out of control and should be adjusted. About the Author: Ray Myers, Jr. is a PMP certified project manager with over 20 years’ experience planning and managing technology projects.  Contact Ray at www.pmservicesnw.com Article source: www.pmservicesnw.com &#169;2012 PMServicesNW. All Rights Reserved..]]></description>
		<wfw:commentRss>http://www.pmservicesnw.com/2011/03/quality-%e2%80%93-rule-of-7/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Six Sigma DMAIC</title>
		<link>http://www.pmservicesnw.com/2011/02/six-sigma-dmaic/</link>
		<comments>http://www.pmservicesnw.com/2011/02/six-sigma-dmaic/#comments</comments>
		<pubDate>Wed, 09 Feb 2011 06:28:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Quality]]></category>
		<category><![CDATA[dmaic]]></category>
		<category><![CDATA[Six Sigma]]></category>

		<guid isPermaLink="false">http://www.pmservicesnw.com/?p=2576</guid>
		<description><![CDATA[By Ray Myers, Jr., PMP The Six Sigma methodology is a way to improve work processes by eliminating defects.  It is a defined set of practices that can improve efficiency and reduce defects. Six Sigma projects normally follow a five-phase improvement process called DMAIC.  The principles can be applied to a wide variety of processes.  The five phases are: Define First, define the problem, opportunity, process, or customer requirement to be analyzed Measure Next, define the base measurements.  Collect accurate samples, compile, and display data Analyze Analyze the data looking for relationships and defect causes.  Determining the root cause and effect will assist in understanding how to fix a problem or identify improvement opportunities Improve Generate and implement solutions and ideas for improving the problem Control Track and verify the improvements.  Analyzing continuous measurements can help processes remain on track and free of defects below the Six Sigma limit. About the Author: Ray Myers, Jr. is a PMP certified project manager with over 20 years’ experience planning and managing technology projects.  Contact Ray at www.pmservicesnw.com Article source: www.pmservicesnw.com &#169;2012 PMServicesNW. All Rights Reserved..]]></description>
		<wfw:commentRss>http://www.pmservicesnw.com/2011/02/six-sigma-dmaic/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pareto Analysis</title>
		<link>http://www.pmservicesnw.com/2010/11/pareto-analysis/</link>
		<comments>http://www.pmservicesnw.com/2010/11/pareto-analysis/#comments</comments>
		<pubDate>Mon, 15 Nov 2010 16:56:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Quality]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[80/20 analysis]]></category>
		<category><![CDATA[80/20 rule]]></category>
		<category><![CDATA[decision tools]]></category>
		<category><![CDATA[pareto anlysis]]></category>
		<category><![CDATA[project management tools]]></category>

		<guid isPermaLink="false">http://www.pmservicesnw.com/?p=150</guid>
		<description><![CDATA[By: Ray Myers, Jr., PMP Pareto Analysis is a statistical technique that is used to focus attention to the vital few factors that are responsible for producing most of the problems in a project.  You’ve heard it said that 20% of the causes are responsible for 80% of the effort to resolve the problems.  What if we could identify the 20% of the issues that cause the most problems?  How would that benefit your project?  Well, the Pareto Analysis will help you do just that. The Pareto Analysis is a methodology that enables the project manger to focus and correct those problems that will increase the probability of delivering a successful project.  The project manager should do the Pareto Analysis when problems arise to help focus the project team’s efforts on the key cause(s) of a problem. The Pareto Analysis is best performed after conduction a cause-and-effect analysis to count the frequency of different causal factors and to identify problems.  The result will be identification of the 20% of the factors that when resolved, will generate 80% of the advantage.  The goal is to identify which 20% of the factors will provide the greatest advantage when addressed. How to Conduct [...]]]></description>
		<wfw:commentRss>http://www.pmservicesnw.com/2010/11/pareto-analysis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Deming Cycle</title>
		<link>http://www.pmservicesnw.com/2010/11/the-deming-cycle/</link>
		<comments>http://www.pmservicesnw.com/2010/11/the-deming-cycle/#comments</comments>
		<pubDate>Sat, 13 Nov 2010 15:57:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Quality]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Deming Cycle]]></category>
		<category><![CDATA[Deming process improvement]]></category>
		<category><![CDATA[PDCA]]></category>
		<category><![CDATA[process improvement]]></category>
		<category><![CDATA[project management tools]]></category>

		<guid isPermaLink="false">http://www.pmservicesnw.com/?p=141</guid>
		<description><![CDATA[By: Ray Myers, Jr., PMP The Deming Cycle is a 4 step process that is typically used in business or project process improvement.  The 4 steps of the Deming Cycle are: Plan, Do, Check, Act or sometimes referred to as PDCA.  PDCA was the brainchild of Dr. Edwards Deming who is considered by many to be the father of modern quality control.  It is typically used as a repeating process to improve project quality. Here a few notes on the Deming process improvement philosophy: Managers are encouraged to stop sacrificing quality for short term gains Managers must manage for the long term Workers can only correct 15% of quality problems The other 85% is the management’s responsibility because they result from the system Productions systems must be stable for quality to be realized Processes can be tested with statistical process control charts Quality cannot be “inspected” into products or services. Quality must be designed into the product, service, or system processes Here is a brief description about how to perform the Deming Methodology: Plan —Set the short-term objective Study the process Determine the time frame Define the opportunity Decide what data will be needed Decide what each member will do [...]]]></description>
		<wfw:commentRss>http://www.pmservicesnw.com/2010/11/the-deming-cycle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cause and Effect Analysis: Fishbone Diagram</title>
		<link>http://www.pmservicesnw.com/2010/11/cause-and-effect-analysis-fishbone-diagram/</link>
		<comments>http://www.pmservicesnw.com/2010/11/cause-and-effect-analysis-fishbone-diagram/#comments</comments>
		<pubDate>Tue, 09 Nov 2010 15:12:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Quality]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[Cause and Effect Diagram]]></category>
		<category><![CDATA[Fishbone Diagram]]></category>
		<category><![CDATA[how to create a fishbone diagram]]></category>
		<category><![CDATA[how to develop a Ishikawa Diagram]]></category>
		<category><![CDATA[Ishikawa Diagram]]></category>
		<category><![CDATA[project management tools]]></category>

		<guid isPermaLink="false">http://www.pmservicesnw.com/?p=122</guid>
		<description><![CDATA[By: Ray Myers, Jr., PMP The Fishbone Diagram identifies many possibilities for an effect or a problem.  It is an established problem solving tool that is well suited for group analysis because it visually assists with understanding of a problem’s roots cause.  Dr. Ishikawa developed the fishbone diagram as an analysis tool that provides a systematic way of looking at effects and the causes that create or contribute to those effects.  The Fishbone Diagram may also be referred to as a Cause-and-Effect Diagram or an Ishikawa Diagram in honor of the inventor. First, let’s define some important terms: Affect:  The action that causes the effect Effect:  The result of the actions of the affect Fishbone Diagrams are typically developed during a brainstorming session to immediately sort ideas into useful categories.  Here’s how to develop a Fishbone Diagram: Setup Prepare a conference room with a white board, flip chart or other means to collect the ideas that are generated by the session Nominate a scribe to write the ideas on the white board or flip chart Limit group size to 8-10 Process The group leader writes the effect (the problem) on the far right side of the whiteboard or flip chart [...]]]></description>
		<wfw:commentRss>http://www.pmservicesnw.com/2010/11/cause-and-effect-analysis-fishbone-diagram/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quality Improvement Tool: PDCA</title>
		<link>http://www.pmservicesnw.com/2010/11/quality-improvement-tool-pdca/</link>
		<comments>http://www.pmservicesnw.com/2010/11/quality-improvement-tool-pdca/#comments</comments>
		<pubDate>Mon, 08 Nov 2010 15:09:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Quality]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[PDCA]]></category>
		<category><![CDATA[Plan Do Check Act]]></category>
		<category><![CDATA[project management tool]]></category>
		<category><![CDATA[Quality improvement tool]]></category>
		<category><![CDATA[quality tool]]></category>

		<guid isPermaLink="false">http://www.pmservicesnw.com/?p=106</guid>
		<description><![CDATA[By: Ray Myers, Jr., PMP PDCA is short for Plan, Do, Check, Act.  PDCA was the brainchild of Dr. Edwards Deming who is considered by many to be the father of modern quality control.  It is typically used as a repeating process to improve project quality. The PDCA cycle is a 4 stage process that is used to coordinate continuous improvement efforts.  It emphasizes that quality improvement programs must begin with careful planning, resulting in actions that are analyzed for effectiveness in a process that is continually repeated. Here’s how to perform the PDCA cycle in a nutshell: PDCA P     Plan D     Do C     Check A     Act Plan Identify the problem.  Use tools like brainstorming to generate ideas Identify the root cause.  Use tools like fishbone diagrams to identify the root causes Develop a solution and create an action plan or implementation plan Do Implement the solution Check Measure and evaluate the results of the implemented solution Act Repeat the process About the Author: Ray Myers, Jr. is a PMP certified project manager with over 2o years experience planning and managing technology projects.   Contact Ray at wwwpmservicesnw.com Article source: www.pmservicesnw.com &#169;2012 PMServicesNW. All Rights Reserved..]]></description>
		<wfw:commentRss>http://www.pmservicesnw.com/2010/11/quality-improvement-tool-pdca/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>QA vs. QC</title>
		<link>http://www.pmservicesnw.com/2010/10/qa-vs-qc/</link>
		<comments>http://www.pmservicesnw.com/2010/10/qa-vs-qc/#comments</comments>
		<pubDate>Wed, 13 Oct 2010 08:03:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Quality]]></category>
		<category><![CDATA[QA vs QC]]></category>
		<category><![CDATA[quality assurance vs quality control]]></category>

		<guid isPermaLink="false">http://www.pmservicesnw.com/?p=422</guid>
		<description><![CDATA[By: Ray Myers, Jr., PMP Quality Assurance (QA) Quality assurance establishes the quality requirements and quality control measures that will be used to audit and monitor the project activities and deliverables.  It creates the formal methodology designed to assess the quality of products or services produced by the project.  QA involves making sure standards and procedures are effective and that they are complied with throughout the project. Quality Control (QC) Quality control is the process of monitoring and recording specific project results to determine if they comply with the relevant standards, assess performance, and recommend necessary changes to eliminate causes of unsatisfactory performance.  Quality control makes sure that project deliverables comply with quality standards established by the quality assurance process.  QC involves monitoring, testing and reviews of specific project deliverables to determine if they comply with the relevant project standards. About the Author: Ray Myers, Jr. is a PMP certified project manager with over 2o years experience planning and managing technology projects.   Contact Ray at wwwpmservicesnw.com Article source: www.pmservicesnw.com &#169;2012 PMServicesNW. All Rights Reserved..]]></description>
		<wfw:commentRss>http://www.pmservicesnw.com/2010/10/qa-vs-qc/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quality &#8211; Deming</title>
		<link>http://www.pmservicesnw.com/2010/08/quality-deming/</link>
		<comments>http://www.pmservicesnw.com/2010/08/quality-deming/#comments</comments>
		<pubDate>Fri, 06 Aug 2010 14:15:56 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Quality]]></category>
		<category><![CDATA[deming]]></category>
		<category><![CDATA[quality deming]]></category>

		<guid isPermaLink="false">http://www.pmservicesnw.com/?p=402</guid>
		<description><![CDATA[By: Ray Myers, Jr., PMP Dr. Edward Deming’s philosophy is based on improvements that are planned, completed, measured, and acted on. Managers must stop sacrificing quality for short-term gains Managers must manage for the long term Workers can only correct 15 percent of the quality problems The other 85 percent are management’s responsibility, because they are due to the system Production system must be stable for quality to be realized Processes can be tested with statistical process control charts Quality is the continuous, incremental improvement of a stable system Quality cannot be “inspected into products”; it must be designed in through the product and process designs The Deming Cycle What are we trying to accomplish? What changes can be made that will result in improvement? How will we know that a change is an improvement? The Deming Cycle or the PDCA Cycle P          Plan D         Do C          Check A         Act About the Author: Ray Myers, Jr. is a PMP certified project manager with over 2o years experience planning and managing technology projects.   Contact Ray at wwwpmservicesnw.com Article source: www.pmservicesnw.com &#169;2012 PMServicesNW. All Rights Reserved..]]></description>
		<wfw:commentRss>http://www.pmservicesnw.com/2010/08/quality-deming/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quality &#8211; Juran</title>
		<link>http://www.pmservicesnw.com/2010/08/quality-juran/</link>
		<comments>http://www.pmservicesnw.com/2010/08/quality-juran/#comments</comments>
		<pubDate>Thu, 05 Aug 2010 14:12:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Quality]]></category>
		<category><![CDATA[quality juran]]></category>

		<guid isPermaLink="false">http://www.pmservicesnw.com/?p=397</guid>
		<description><![CDATA[By: Ray Myers, Jr., PMP Joseph Juran promoted a 3-principle quality process: Quality Planning Identify customers Determine customers’ 5 basic needs Develop product features Establish quality goals Develop a process Prove process capability Quality Control Choose what to control Choose units of measurement Establish measurement Establish standards of performance Measure actual performance Interpret the differences between actual vs. standard Quality Improvement Prove the need for improvement Identify specific projects for improvement Organize to guide the projects Organize to discover causes Diagnose to find causes Implement remedies Provide for controls to retain the gains About the Author: Ray Myers, Jr. is a PMP certified project manager with over 2o years experience planning and managing technology projects.   Contact Ray at wwwpmservicesnw.com Article source: www.pmservicesnw.com &#169;2012 PMServicesNW. All Rights Reserved..]]></description>
		<wfw:commentRss>http://www.pmservicesnw.com/2010/08/quality-juran/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quality – Malcolm Baldrige Award</title>
		<link>http://www.pmservicesnw.com/2010/08/quality-malcolm-baldrige-award/</link>
		<comments>http://www.pmservicesnw.com/2010/08/quality-malcolm-baldrige-award/#comments</comments>
		<pubDate>Wed, 04 Aug 2010 14:11:26 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Quality]]></category>
		<category><![CDATA[malcoim baldrige]]></category>
		<category><![CDATA[quality malcoim baldrige award]]></category>

		<guid isPermaLink="false">http://www.pmservicesnw.com/?p=393</guid>
		<description><![CDATA[By: Ray Myers, Jr., PMP An award established by the U.S. congress to promote quality awareness.  The award considers: Validity and analysis of quality of information used in business decisions Analysis includes factors that impact success or failure of strategy Social Regulatory Economic Development of scenarios built around possible outcomes of strategy Lessons learned from previous strategy developments Award Criteria Senior executive leadership Information and analysis Strategic quality planning Human resource development and management Management of process quality Quality and operational results Customer focus and satisfaction About the Author: Ray Myers, Jr. is a PMP certified project manager with over 2o years experience planning and managing technology projects.   Contact Ray at wwwpmservicesnw.com Article source: www.pmservicesnw.com Copyright © 2009 Ray Myers, Jr.  All rights reserved. &#169;2012 PMServicesNW. All Rights Reserved..]]></description>
		<wfw:commentRss>http://www.pmservicesnw.com/2010/08/quality-malcolm-baldrige-award/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

