Skip to main content

Hygiene Processes

There are certain actions that we do, like getting vaccinated or washing hands (preferably with soap) before touching food items or taking some precautions (apply insect repellant) when we trek.

Getting vaccinated against a disease is expected to prevent a person from not getting the disease. Applying insect repellant ensures that a person, gets lesser number  / does not get any insect bites. In both the scenarios, the success is measured by what did not happen.

If we think about the above in detail, we realize that the same categorization can also apply to the processes that we follow. Not all the processes help us to take our product, its quality or other important parameters of interest to a different level.

Certain processes* just* ensure that we stay at the same level or don't slip from the current position. We can use the term hygiene process to denote such processes.

Thinking deep about this concept will reveal the following.
  • Hygiene processes are equivalent to the foundation of a building and are just as important as any other process in the process hierarchy.
  • These processes are hidden beneath more important process and many a times don't get the importance that they deserve.
  • Any process definition should first identify the hygiene processes.
  • Embarking on process improvements without identifying, ensuring that the hygiene processes are in place and followed, always leads to failure.
  • Hygiene processes need not always be basic processes.
  • Hygiene Processes can also be those that help us to maintain a certain state or level or quality of our deliverables.
  • Hygiene process definition is a very relative definition and differs from company to company or system to system.
  • What is state of the art process for a system can be Hygiene process for another system (at a different maturity/capability level).


Popular posts from this blog

Kano Model of Customer Satisfaction - Notes to Self

Note: What follows is the notes taken from my study of Kano's model of Customer Satisfaction. I came across this model when i wanted to know if there was a structured approach that would help me prioritize features for software product development. 

To evaluate a product or service, following parameters are very important

The value provided - this helps attract customersThe Quality offered - This earns customer respectProduct or Service innovation - This helps differentiate from competition
But these are not perceived directly, but indirectly through the product and it's features. Kano's model help to group product features into 3 categories ( 6 categories, but only 3 are important) and there by makes it feasible to deliver value at a promised quality while offering innovation. 

The 3 important feature categories are 
Basic featuresLinear featuresExciters or DelightersBasic features are that must be present in the product to be successful. They are also referred to as must have…

Knowns, Unknowns and Project Management...

This article is a draft of a paper i started to write in september 2007 and left it where you see it today.  The purpose is to to come out with a conceptual framework through which “the knowledge needed to successfully execute a project” can be viewed and gauged and presents a brief outline of the same. As always comments are most welcome...
Financial Resources, Domain, Technology, Communication, Cultural Differences, Organizational Structure, Organizational Culture and Power Play within an organization are some of the factors that have an ultimate bearing on the success of a project.
All projects come in shades of grey is a fact that has to be acknowledged. For example, when we start a project, very rarely do we know everything about Project Requirement, Scope and other factors that impact the project. There will be lot of ambiguity and this ambiguity has to be accepted and put to proper use.
But the problem is that people usually look at these factors in black and white. This may be ac…

Aggressive Schedules - Few thoughts...

During my early years in the software industry, i used to look at people who worked in projects with aggressive schedules, in awe. The people working in such projects talked about, long hours, working week ends and heroic endeavors in their projects. The people who worked in such projects were given more awards and rewards, compared to others. i thought that this was the way to be.

After working in projects with aggressive schedules, I realized that what I saw was only the silver lining and there was a big dark cloud behind this ( talk about what experience can do for you). The common thread that linked all the projects was that all of them exhibited one or more of the following.
Project ended up delayed by more than 100% Project got cancelled Project got de-scopedProject has a high cost of maintenance.  Having been burnt up by working in projects with “Aggressive Schedules’, (henceforth denoted as AS), I understand that projects with aggressive schedules cause more damage than what we …