[RFC] Software Process Improvement in Free Software, Closing the Quality Cycle, Inventing Non-Developer-Demotivating QA/QM/SPI
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi all,
as i see you try to maintain quality in debian efficently.
ive been thinking for months now about inventing and adopting
the SPI-standards cmm(x), spice, iso12207, and iso 9001,
etc, in free sw's lifecycles
and would like to ask you about comments and discussion.
discussion/research points:
1. closing and improving the spi/qm/qa- cycle with the developers by
analyzing their dev-processes, tools, configuration/analysis mngmnt and
give non-demotivating feedback with
- -what i call now- "CMP" ( Capability Maturity Points), scale 10-100 (log).
the classic industry way has shown up to be demotivating, developers
would avoid the system or even trick it off.
2. escape the megawave of developer->feature->bug->developer bad cycles
by targeting q-lacks at the beginning of a lifecyle leaving no stage
uncovered, just building a dam against the bug-hazard at the end
and maintaining old waterfall structures has shown up no more
sufficent -UNDEPENDENTLY- of the size and amount of sw-project(s).
3. research, collect and provide "best practices", not just scales.
. . .
y
tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.90 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iQCVAwUBQYXTt2qsze5HSzyoAQJzPwP9HfY0/ZwzUwMSegAx7HwolYpP3su+PLWS
345gPRfuTgtgqjcXmtu9qO3kQPxQ1LK5wprCjjFeR7bNar0GggZmSh40QITBJ9aw
w6Cw+aULdfX20rXIqDS8+QEiivtb7NrFLqrZ9s8Rcj4k7X0rSGjKdAtlKgk9XBIe
FFTnOrgALKI=
=s81J
-----END PGP SIGNATURE-----
Reply to: