Smart se seminar agile quality cybozu session en

We compared and discussed
agile QA in the field with the
QA2AQ pattern.
SMART SE SEMINAR SERIES
THINKING ABOUT SOFTWARE ENGINEERING IN THE POST -CORONA
ERA.
PART 6: AGILE DEVELOPMENT AND QUALITY
2020/8/20 CYBOZU INC. COPYRIGHT © ATSUSHI NAGATA 1
Cybozu Corporation
QA Community
Atsushi Nagata

QA2AQ Pattern Study Group in Cybozu
Objective
Learn the patterns.
Compare them with our QA activities, we find
exactly same, slightly different, we didn’t do it.
We don’t intent to do the same pattern as it is.
Discuss, learn, and consider your own next activities.
Procedures.
• Explan the QA2AQ pattern, questions and answers
Throw the question to the participants.
Example: so what are you doing?

achievements
6 study sessions
Part 1: Introduction
Second: Pattern: "Dismantling the Barriers"
Second: Pattern: “Whole Team."
Fourth: Pattern: “Integrate Quality"
Part 5: Patterns: "Agile Quality Processes"
continued
Part 6: Review of the Presentation of the Smart SE
seminar.

Pattern: "Break Down Barriers"
A lot of problems can arise when QA people are not part of the development
team (the "us" vs. "them" syndrome) How do you integrate QA people into
an agile team?
problem
solution
In an agile quality team, it's important to include a QA person as part of the
agile team from the beginning.
Pattern : Break Down Barriers

“Break Down Barriers" at Cybozu
· 2017/2 Nagata Introduced Agile QA (DevQA) at Cybozu
· 2018/2 Cybozu Meetup #11 Agile QA
I was invited and saw some presentations of the cases of Agile QA of Cybozu.
I was surprised that Cybozu had implemented DevQA in one year.
Although there were still the release decision meetings (the quality gate).
· 2019/2 Development organization reorganization:
· No longer a QA department or no quality gate
QA did not have a responsibility of Quality, but the whole team does.
QA people is a member of the development team as a quality specialist.
QA Community was established.
QA people are very much alive and working their jobs and enjoy trying
improvement.

DevQA : Quality Feedback Loop
design QA
Message of Qualities.
Quality Visualization
▪ Review
▪ test
▪ measurement
support
Deploy Evaluation Environment
implicit sharing
risk
task
action
relationship of trust
Information provided by Quality Feedback
(Development, PO)
Quality Feedback
https://www.slideshare.net/POStudy/devqa-qa-postudy

Pattern: “Whole Team"
How can an agile team remove such barriers and make quality even more
agile?
problem
solution
Break down barriers and barriers to communication through a variety of
actions, including the inclusion of QA at an early stage.
Pattern : Whole Team

I asked them a question.
QA writes a lot of documentation because it's their deliverable. Particularly
important are the quality reports to their supervisors.
So what are the deliverables in Agile QA?
question
Answer.
I still think the test specs are an artifact!
I was naively aware that the development products (programs) were also the
product of QA.
This development will also include specifications (as we will be testing them as well).
I was aware that the byproducts produced in the process of creating this product
were the test results left in kintone, etc.
I believe that the deliverables are the version of the product we are releasing.
I think it's a product of QA, or rather, the entire development team is creating a
single product.

Whole Team
I was aware that the development
product (program) was also a
product of QA.
I think the deliverable code is a
product of QA, or rather, the entire
development team is creating a single
product.

Pattern: "Integrate Quality"
How do you incorporate critical system quality assessments into your agile
processes and where should QA professionals go in the process?
problem
solution
Build a way to understand, describe, develop and test system quality as part
of the agile process.
Pattern : Integrate Quality

Treatment of Quality in Scrum

Integrate Quality
sprintrequirements behaviour
Where do you notice and
specify the qualities?
What is that qualities
implemented in?
Where do you share that
qualities with your team?
Where and how to evaluate
that qualities.
Ready Done.

Examples of agile processes
In the case of kintone

Refinement
Requirements Process: Practices that improve the quality of the backlog and make it Ready
Objective
Background and Reason
User Story
Acceptance Criteria
Describe
backlogs question estimate
PBI
Ready
sprintsprint sprint
Delphi
Notice and specify
the Qualities
Quality
Implementation
QA Dev
PO
PO
Dev
Improve the
quality of
backlogs
Identify development
perspectives and risks
PO
Refinement is working in parallel with sprinting.
Modify
Modify

sprint
development process
PBI
Done.
Sprint
Planning 2
Risk
Identification
task
plan
Acceptance
Test Design
Specification
modification
Product Backlog Items
Design, implementation and testing
Sprint
Review
Sprint
Panning 1
Backlog
Description
Assignment
Task Execution
Mob Activity

Planning 2
backlog
Task
Design
test
implementation
Task
Execution
RiskIdentification
QA
Dev
TestDesignReview
Specificationcreationand
review
PO
UI Design
Risk
list
Specification
document
design
acceptance
test
Test
Execution
Sharing Quality
Sharing
Quality
Formalizing
Shared
Qualities
Quality
Implantation
Quality.
Evaluation

Integrate Quality
There are feedback loops throughout the agile process to
"integrate" quality.
Notice
Specify
Share
ImplementationEvaluation
learning
As quality specialists, the QA team implement the qualities by
noticing it, feeding it back and sharing it with the team.
QA evaluate the products and learns as a specialist.

Summery
Pattern : Break Down Barriers
Pattern : Whole Team
Pattern : Integrate Quality
At Cybozu, when we were introducing Scrum, we were wondering how to go about QA.
I introduced them to a feedback model called DevQA, and QA took these two patterns and
showed me within a year. And a year later, the company organization also became a
Whole Team pattern.
This very quick change was due to the mentality and culture of Cybozu, which I will show
later.
In the diagram of Scrum on P11, it looks like QA is embedding quality using various
patterns and then feeding it back to Quality Testing.
However, at Cybozu, we use feedback everywhere in a more agile way, and our
perspectives and ways of thinking change as we realize and learn from the feedback. As a
consequence, the quality of the backlog, specifications, code and test design improves.
And those feedback loops work as agile processes.

Mentality
• The Power to Change
• Embrace change.
• Change their values by learning.
• Have respect for the other person.
• Trust each other.
• The courage to try.
• The courage to dive into something new.
• The power of ingenuity.
• Recognize and summarize issues and
come up with responses to them.
Heart of Improvement (Evolutionary)

Foundational Culture in Cybozu
Psychological Safety
Equality of speech
Agile Leadership Training 1: Michael Sahota, Audree Sahota
Open mind

The Agile QA Mentality
The deliverable product is also a product of
QA, or rather, the entire development team is
creating a product.
This is what I learned through the workshop in the QA2AQ study group.

Thank you very much
for your attention.
Cybozu
QA Community
Atsushi Nagata

Smart se seminar agile quality cybozu session en

More Related Content

What's hot

Similar to Smart se seminar agile quality cybozu session en

More from atsushi nagata

Recently uploaded

Smart se seminar agile quality cybozu session en