<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>

<feed version="0.3" xml:lang="en-US" xmlns="http://purl.org/atom/ns#">
<link href="http://www.blogger.com/atom/8669453" rel="service.post" title="Thinking about Quality" type="application/atom+xml"/>
<link href="http://www.blogger.com/atom/8669453" rel="service.feed" title="Thinking about Quality" type="application/atom+xml"/>
<title mode="escaped" type="text/html">Thinking about Quality</title>
<tagline mode="escaped" type="text/html">Reflections on the relationship between quality, people and process in the development of complex software systems.</tagline>
<link href="http://www.hempelpai.com/work/" rel="alternate" title="Thinking about Quality" type="text/html"/>
<id>tag:blogger.com,1999:blog-8669453</id>
<modified>2005-05-12T01:49:38Z</modified>
<generator url="http://www.blogger.com/" version="5.15">Blogger</generator>
<info mode="xml" type="text/html">
<div xmlns="http://www.w3.org/1999/xhtml">This is an Atom formatted XML site feed. It is intended to be viewed in a Newsreader or syndicated to another site. Please visit the <a href="http://help.blogger.com/bin/answer.py?answer=697">Blogger Help</a> for more info.</div>
</info>
<entry xmlns="http://purl.org/atom/ns#">
<link href="http://www.blogger.com/atom/8669453/111586257865973146" rel="service.edit" title="Knowing you have a problem" type="application/atom+xml"/>
<author>
<name>Thomas</name>
</author>
<issued>2005-05-11T17:45:00-07:00</issued>
<modified>2005-05-12T01:49:38Z</modified>
<created>2005-05-12T01:49:38Z</created>
<link href="http://hempelpai.com/work/archive/2005_05_01_archive.html#111586257865973146" rel="alternate" title="Knowing you have a problem" type="text/html"/>
<id>tag:blogger.com,1999:blog-8669453.post-111586257865973146</id>
<title mode="escaped" type="text/html">Knowing you have a problem</title>
<summary type="application/xhtml+xml" xml:base="http://www.hempelpai.com/work/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml">It's said that the first step towards recovering from an addiction is to admit that you have one. This idea applies squarely to change management. If a new idea is being introduced into an organization, frequently it starts in some part of the organization where the team has had the collectively realization, that we have a problem. Once that realization occurs there is a natural receptivity</div>
</summary>
</entry>
<entry xmlns="http://purl.org/atom/ns#">
<link href="http://www.blogger.com/atom/8669453/111552308733768006" rel="service.edit" title="Intellectual Property Protection for offshore development" type="application/atom+xml"/>
<author>
<name>Thomas</name>
</author>
<issued>2005-05-07T19:55:00-07:00</issued>
<modified>2005-05-08T03:31:27Z</modified>
<created>2005-05-08T03:31:27Z</created>
<link href="http://hempelpai.com/work/archive/2005_05_01_archive.html#111552308733768006" rel="alternate" title="Intellectual Property Protection for offshore development" type="text/html"/>
<id>tag:blogger.com,1999:blog-8669453.post-111552308733768006</id>
<title mode="escaped" type="text/html">Intellectual Property Protection for offshore development</title>
<summary type="application/xhtml+xml" xml:base="http://www.hempelpai.com/work/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml">One of the big challenges with offshore development is protection of intellectual property. Of course intellectual property protection is a major issue for onshore development too. Domestically there are two main layers of protection: internal controls, and legal controls. Internal controls are by their nature preventive, whereas the legal controls are remediative. The problem is that with</div>
</summary>
</entry>
<entry xmlns="http://purl.org/atom/ns#">
<link href="http://www.blogger.com/atom/8669453/111543345108368035" rel="service.edit" title="A short break while we ship" type="application/atom+xml"/>
<author>
<name>Thomas</name>
</author>
<issued>2005-05-06T19:28:00-07:00</issued>
<modified>2005-05-07T02:37:31Z</modified>
<created>2005-05-07T02:37:31Z</created>
<link href="http://hempelpai.com/work/archive/2005_05_01_archive.html#111543345108368035" rel="alternate" title="A short break while we ship" type="text/html"/>
<id>tag:blogger.com,1999:blog-8669453.post-111543345108368035</id>
<title mode="escaped" type="text/html">A short break while we ship</title>
<summary type="application/xhtml+xml" xml:base="http://www.hempelpai.com/work/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml">I've been a busy a bit while we shipped our latest release. Like all endgames, it was a lot of work. However, it felt much different from previous releases. In particular, the focus we've had via our agile process on keeping the system running at all times really paid off towards the end. Rather than a frantic rush to kill large piles of fundamental defects, things were really quite measured and</div>
</summary>
</entry>
<entry xmlns="http://purl.org/atom/ns#">
<link href="http://www.blogger.com/atom/8669453/111189768109073307" rel="service.edit" title="Perceived Software Quality Introduced" type="application/atom+xml"/>
<author>
<name>Thomas</name>
</author>
<issued>2005-03-26T19:59:00-08:00</issued>
<modified>2005-03-27T04:28:01Z</modified>
<created>2005-03-27T04:28:01Z</created>
<link href="http://hempelpai.com/work/archive/2005_03_01_archive.html#111189768109073307" rel="alternate" title="Perceived Software Quality Introduced" type="text/html"/>
<id>tag:blogger.com,1999:blog-8669453.post-111189768109073307</id>
<title mode="escaped" type="text/html">Perceived Software Quality Introduced</title>
<summary type="application/xhtml+xml" xml:base="http://www.hempelpai.com/work/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml">All competent companies engage in testing of their software. When this testing is completed, and the software meets the agreed upon quality criteria, the software is viewed as being good enough to release to customers. Let's dissect this further. Typically a quality plan specifies a basic set of regression tests describing the base functionality of a product, a set of new test cases for new</div>
</summary>
</entry>
</feed>
