Timeline for What types of positions might involve improving processes using CMMI and Scrum?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 9, 2012 at 17:24 | comment | added | rjzii | @altern - We are in the process of implementing the CMMI standard from scratch so I've been reading through the report. Odds are when things are all said and done there might be a bit of an organizational change so that Release Engineering and Quality Assurance are under some Quality Control umbrella but that is above my pay-grade. :) | |
| Feb 9, 2012 at 17:22 | history | edited | rjzii | CC BY-SA 3.0 | added 67 characters in body |
| Feb 9, 2012 at 17:16 | comment | added | altern | Probably you're right about the bias :) But it is worth mentioning that your company has common misunderstanding about what the QA is. Making sure software works correctly is QC (Quality Control) and covered by the Verification (sometimes Validation) process area from CMMI standard. QA covers them all. Give me some time and I'll show you some proofs of my point. | |
| Feb 9, 2012 at 17:12 | comment | added | rjzii | @altern - I think we might be being a bit biased because of how our companies are organized. :) Where I am we (Release Engineering) are in charge of the process improvement and QA is limited more to making sure the software works correctly. | |
| Feb 9, 2012 at 17:03 | comment | added | altern | I perfectly understand what is the responsibility of Release Engineering because currently I'm on the same position :) And that's why I argue with you - I know that doing my job I do not cover general issue of software quality even though I help to improve it. I also worked as QA (being release/configuration manager allowed me to), and it was completely different kind of tasks, they were more "high-level" and covered more broad picture than only release engineering. | |
| Feb 9, 2012 at 16:56 | comment | added | rjzii | @altern - Where I am Release Engineering is responsible for managing the build process, process overlays, and providing automation support to Quality Assurance (i.e. manual testing and review of products) in addition to managing what actually goes out the door. | |
| Feb 9, 2012 at 16:51 | comment | added | altern | Release Management is focused on providing successful release for the particular project(s), while Quality Assurance is focused on overall improvement of software processes (and, therefore, quality) throughout whole organization. At least this how it was at the organization I recently worked for. And it seems more logical for me to have Quality Assurance department be responsible of quality on all company levels. BTW, see my answer here: programmers.stackexchange.com/a/134229/44188 | |
| Feb 9, 2012 at 16:50 | history | edited | rjzii | CC BY-SA 3.0 | Expanded the answer a bit. |
| Feb 9, 2012 at 16:45 | comment | added | rjzii | @altern - Release Engineering is not the same as Release Management although the a release engineering group might be in charge of release management. Plus companies might do things differently, where I am the release engineering group is assuming responsibility for the builds and the software development process standards. | |
| Feb 9, 2012 at 16:39 | comment | added | altern | Release Management has nothing to do with CMMI and related stuff. This is the task of upper management and QA engineers. Configuration Management (and, therefore, release management) is only one of 22 process areas described by CMMI. Release manager deals with a subset of responsibilities QA engineer should be in charge of. | |
| Feb 9, 2012 at 14:20 | vote | accept | Aki | ||
| Feb 9, 2012 at 17:41 | |||||
| Feb 9, 2012 at 14:15 | history | answered | rjzii | CC BY-SA 3.0 |