This paper suggests how to introduce software quality assurance (QA) and measurement practices where they might most easily be accepted without taking mainstream development tasks head-on. The paper begins by describing an in-the-small, limited resource ("guerrilla") approach and the context in which it is applied. QA and measurement practices are recommended which support one another and encourage data-centered decision-making. Implementation behaviors to avoid are noted to reduce the resistance faced when introducing such practices flow.
Adequate resources and senior management commitment are oft-cited prerequisites to successful process/quality improvement activities. What if you have neither? The metaphor of guerrilla fighters seems appropriate for the inch-by-inch "underground" effort which can characterize in-the-small process/quality change attempts.
This paper suggests how to introduce software quality assurance (QA) and measurement practices where they might most easily be accepted without taking mainstream development tasks head-on. The paper begins by describing an in-the-small, limited resource ("guerrilla") approach and the context in which it is applied. QA and measurement practices are recommended which support one another and encourage data-centered decision-making. Implementation behaviors to avoid are noted to reduce the resistance faced when introducing such practices flow.
