<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;AkEHSXw9eip7ImA9WxNVF0s.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711</id><updated>2009-10-28T15:23:58.262-07:00</updated><title>Q- Environment</title><subtitle type="html">To develop a shared understanding  and common dimension for quality assurance.

To facilitate the free exchange of information.

To provide space to exchange views.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://q-environment.blogspot.com/" /><link rel="hub" href="http://pubsubhubbub.appspot.com/" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>19</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/Q-Environment" type="application/atom+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><entry gd:etag="W/&quot;C0UBRXwycCp7ImA9WxVTEkQ.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-8417962849524102484</id><published>2008-12-26T03:27:00.001-08:00</published><updated>2008-12-26T03:34:14.298-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-26T03:34:14.298-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="ISO 9001:2008" /><title>What has changed in ISO 9001:2008?</title><summary type="html">Here's a summary of the changes to ISO 9001 in 2008.   There are no new requirements in this version. This is significant, because a 'requirement' is something you must do. 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 &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/m2YskISh0xA" height="1" width="1"/&gt;</summary><link rel="related" href="http://www.iso9001consultant.com.au/9001_2008.html" title="What has changed in ISO 9001:2008?" /><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/8417962849524102484/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=8417962849524102484" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/8417962849524102484?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/8417962849524102484?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/m2YskISh0xA/what-has-changed-in-iso-90012008.html" title="What has changed in ISO 9001:2008?" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/12/what-has-changed-in-iso-90012008.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU4AR346fip7ImA9WxVTEkU.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-7706187530225148313</id><published>2008-12-26T02:35:00.000-08:00</published><updated>2008-12-26T02:39:06.016-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-12-26T02:39:06.016-08:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="ISO 9001" /><title>ISO publishes new edition of ISO 9001 quality management system standard</title><summary type="html">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 &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/6Zmy6NN4tbA" height="1" width="1"/&gt;</summary><link rel="related" href="http://iso9000and9001.blogspot.com" title="ISO publishes new edition of ISO 9001 quality management system standard" /><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/7706187530225148313/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=7706187530225148313" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/7706187530225148313?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/7706187530225148313?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/6Zmy6NN4tbA/iso-publishes-new-edition-of-iso-9001.html" title="ISO publishes new edition of ISO 9001 quality management system standard" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/12/iso-publishes-new-edition-of-iso-9001.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEQHRXk_fCp7ImA9WxRUEkg.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-9083248323668945252</id><published>2008-11-20T20:51:00.000-08:00</published><updated>2008-11-20T23:25:34.744-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-11-20T23:25:34.744-08:00</app:edited><title>CMMI - Misunderstandings and Abuses</title><summary type="html">I was reading White paper, CMM &amp; 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.MisunderstandingsMany 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 &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/5ll0J2bezW8" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/9083248323668945252/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=9083248323668945252" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/9083248323668945252?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/9083248323668945252?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/5ll0J2bezW8/cmmi-misunderstandings.html" title="CMMI - Misunderstandings and Abuses" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/11/cmmi-misunderstandings.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkEGQ34yfSp7ImA9WxRVFEU.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-459186189046276652</id><published>2008-11-12T02:00:00.000-08:00</published><updated>2008-11-12T02:10:22.095-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-11-12T02:10:22.095-08:00</app:edited><title>ODC: Orthogonal Defect Classification</title><summary type="html">Ram Chillarege proposed a technique in the early ’90s called Orthogonal DefectClassification (ODC), as a way of categorizing defects found both during thedevelopment process and after customers receive and begin using the product.In ODC, defects are classified according to key attributes and then data areanalyzed to form the basis for action plans and process improvement activities.ODC is a &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/DnW0R0rjlnI" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/459186189046276652/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=459186189046276652" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/459186189046276652?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/459186189046276652?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/DnW0R0rjlnI/odc-orthogonal-defect-classification.html" title="ODC: Orthogonal Defect Classification" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/11/odc-orthogonal-defect-classification.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0cEQXg4eCp7ImA9WxZTEE8.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-4288445927574648984</id><published>2008-01-10T20:12:00.000-08:00</published><updated>2008-01-10T20:16:40.630-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-10T20:16:40.630-08:00</app:edited><title>CMMI V1.2: What Has Changed and Why</title><summary type="html">This article provides a view of what has been included – and not included – in Capability Maturity Model®Integration Version 1.2 (CMMI®V1.2) for CMMI users who are familiar with the products. CMMI V1.2 products, including CMMI for Development, V1.2 (the model),Standard CMMI Appraisal Method for Process Improvement (SCAMPISM), V1.2 (the appraisal method), and Introduction to CMMI, V1.2 (the &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/J0vKD_480xw" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/4288445927574648984/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=4288445927574648984" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/4288445927574648984?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/4288445927574648984?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/J0vKD_480xw/cmmi-v12-what-has-changed-and-why.html" title="CMMI V1.2: What Has Changed and Why" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/cmmi-v12-what-has-changed-and-why.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk4DR30yeSp7ImA9WxZTEE8.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-7595744032321338352</id><published>2008-01-10T20:10:00.000-08:00</published><updated>2008-01-10T20:16:16.391-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-10T20:16:16.391-08:00</app:edited><title>Connecting Software Industry Standards and Best Practices: Lean Six Sigma and CMMI</title><summary type="html">Integration of Six Sigma and the Capability Maturity Model Integration (CMMI) is becoming fairly widespread, yet confusion remains about their relationship.Part One of this article includes several case studies that answer some of the more common questions,Part Two describes the relationship of Lean Six Sigma and Six Sigma's approach to improvement of existing products and processes (Define, &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/zktogkDE9KQ" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/7595744032321338352/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=7595744032321338352" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/7595744032321338352?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/7595744032321338352?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/zktogkDE9KQ/connecting-software-industry-standards.html" title="Connecting Software Industry Standards and Best Practices: Lean Six Sigma and CMMI" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/connecting-software-industry-standards.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk4CR30-eCp7ImA9WxZTEE8.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-2280069429784040528</id><published>2008-01-10T20:06:00.000-08:00</published><updated>2008-01-10T20:16:06.350-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-10T20:16:06.350-08:00</app:edited><title>Process Improvement – Is it a Lottery?</title><summary type="html">This article provides an overview of the approach utilized to implement process improvement across its global organization without losing focus of its business drivers.It provides a practical overview of how over a four year period an organization moved from CMM® Level 1 to Level 3 and is currently transitioning to CMMI® Level 4.It will provide a candid insight including lessons learned and &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/5j5-gt8nw9c" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/2280069429784040528/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=2280069429784040528" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/2280069429784040528?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/2280069429784040528?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/5j5-gt8nw9c/process-improvement-is-it-lottery.html" title="Process Improvement – Is it a Lottery?" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/process-improvement-is-it-lottery.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk4FQ3k9eSp7ImA9WxZTEE8.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-5515844240957157792</id><published>2008-01-10T20:04:00.000-08:00</published><updated>2008-01-10T20:15:12.761-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-10T20:15:12.761-08:00</app:edited><title>Finding CM in CMMI</title><summary type="html">Configuration management (CM) acts as a central nervous system in system development, and is a prominent key process area and generic practice in Capability Maturity Model® Integration (CMMI®) and other maturity models. As such, implementing and improving CM in the company may seem like an overwhelming task.This article takes you through the requirements in CMMI step by step and offers practical &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/87SaNWuMYsM" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/5515844240957157792/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=5515844240957157792" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/5515844240957157792?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/5515844240957157792?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/87SaNWuMYsM/finding-cm-in-cmmi.html" title="Finding CM in CMMI" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/finding-cm-in-cmmi.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk4AQ3k7cCp7ImA9WxZTEE8.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-3036750079864132316</id><published>2008-01-10T20:01:00.001-08:00</published><updated>2008-01-10T20:15:42.708-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-10T20:15:42.708-08:00</app:edited><title>Relation Between CMMi and Six SIgma</title><summary type="html">Successfully implementing CMMI and Six Sigma together requires an understanding of the relationships between the two.This report contains a brief summary of each initiative and then outlines the connections between frameworks commonly used in Six Sigma and the CMMI process areas. Coupling this knowledge with a conscious strategy enables an organization to create tactical plans and specific &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/fYxqlHRCwIE" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/3036750079864132316/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=3036750079864132316" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/3036750079864132316?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/3036750079864132316?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/fYxqlHRCwIE/relation-between-cmmi-and-six-sigma.html" title="Relation Between CMMi and Six SIgma" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/relation-between-cmmi-and-six-sigma.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkAAR349eip7ImA9WB9aGUg.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-6279331808505386093</id><published>2008-01-10T00:32:00.000-08:00</published><updated>2008-01-10T00:45:46.062-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-10T00:45:46.062-08:00</app:edited><title>Basic Project Management Outline</title><summary type="html">A successful Project Manager must simultaneously manage the four basic elements of a project: resources, time, money, and most importantly, scope. All these elements are interrelated. Each must be managed effectively.All must be managed together if the project, and the project manager, is to be a success.Resources : People, equipment, materialTime : Task durations, dependencies, critical &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/nrU8llV_cac" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/6279331808505386093/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=6279331808505386093" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/6279331808505386093?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/6279331808505386093?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/nrU8llV_cac/part-1-basic-project-management-outline.html" title="Basic Project Management Outline" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/part-1-basic-project-management-outline.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEAGQHk-fCp7ImA9WB9aGEs.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-1603379065895028517</id><published>2008-01-09T00:13:00.000-08:00</published><updated>2008-01-09T00:18:41.754-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-09T00:18:41.754-08:00</app:edited><title>Quality-Process-Software-CMMI-ISO-SixSigma</title><summary type="html">Differences between Continuous and Staged Representations in CMMIhttp://www.sei.cmu.edu/cmmi/presentations/sepg05.presentations/cepeda-cmmi.pdfCMMI 1.2 for Development online - browser versionhttp://www.wibas.de/presentation/site/cmmi_1.2_browser.html.enThis is the link to see online version of CMMI 1.2 for developmenthttp://chrguibert.free.fr/cmmi12/text/index.phpWhat is not CMMI Level 4 and &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/u2igarh0XUI" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/1603379065895028517/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=1603379065895028517" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/1603379065895028517?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/1603379065895028517?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/u2igarh0XUI/quality-process-software-cmmi-iso.html" title="Quality-Process-Software-CMMI-ISO-SixSigma" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/quality-process-software-cmmi-iso.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEABR3YyeSp7ImA9WB9aGEs.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-5597356378351269032</id><published>2008-01-09T00:11:00.001-08:00</published><updated>2008-01-09T00:19:16.891-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-09T00:19:16.891-08:00</app:edited><title>Agile Methodologies and Related Links</title><summary type="html">http://www.extremeprogramming.org/ -eXtreameProgramminghttp://www.controlchaos.com/ - Scrumhttp://www.agilemetrics.com/ - Agilemetrics sitehttp://www.blueink.biz/RapidApplicationDevelopment.aspx RAD&lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/-y2gM6D2O7I" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/5597356378351269032/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=5597356378351269032" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/5597356378351269032?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/5597356378351269032?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/-y2gM6D2O7I/agile-methodologies-and-related-links.html" title="Agile Methodologies and Related Links" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/agile-methodologies-and-related-links.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D08HQHg-fip7ImA9WB9aGEs.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-7890648453352048254</id><published>2008-01-09T00:01:00.000-08:00</published><updated>2008-01-09T00:03:51.656-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-09T00:03:51.656-08:00</app:edited><title>Introduction to SoftwareEstimation</title><summary type="html">Estimation is done in terms of* Size*Effort* Schedule* CostSize estimate: This is thefirst estimation task. A measurement that tells the user what the system shalldo. Size estimate is usually done by Function Points Analysis, Feature points,Use Case points or Lines of Code (LOC). Effortestimate: The estimate for the manpower that is requiredfor a project. This is a most important factor &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/AGczXS_AOEA" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/7890648453352048254/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=7890648453352048254" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/7890648453352048254?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/7890648453352048254?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/AGczXS_AOEA/introduction-to-softwareestimation.html" title="Introduction to SoftwareEstimation" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/introduction-to-softwareestimation.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkYCQH0-eyp7ImA9WB9aGEo.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-3953089839293173574</id><published>2008-01-08T22:56:00.000-08:00</published><updated>2008-01-09T03:29:21.353-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-09T03:29:21.353-08:00</app:edited><title>Statistical process control (SPC)</title><summary type="html">Statistical process control (SPC) is a method for achieving quality control in manufacturing processes. It is a set of methods using statistical tools such as mean, variance and others, to detect whether the process observed is under control.HistoryStatistical process control was pioneered by Walter A. Shewhart and taken up by W. Edwards Deming with significant effect by the Americans during the &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/2mEb2CxB5PA" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/3953089839293173574/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=3953089839293173574" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/3953089839293173574?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/3953089839293173574?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/2mEb2CxB5PA/statistical-process-control-spc.html" title="Statistical process control (SPC)" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/statistical-process-control-spc.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkMASHY9eCp7ImA9WB9aGEs.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-7391031587674824653</id><published>2008-01-08T22:28:00.000-08:00</published><updated>2008-01-08T22:34:09.860-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-08T22:34:09.860-08:00</app:edited><title>Requirements Management and Enterprise Architecture</title><summary type="html">Requirements Management is the science and art of gathering and managing user, business, technical, functional requirements, and process requirements within a product development project. The project could be for a new consumer product, a web site, a system or a software application. In all these cases, the five classes of requirements should be represented. The objective of the Requirements &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/EeJ66LM-FGQ" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/7391031587674824653/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=7391031587674824653" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/7391031587674824653?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/7391031587674824653?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/EeJ66LM-FGQ/requirements-management-and-enterprise.html" title="Requirements Management and Enterprise Architecture" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/requirements-management-and-enterprise.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEMNQ3o-cCp7ImA9WB9aGEg.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-4784844911982936471</id><published>2008-01-08T21:22:00.000-08:00</published><updated>2008-01-08T21:28:12.458-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-08T21:28:12.458-08:00</app:edited><title>Six Sigma - Terms and Definitions</title><summary type="html">Jack Welch, former CEO of General Electric, and one of the most succesful corporate leaders ever, used Six Sigma as major Quality Improvement method.In his book Winning he writes:Six Sigma is one the biggest management innovations of the past 25 years. Six Sigma improves the development procedures, brings products faster to the market with less defects, and reduces cost. The biggest - but least &lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/XMA5eLg73W0" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/4784844911982936471/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=4784844911982936471" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/4784844911982936471?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/4784844911982936471?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/XMA5eLg73W0/jack-welch-former-ceo-of-general.html" title="Six Sigma - Terms and Definitions" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/jack-welch-former-ceo-of-general.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUIDQHo4eCp7ImA9WxZTEE8.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-7387741183406086282</id><published>2008-01-08T20:27:00.000-08:00</published><updated>2008-01-10T20:59:31.430-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-10T20:59:31.430-08:00</app:edited><title>Handling Late Requirements</title><summary type="html">Many of project issues are related to bad requirements management. One particular issue which is hard to tackle is the handling of late requirements.Coping with new requirements after the development has started often leads to problems in the project:Schedule, cost and scope of the running project become unknowndelays due to unsufficient impact investigation, which may propagate to other projects&lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/Bu7zodR1j10" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/7387741183406086282/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=7387741183406086282" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/7387741183406086282?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/7387741183406086282?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/Bu7zodR1j10/handling-late-requirements.html" title="Handling Late Requirements" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/handling-late-requirements.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEQFQnc8eip7ImA9WB9aGEg.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-2815632113466043463</id><published>2008-01-08T20:14:00.000-08:00</published><updated>2008-01-08T20:18:33.972-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-08T20:18:33.972-08:00</app:edited><title>Requirement Processes</title><summary type="html">Understand and communicate requirements that align out IT priorities with your business needs.No process is more fundamental than the process of defining and managing business and technical requirements. It's no surprise that studies cite inaccurate, incomplete, and mismanaged requirements as the primary reason for project failure.The Requirements-engineering process consists of two major domains&lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/GzyWpaP1FsM" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/2815632113466043463/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=2815632113466043463" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/2815632113466043463?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/2815632113466043463?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/GzyWpaP1FsM/requirement-processes.html" title="Requirement Processes" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/requirement-processes.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkcAQXw9fCp7ImA9WxZTEE8.&quot;"><id>tag:blogger.com,1999:blog-455849324211152711.post-7510483911847582428</id><published>2008-01-08T19:52:00.000-08:00</published><updated>2008-01-10T21:07:20.264-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2008-01-10T21:07:20.264-08:00</app:edited><title>6 Tips for Quickening Software Releases</title><summary type="html">MONTHLY NEWSLETTERJanuary 2008 - Pragmatic Software NewslettersTools for Managing the Software Development LifecycleSponsored Linkhttp://www.softwareplanner.com/Software Planner is an award winning web-based solution for managing the software life cycle. Tracks support tickets, customer requirements, defects, test cases and allows document sharing. Provides project management, with importing/&lt;img src="http://feeds.feedburner.com/~r/Q-Environment/~4/I_W_PCuwRwI" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://q-environment.blogspot.com/feeds/7510483911847582428/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=455849324211152711&amp;postID=7510483911847582428" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/7510483911847582428?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/455849324211152711/posts/default/7510483911847582428?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Q-Environment/~3/I_W_PCuwRwI/6-tips-for-quickening-software-releases.html" title="6 Tips for Quickening Software Releases" /><author><name>Chetan G.R</name><uri>http://www.blogger.com/profile/09512143056116035881</uri><email>chetangr@gmail.com</email><gd:extendedProperty name="OpenSocialUserId" value="06753547982401684917" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://q-environment.blogspot.com/2008/01/6-tips-for-quickening-software-releases.html</feedburner:origLink></entry></feed>
