Timeline for Implementing new software development process
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:46 | history | edited | CommunityBot |
replaced http://pm.stackexchange.com/ with https://pm.stackexchange.com/
|
|
| Jun 2, 2012 at 11:03 | comment | added | Tiago Cardoso | Hi @aldrin, IMO, QA is a role, not a function. I see no problem having DEV-A QA'ing DEV-B work and DEV-B QA'ing DEV-A work. I"d go further, I'd say it's common for small projects. | |
| Jun 2, 2012 at 3:12 | comment | added | aldrin | i disagree with 'everyone uses several hats'. that's not necessary. else you'd expect the QA to develop too :) | |
| May 28, 2012 at 22:26 | comment | added | Tiago Cardoso | Exactly, @jmort253. The point is to make clear that if the project goes fine, everyone goes home happy. I'd say it would reinforce the idea of having anyone (not only devs) using as much hats as they could (in a productive way, of course). | |
| May 28, 2012 at 19:41 | comment | added | jmort253 | Not that I'm advocating incentive pay here, but if one were to offer incentive pay for a team, it could be for all people involved, dev, testing, the documentation group, etc. An everybody or nobody bonus could help bring people together, but of course there are problems with that approach too, if not implemented properly. | |
| May 28, 2012 at 12:36 | comment | added | Tiago Cardoso | One addition: maybe reinforcing that the 'developer performance' is related to the overall project success rather than the 'development success' may work... | |
| May 26, 2012 at 0:18 | comment | added | jmort253 | +1 - You're absolutely right about QA. Testing is a part of QA but not exclusively QA. In fact, QA is the responsibility of everyone, not just the testing team. | |
| May 25, 2012 at 23:31 | history | answered | Tiago Cardoso | CC BY-SA 3.0 |