Which areas of CMMi are relevant to a tester?
The process areas of Verification, Validation, Causal analysis and resolution are most relevant to the tester
Depends on what you want to achieve as a tester... For me, most of the process areas have some relevant links for the tester.
At a level 2, I think of the following:
Test managers might be very much interested in the process areas project planning, and project monitoring and control.
A tester that helps during the requirements management process will ensure that he/she is informed on the changes of the requirements so he'll know when an update is required to the test strategy, test cases, and other test documentation.
Configuration Management will help to provide the tester with a stable test environment. Help from the 'tester' will ensure that the CM system fits their needs.
Measurement and Analysis will help testers to identify the critical measures to follow up their testing. When is more testing required? When can we stop testing? Is the testing project getting out of hand? etc.
In fact, I think all level 2 process areas help the tester. After all, level 2 is about managing a project. And if a project is badly managed, the tester, very often coming late in the development cycle, receives less time to do more testing. So personnally I try to get involved and provide "the testers point of view".
At level 3, Kuldeep Chawla already mentioned Verification and Validation. But doesn't testing has a lot to do with risk? So I would certainly add Risk Management.
I'll not continue with the other process areas. I think you get my point. A tester that wants to do more than executing test scenarios is a very flexible person and will be interested in a lot more than verification and validation.
Just go through the different process areas with the testers mindset and you'll be amazed what CMMI has to offer. Although not detailed, but it makes a person think. And that is the goal of the model. Not to give all the answers, but make people think about solutions that work in their own environment.
Wow! That was really cool.
When we look into CMMI from a Tester point of view, I am sure you have lot many areas which tester need to work on, eventhough it looks like its not related directly to testing.
For sure CMMI is about tailoring CMMI to suit it best for ur organization.
The following paragraph posted by Steve says it all.....
<font size="2" face="Verdana, Arial, Helvetica">
Originally posted by Steven Deneir:
Not to give all the answers, but make people think about solutions that work in their own environment.
[i]Work Like u don't need Money...Love like u have never been Hurt...Dance Like Nobody is Watching...Sing Like Nobody is Listening...Live like its Heaven on Earth!
I just finished the Introduction Course of CMMI (although I'm working with the model since quite some time, but it is required to be part of an appraisal team, so...)
And I often say it to people: every word in the CMMI model is carefully choosen and has its meaning. So again, I learned some interesting things.
I never really paid attention to it (because I mainly focussed on level 2), but in the process area Technical Solution, unit testing is addressed. And in the process area Product Integration, it is all about integration testing. System testing is tackled in Verification.