Hi Mechtilde,
Mechtilde wrote:
Hello,
Thorsten Ziehm schrieb:
Hi Andre,
first of all, thank you for summarizing the discussion from the German
mailing list and bring it into the international lists.
André Schnabel wrote:
[...]
This Quality Management is (imo) the missing link. Nobody seems to be
(or even willing to be) in charge of this.
Here I have a different conclusion. There exists a Quality Management.
You can find a mass of information for processes for bug handling,
working in QA project, making testing and QA and what is needed for
working in the QA project. So there are a mass of information inside
the QA project (on qa.openffice.org or in the Quality Assurance part
in ooo-wiki). Therefore a Quality Management for OOo exists, I think.
But this wasn't updated in the past years. Perhaps we need new adopted
processes, need other information etc.
Quality Management means to mangage the process of QA and development
this means an *active* process and not some websites or papers.
Perhaps here are misunderstandings again :
I understand Quality Management as something like :
"Quality management can be considered to have three main components:
quality control, quality assurance and quality improvement. Quality
management is focused not only on product quality, but also the means to
achieve it. Quality management therefore uses quality assurance and
control of processes as well as products to achieve more consistent
quality."
=> http://en.wikipedia.org/wiki/Quality_Management
so my idea is a better *active* flow of information between QA and
development and reverse.
More communication is needed, I am on your side. But how? Without
defining ways, we cannot handle such mass of work with the whole
community.
Here we have to work together to find out, what information has to be
changed or is missing. For example we have to work together to find a
way how to handle the mass of open issues. This will not be an easy
task. ;-) I do not have any solution.
My suggestion is that members of the QA Team described at [1] to [8]
should have there responsibilities of the development.
This should lead to have influence of the priority of issues.
On the other side new code can easier be tested because development know
how can do this.
A good communication minimized the missunderstanding about problems.
We need not only short ways by Sun internal but also between development
and QA for Quality Management. IRC and direct mails are good tools.
Some good points. But how this can be realized with all community
members?
The Base Team is there on a good way.
Why do you think this is a good example?
-> good quality of the application
-> less regressions
-> less bugs
-> good communication
-> ...
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
