|
|
|
|
|
|
|
Quality Standards Intelligoe adheres to the international standard known as SPICE
or Software Process We commit to: Zero defects: " The customer expects a perfect job from us. Even in teams that already have wonderful commitment to quality, some folks are scared of promising zero defects... but that's what we expect from others. And any tiny defect can blow the reputation of the whole system, in the user's eyes. (This is the cockroach theory: if you see a roach in a restaurant, you don't say "There's the roach in this place." You say, "Let's get out of here, this place is infested.") Proceed systematically: Architecture, procedures, well-reviewed designs, high-level languages and discipline for using them, plans for thorough testing, and measurement of results are all evidence for a development process that's under control. In addition, the team should have documented methods for design, defect prevention, and inline testing, and tools to mechanize these. Check everything: Every work product should be checked somehow. Most teams review designs, review source code, and test compiled code. The principle can be applied to other things we do for a "client" anywhere that quality might suffer. If this principle becomes part of our culture, each step can concentrate on preventing or removing its own defects, counting on clean input from the prior step. Improve continuously: If we do all the above, it won't be enough. We need to learn from our mistakes, look for better ways, question authority. Our methods and processes have to keep evolving to meet changing conditions.
|
|
Send mail to intelligoe2002@yahoo.com with
questions or comments about this web site.
|