I’ll be live blogging the SAO QAForum event, “The Role of QA in the Agile Environment”.
early feedback: I was able to use the restroom without touching any parts of the room. kudos to Kell’s.
speaker/ Greg Smith, GS Solutions Group
topic/ Ten Steps to Becoming Agile
“What is Agile?”
quecreek mining disaster is the opening story.
key aspects: time constraint, immediate adaptation, collaboration on ideas, feedback early and often.
better estimates ideas etc when WHOLE team is involved.
review of “The Traditional Lifecycle”
he missed the key advantage of “waterfall”
return to previous phase due to mistakes
he equates QA with Test
now were looking at mini-waterfall
“final iteration” is defined as customer sees enough value to release.
no review/retrospective for very short sprints.
where QA fits in:
feasibilty – not usually inc QA
release planning – painful meeting betwen team and PO
qa person is “just” the interviewer
S: apparently QA folks don’t add value to requirements definition
storey points – QA is involved, points are relative
Q: relative to what?
iteration 0 examines “foundational” issues
QA is separate from DEV and DEV is separate from both
agile vs traditional
most projects are some kind of hybrid, more traditional for government contracts.
moving to agile is like being on a half-pipe
scrum and xp are flavors of agile
scrum is a framework
scrummaster is a policeman “process management”
team is a bunch of specialist
www.dragile.com
my thoughts…
the author doesn’t understand QA
the author doesn’t understand phased development
the author doesn’t get team commitment to the project
