What is this scrum anyway?
Monday, 16. June 2008, 08:16:28
Ok, I know.. im old on the computer/it world... or.. well. sorta old.. been doing it the last 8 years now, with a direction against QA mostly, but also projectmanagement and group manager. I mean that Im quite comfortable in my clothing when it comes to QA and how to test things, however, Im completely fresh to this "scrum" business everyone is talking about.
When it comes to scrum, I really like the thinking about it and how it gives the thought controll back to the developers opposed giving the controll completely to the manager... However, with 2weeks sprints within scrum, Im sorta struggling with how to get the QA part of the scrum business working. A 'sprint' is a 2 week period where you have to complete a specific set of 'slices' which the dev decides to complete during a 2-4hour meeting. Each slice is a specific part(or goal) of the game/project which needs to be completed. A definition of a slice can for example be "Be able to run/control with a character inside the stadium and kicking/playing a ball"
That sounds fair enough you say? But what about from the QA side of things? How on earth should a QA be able to say that this definition for that slice is met? I mean, if you dont specify exactly what each thing in this highlevel definition is, how can I as a QA say that this is OK from a QA point of view? From the dev side, they can pretty much just put a qube which you control and you then just push a ball infront of you inside a big bowl and would still meet the definition of the slice...
Hmm.. Lets see what happends during the week =) I mean, what could possibly go wrong?
When it comes to scrum, I really like the thinking about it and how it gives the thought controll back to the developers opposed giving the controll completely to the manager... However, with 2weeks sprints within scrum, Im sorta struggling with how to get the QA part of the scrum business working. A 'sprint' is a 2 week period where you have to complete a specific set of 'slices' which the dev decides to complete during a 2-4hour meeting. Each slice is a specific part(or goal) of the game/project which needs to be completed. A definition of a slice can for example be "Be able to run/control with a character inside the stadium and kicking/playing a ball"
That sounds fair enough you say? But what about from the QA side of things? How on earth should a QA be able to say that this definition for that slice is met? I mean, if you dont specify exactly what each thing in this highlevel definition is, how can I as a QA say that this is OK from a QA point of view? From the dev side, they can pretty much just put a qube which you control and you then just push a ball infront of you inside a big bowl and would still meet the definition of the slice...
Hmm.. Lets see what happends during the week =) I mean, what could possibly go wrong?
WIDGETIZE