Topic: Embedded QA in Scrum
Objectives:
Traditional QA started during post-Alpha in a
traditional waterfall approach to vigorously test the software once all the
features were implemented. Alpha phase had been the first real chance to test
the software in some form which is near its final state. This often raises the
desire to change things even more. This and many more examples where
discovering product value at the end of the project.
Additionally, QA was underused. QA folks would be
either unclear at not having their insights into the software ("it's too
late to change the software based on your suggestions") or their role
would be so undervalued in some cases that people would be literally hired off
the street to fill the role.
Then the next approach was using Scrum for 3-4 weeks
before it even occurred to reconsider QA. Scrum was about mixing things up. The
word is taken from Rugby where the team moves the ball as a group. So the
question is why separate QA into a separate department that doesn't Scrum with
to produce a vertical and complete slice of the software? Initially it could be slow at times, but
eventually it should be successful.
The Scrum and the tackle are the two really
contentious areas of the game. If you get those aspects rightmost rugby matches
will work in your favors.” – Allan Lewis
So the best idea would be to start embedding QA into
the Scrum team. They will sit together, have open discussion together, Analyze
Design, Provide End User cases before Coding starts. They will get their hands
a lot more dirty. Sometimes QA will be expected to do a bit of coding,
designing layout and also having part time associate producer roles, but their
main job will be to exercise functionality as well as Drive and design
Acceptance Tests.
Embedded QA will help in validating each story once
it is resolved during a sprint. It will focus on validating the acceptance
criteria of the Story. Also Embedded QA will ensure what was working previously
is still working. The Quality will now not only be sole responsibility of QA
but will be of whole scrum Team.
In this presentation I would like to showcase how embedded
QA can help any software industry Better the quality higher the customer
satisfaction and increase in sales, QA is the person who gives assurance of
quality of product. So role of QA is becoming more critical in modern Software
Development Life Cycles like Scrum.
Target Audience:
Embedded QA in scrum will beneficial to any person involved in Application development.
Session Length:
This session will comprise of presentation, followed
by questions and answers. Over all session length will be 60 minutes.
Overview:
Traditional QA started during post-Alpha in a
traditional waterfall approach to vigorously test the software once all the
features were implemented. Alpha phase had been the first real chance to test
the software in some form which is near its final state. This often raises the
desire to change things even more. This and many more examples where
discovering product value at the end of the project.
Additionally, QA was
underused. QA folks would be either unclear at not having their insights into
the software ("it's too late to change the software based on your
suggestions") or their role would be so undervalued in some cases that
people would be literally hired off the street to fill the role.
Then the next
approach was using Scrum for 3-4 weeks before it even occurred to reconsider
QA. Scrum was about mixing things up. The word is taken from Rugby where the
team moves the ball as a group. So the question is why separate QA into a
separate department that doesn't Scrum with to produce a vertical and complete
slice of the software? Initially it
could be slow at times, but eventually it should be successful.
The Scrum and the
tackle are the two really contentious areas of the game. If you get those
aspects rightmost rugby matches will work in your favors.” – Allan Lewis
So the best idea
would be to start embedding QA into the Scrum team. They will sit together,
have open discussion together, Analyze Design, Provide End User cases before
Coding starts. They will get their hands a lot more dirty. Sometimes QA will be
expected to do a bit of coding, designing layout and also having part time
associate producer roles, but their main job will be to exercise functionality
as well as Drive and design Acceptance Tests.
Embedded QA will help
in validating each story once it is resolved during a sprint. It will focus on
validating the acceptance criteria of the Story. Also Embedded QA will ensure
what was working previously is still working. The Quality will now not only be
sole responsibility of QA but will be of whole scrum Team.
Better the quality
higher the customer satisfaction and increase in sales, QA is the person who
gives assurance of quality of product. So role of QA is becoming more critical
in modern Software Development Life Cycles like Scrum.
Implementation of
Embedded QA:
Each Team should be
cross-functional and should contain DEV, QA, and PM and if possible Architects
too. Each member of the team is wholly responsible for the quality of the
features they produce. However, each one has different roles in those teams –
it’s not that a developer and QA are interchangeable. Oversimplified – the
dev.’s role is to produce a high-quality feature; the QA’s to enable them to do
it; the PM’s to ensure that the team is building the right thing. It should be
ensured that every member of the team understands the actual purpose of the
feature and the goals/skills of the people who will be using it.
Diagram 4
A QA engineer will
have multiple points at which he or she provides input into the way the story
is developed and tested – providing every form of quality improvement.
Challenges:
To create a high performing Agile team, a lot of
collaboration is required. One of the challenges when it comes to collaboration
on Agile teams is that testing is no longer the domain of a quality team. It is
everybody’s responsibility.
Speakers:
Chaithra Thimmappa is a Manager EngineeringShe has technical
knowledge in Storage Domain working with leading technology companies like EMC,
NetApp, Brocade and VMware. Currently she is involved in Leading Professional
Services Application Solutions QA group.
She
has achieved many awards as follows:
§ EMC Knowledge Sharing
white paper selection for publishing in article
§ Part of WOmen in leadership comitee inside EMC(RISE program)
