| bio | website | twitter.com/#!/yrizos |
|---|---|---|
| location | Thessaloniki, Greece | |
| age | 33 | |
| visits | member for | 2 years |
| seen | Dec 24 '12 at 13:03 | |
| stats | profile views | 3 |
You can find me in The Whiteboard.
|
Aug 9 |
awarded | Citizen Patrol |
|
Nov 10 |
awarded | Autobiographer |
|
Jul 5 |
awarded | Teacher |
|
Jun 11 |
comment |
Workflow shortcut to meet the release deadline Your question is wildly open to speculation. Can you give us a little bit more detail on what the actual process is in your organization and what exactly is expected from QA and from marketing? You are asking whether it's ok to take over some steps of the process, but don't tell us what steps those are. Is it complete lack of specifications? Why, in your opinion, does the process fail? |
|
Jun 11 |
comment |
Workflow shortcut to meet the release deadline @stuartf Yes, my bad. In that line I refer to gathering / creation as the very first steps towards the actual specs, which usually involve gathering input from clients / stakeholders, generating raw ideas, checking the competition etc, assuming that's what the OP had in mind (as what else could a marketing dept. actually do towards specs?). I think we need a lot of clarification on the question itself, its wildly open to speculation. |
|
Jun 10 |
comment |
Workflow shortcut to meet the release deadline @stuartf If this was a general discussion I'd agree with you, but the question is more along the lines "Should I take over specs creation?". And where do I suggest that a QA specialist should not get involved? Getting testing involved from the start is what requirements reviews are for, shaping requirements with your reviews does involve QA in the creation process. But completely taking over the creation process, that's not typically a good thing. Still, if the person is sufficiently talented, the wrong way may be the best way to go. |
|
Jun 10 |
answered | Workflow shortcut to meet the release deadline |
|
May 27 |
awarded | Supporter |