Page 17 - QDigitz

Q!Digitz Vol 1
Always Derive Quality themes and quality
strategies for the large program at the overall
account level. Never start at the team level to
establish quality goals. This is one mistake we do
when we support large programs for quality
assurance. We start o small- trying to de ne a
governance plan, tailoring of the processes,
establishing a measurement system etc for the
rst scrum team and then when another scrum
team onboards, we repeat the same process.
Slowly, we realize that what ts one team is not the defect status work ow while tracking defects.
tting another. And it leads to chaos in the middle
of the program execution. So always look at the
account/program understand what the Business
Organization and technology goals are and then
derive the Quality themes and strategy such that it
gets embedded within the overall account
strategy. When the themes are set at larger
program level, it ows in as quality goals to
individual scrum teams and the focus and
importance is in built into the processes itself. Eg:
De ne KPI for UI/UX teams or test automation
teams; Establish Feedback mechanism at various
levels, etc
DigitQ.in
Aug 2019
Design Ways of
Working across all
Agile Teams
While di erent Scaling models like SAFe, LeSS,
Nexus etc would provide guidance on what
practices needs to be de ned, how the team
needs to be structured, how the practices needs to
be implemented etc, as a quality professional we
still have a lot of work to do for setting up of Ways
of Working within the team.It starts right from
de ning and agreeing with all scrum masters,
product owners etc on what standards to follow
(eg: development framework, defect tool, testing
tool, etc) to de ning collaboration mechanisms for
various roles within the teams ( eg: between
solution architects, between Business analysts
etc).
It could also be simple things like what should be
For eg: if there is a visual board which is decided
to be used by one scrum team for tracking, ensure
it gets used in a similar fashion across all teams. It
will help remove many overheads during program
level metrics tracking.
Bigger the team, they require the better
facilitation skills to bring every stakeholder to the
table and agree on the Ways of working for the
team. It doesn’t just stop there, once it's agreed, it
becomes a prime responsibility for the QA
professional to determine how it needs to be
introduced to the newly added teams, how they
are trained, and how we monitor the quality and
progress throughout.