Hi Mathias,
Mathias Bauer wrote:
Possibly we can establish a process that allows for more "asynchronous"
work or creates the documentation in a "Q&A" style (QA or documentation
ask for the information they need instead of forcing the developers to
provide everything upfront).
As some of us have desribed in a presentation [1] (slide 12+ is the
i-Team work described -> How to write a specification) held on OOoCon
[2] the i-Team should work together on the specification because they
are the stakeholder for the document.
If there are information included in a specification which is not needed by
- developer (also developer who will work afterwards with the
implementation!)
- tester
- documentation people
then it makes no sense in the document.
I hear "lightweight" specification document from many people but mostly
I thnk you mean "lightweight specification PROCESS" because in the
doucment there should be no information which is not helpful for DEV,
QA, DOC!
The specification process [3] and issue handling [4] only has been
written down and not being changed. If there are intersted people in
doing it -> [EMAIL PROTECTED] will be your right place. We want
to do it and it should match the needs of DEV, QA, DOC - surely! :-)
Have fun,
Jogi
[1]
http://marketing.openoffice.org/ooocon2006/presentations/wednesday_c12.odp
[2]
http://marketing.openoffice.org/ooocon2006/schedule/community_abstracts.html#c12
[3] http://wiki.services.openoffice.org/wiki/Category:Specification
[4]
http://qa.openoffice.org/issue_handling/workflowcharts/taskhandling_workflow_feature_specification.html
--
===============================================================
Sun Microsystems GmbH Joerg Sievers
20097 Hamburg Quality Assurance Engineer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
