The document discusses the changing role of business analysts (BA) from a traditional, documentation-focused role to a more modern, agile role focused on delivering value. Traditionally, a BA's responsibilities included requirements gathering, project management and documentation. However, challenges now include multidisciplinary work, rapid delivery, and minimal viable products. The modern BA role is more of a change agent that works within cross-functional teams using skills like user research, design, and agile methods to help drive transformation at multiple levels of an organization.
Yuriy Gaiduchok presented information on quality attributes analysis. The document discusses how to determine important quality attributes for a system before it is built through various approaches like interviews, surveys, scenarios. It describes quality attribute scenarios that consist of a stimulus, source, environment, artifact, response, and response measure. Examples of quality attribute scenarios are provided for modifiability, security, and availability. The document emphasizes that analyzing quality attributes upfront can help avoid issues later and lead to stakeholder satisfaction.
The document discusses how business analysts and testers can better understand each other when accepting software by exploring their different roles and processes, finding areas of overlap, and establishing a common language through workshops, modeling, and other collaboration techniques.
This document discusses continuous performance testing (CPT) and introduces the Jagger CPT solution. It provides an overview of why performance testing is important, outlines the principles and goals of CPT, and describes the key parts of the Jagger CPT platform including load generation, metrics collection, test data management, and environment management. It also provides an example customer success story where Jagger was used for continuous performance testing of a large ecommerce site.
The document discusses the changing role of business analysts (BA) from a traditional, documentation-focused role to a more modern, agile role focused on delivering value. Traditionally, a BA's responsibilities included requirements gathering, project management and documentation. However, challenges now include multidisciplinary work, rapid delivery, and minimal viable products. The modern BA role is more of a change agent that works within cross-functional teams using skills like user research, design, and agile methods to help drive transformation at multiple levels of an organization.
Yuriy Gaiduchok presented information on quality attributes analysis. The document discusses how to determine important quality attributes for a system before it is built through various approaches like interviews, surveys, scenarios. It describes quality attribute scenarios that consist of a stimulus, source, environment, artifact, response, and response measure. Examples of quality attribute scenarios are provided for modifiability, security, and availability. The document emphasizes that analyzing quality attributes upfront can help avoid issues later and lead to stakeholder satisfaction.
The document discusses how business analysts and testers can better understand each other when accepting software by exploring their different roles and processes, finding areas of overlap, and establishing a common language through workshops, modeling, and other collaboration techniques.
This document discusses continuous performance testing (CPT) and introduces the Jagger CPT solution. It provides an overview of why performance testing is important, outlines the principles and goals of CPT, and describes the key parts of the Jagger CPT platform including load generation, metrics collection, test data management, and environment management. It also provides an example customer success story where Jagger was used for continuous performance testing of a large ecommerce site.
Мощь переполняет с JDI 2.0 - новая эра UI автоматизацииSQALab
This document provides an overview of the JDI (Java UI test automation framework). It discusses features of JDI including being UI element oriented, providing common UI elements and solutions to common problems. It provides examples of how to write tests using JDI annotations and page object pattern. The document also summarizes benefits of JDI such as reducing test code, improving test clarity, reuse across projects. Finally it outlines new features planned for JDI 2.0 including layout verification, page object generator, integration with Selenium and expanding JDI to other languages like Python.
The document discusses testing of geolocation systems. It provides an overview of geolocation, including definitions and importance. It then outlines the speaker's experience and work testing GIS systems. The rest of the document details approaches to testing geolocation, including simulating calls, checking responses and databases, and verifying accuracy. It also discusses common data formats, projections, tools like PostGIS and QGIS, and potential bugs to watch for like coordinate jumbling. The conclusion emphasizes starting simple, practicing to improve, and for tests to grow with knowledge as geolocation is important for future IT.
От Зефира в коробке к Structure Zephyr или как тест-менеджеру перекроить внут...
Agile: что надо знать аналитику, чтобы действовать?
1. Agile для аналитиков – основные схемы
Максим Цепков
Навигатор и эксперт по миру Agile,
бирюзовых организаций и Спиральной динамике
IT-архитектор и бизнес-аналитик
http://mtsepkov.org
13-14 октября 2017
Analyst Days-7 в Минске
2. Примеры кейсов
2/70
Я пришла на проект ставить тестирование и не могу понять, откуда
брать исходную информацию для тест-кейсв – проект работает по
Scrum и все в почте и мессенджерах
У нас в проекте часть народа хотят попробовать Agile, а другие
говорят, что он не подходит, потому что заказчику нужна сдача и
документы по ГОСТу. Руководство в принципе не против, но если ему
объяснить как будет работать.
3. Ценности Agile – основа совместной работы
Agile-манифест в 2001: результативность и сотрудничество
Люди и взаимодействие
важнее процессов и инструментов
Работающий продукт
важнее исчерпывающей документации
Сотрудничество с заказчиком
важнее согласования условий контракта
Готовность к изменениям
важнее следования первоначальному плану
Принципы показывают, как организовать работу
Методы (Scrum, Kanban и др.) дают конкретный способ организации
3/70
4. Scrum – конкретная реализация принципов
Поставка.
Прирастает
каждый спринт
Спринт 2-4 недели – создание
конкретного результата
1 день
Product
Backlog
Определение
релизов
Планирование спринта:
цели и scope
Демо – проверка
адекватности
результата
Ретро –
адаптация
процесса
Daily scrum
Выбор
задачи
Выявление
потребностей Sprint
Backlog
Пакеты
поставки,
ценности
Доска и Burndown показывают всем
движение к результату в спринте
4/70
5. Backlog Item
5/70
Несет конкретную пользу (ценность) пользователю или стейкхолдеру
Достаточно конкретен, чтобы оценить трудоемкость
Достижение демонстрабельно – определено How to demo
Форма представления Backlog Items может быть различна,
но признаки – обязательны, иначе процесс не будет работать
6. Kanban – организация обработки потока задач
Сделать Делаем Проверяем Сделано
5 3
В работе Готово
Фазы
обработки
Лимиты ограничивают
незавершенную работу
Сложности в задаче на конкретной фазе приводят
к остановке работы для остальных сотрудников и
совместному поиску решения всей командой 6/70