QA Fest 2019. Яна Лыса. Особенности управления процессами тестирования для удаленных команд

Тема доклада
KYIV 2019
Yana Lysa
Managing testing processes for
remote teams
QA CONFERENCE #1 IN UKRAINE

WITH PASSION TO QUALITY
About me
QA CONFERENCE #1 IN UKRAINE KYIV 2019
QA work experience 7 years
QA Lead experience 3 years
Remote experience 4 years
ISTQB certified Test Manager and Test Analyst
Current position: QA Coordinator at
Access Softek, Inc.
ylysa@accesssoftek.com

Classical vision of remote employee

Our QA team structure
QA Manager
Head of
Coordinators
QA
Coordinator
QA Lead Regular QA
QA Lead Regular QA
QA
Coordinator
QA Lead Regular QA
QA Lead Regular QA

Sprint in remote team vs. sprint in office
Activities Remote team risks comparing with office work
Estimation process
and
New features discussion
-Time zones;
- Miscommunication and misunderstanding;
- Not enough investigation before estimation
Project documentation - Not enough documentation;
- Unclear documentation
Test documentation review, discussion - Different understanding of system parts by different QA tem members
Communication channels -Miscommunication;
-Not enough history
Metrics and reports - Team members’ productivity also included

Organizational phactors

Communicational channels
History is valuable!
Communication channels, which save
conversation history: email, Slack,
Jira/Confluence, skype*.
Meetings channels with ability to record and
share screen: Zoom, GoToMeeting.

Working day in remote team
Mandatory meetings+ flexible hours
Working schedule

Project and process factors

Estimation
Online planning pocker
Discussion of open questions in Jira
Sprint planning using provided
estimates

New features discussion
Feature chats: Product manager, developers, QA.
First day call rule to discuss everyone’s vision of requirements

Product documentation
It is not possible to work without
documentation in remote team.
Ideally, if open questions are also
documented, we use spec clarification
tickets in Jira for this purpose.

Release without documentation

Sprint planning
Risks in planning period for remote
team:
-Incomplete acceptance criteria;
-Not enough investigation before
estimation;
-Not discovered team velocity.

Metrics
•Planned vs. actual hours to prepare test
documentation
•Number of issues discovered
Planning and
Control
•Number of test cases created
•Traceability between requirements and test
documentation
Analysis and
Design
•% planned test cases executed, passed and failed
•Planned vs. actual defects reported/resolved
•Planned vs. actual coverage achieved
Implementation
and Execution

Reports
Reports should be as much detailed as
possible:
-in test documentation;
- in story;
-demo recording.

Managing remote team

Control in remote teams
Emergency
No tasks
Contact manager
Time shift

Priorities and subordination
Only direct manager can set
priorities.
You
Direct manager
Manager of your
direct manager

Criticism and praise
Criticism – personal, praise – public.
Regular one-on-one meetings.
Feedback is valuable

Work in Access Softek
If you’re interested in work,
please contact
Tamara Mishcherina
tmishcherina@accesssoftek.com

WITH PASSION TO QUALITY QA CONFERENCE #1 IN UKRAINE KYIV 2019
Questions?

QA Fest 2019. Яна Лыса. Особенности управления процессами тестирования для удаленных команд

More Related Content

What's hot

Similar to QA Fest 2019. Яна Лыса. Особенности управления процессами тестирования для удаленных команд

More from QAFest

Recently uploaded

QA Fest 2019. Яна Лыса. Особенности управления процессами тестирования для удаленных команд