I am currently charged with getting our testing formalised enough to obtain TickIT accreditation (obviously alongside the other development disciplines).
We currently do mostly exploratory testing due to lack of documented requirements. However this seems to me to be nowhere near enough for TickIT.
I am implementing the IEEE test documentation standards but realistically can't see people using it - or, if they do, I can't see a huge benefit. We don't do large projects, mainly small scale, often embedded ones.
We do sometimes test from use cases which we find most efficient (and that will satisfy TickIT as far as I understand its requirements).
Can anyone help me with any similar or related experiences? Or any thoughts at all.
Many thanks in advance.
"Even when the experts all agree, they may well be mistaken."
Well, I'm currently working on getting ISO9001 and TickIT certification for where I work too. I'm 'lucky' enough to be co-ordinating the whole thing, not just bringing the testing into line!!
Your major stumbling block seems to be the lack of documented requirements. Surely there must be something written down?
If you start with a spec then you should be able to associate a test plan and the test results with that spec. Our 'projects' also tend to be small, even tiny, but we have an in-house system we have developed to manage our projects and we have developed this to help us record who did what and when. Our system records which programs were changed and tested, what the test plan was, and how it was carried out, and whether bugs were found, and when these resolved. For small projects this is easily done within the system, for larger projects the specification documents are needed. If in doubt, record it. Traceability seems to be the key.
One problem we had seemed to be design reviews. I was told that we didn't appear to do them. But, of course, we did - its just that we didn't have the evidence. We will be ensuring that meeting dates and vital decisions are recorded.
Describing it like this it sounds simple! I hope this can provide some encouragement. However, one of the things I have found is that it is a cultural change and difficult to implement at times. It is all very well saying 'we are now going to record x, y, and z' the problems come because the staff were quite happy doing everything the old ways - which often relied on trust and common sense. They need to understand the changes.