Саморазвитие

•Download as PPT, PDF•

0 likes•279 views

Andrey Rebrov

Technology Art & Photos

Самоорганизация: на работе и в жизни Самара - 2010

Успеть все... ....что действительно надо

[object Object],[object Object],[object Object],[object Object]

This document discusses problems that can occur with traditional testing approaches and how to transition to agile testing practices. It provides two examples of organizations that struggled with long regression cycles, missed estimates, low quality and stress. The root causes are identified as document-based collaboration, lack of testing knowledge by developers, and infrastructure management chaos. Recommendations are made to use Kanban, collaborate on requirements, implement smart metrics, test automation, and a DevOps approach. Specific practices that were implemented include risk management, specification by example, test-driven development, continuous integration, configuration automation, and test automation. The results were increased delivery rates up to 5 times, zero bugs in production, no overtime, and more enjoyable work.

Spec By Example or How to teach people talk to each other

Andrey Rebrov

This document introduces an approach called "Spec By Example" to improve communication between developers, QA analysts, and clients. It involves impact mapping to focus on user stories, QA and analyst pairing to create examples to describe requirements, and diverse and merge sessions for the team to collaboratively build out examples. The examples are then optimized by compressing tables and introducing parameters before being linked to automated tests through a behavior driven development approach. This unified process allows requirements, test cases, and code to have a single source of truth, makes it easy to trace work back to business needs, and improves estimation, demos, and reduces rework and issues.

Test Automation Canvas

Andrey Rebrov

This document discusses test automation challenges at an investment bank and lessons learned. It outlines problems with lengthy manual regression testing. An attempt was made to use Jameleon for test automation but it caused issues. They identified needs for metrics, definitions of done, and separating test connections. Recommendations include using tools like Selenium and SoapUI with a Jenkins/JIRA setup. While quick wins are possible, separating test connections and fully defining requirements are important for successful test automation.

How engineering practices help business

Andrey Rebrov

This document provides advice on how to introduce new engineering practices and technologies to a team or business. It discusses several examples of proposed new practices and technologies such as test automation, continuous integration, refactoring, and DevOps. For each, it advises how to demonstrate the benefits through examples and metrics, how to gain buy-in from various stakeholders, and pitfalls to avoid such as claiming a practice is necessary just because a famous person recommends it. The overall message is that new practices must provide clear value and be introduced through demonstration and collaboration rather than dictates.

Don’t turn your logs into cuneiform

Andrey Rebrov

This document discusses using Logstash to collect, parse, and store logs from multiple sources in Elasticsearch. It describes Logstash's three main components - inputs, filters, and outputs. Examples are provided for using Logstash with Lumberjack to ship logs, parsing logs with grok filters, and outputting to Elasticsearch. Instructions are included for installing, configuring, and running Logstash, Elasticsearch, Kibana, and Lumberjack to build a log management pipeline.

DevOps tools cargo tools

Andrey Rebrov

This document discusses various DevOps tools and techniques including continuous integration, monitoring, logging, infrastructure as code, and visualization. For each tool or technique, it provides examples of how they can help teams as well as potential downsides related to communication issues. The key message is that while tools are useful, overreliance on tools without proper communication between team members can cause problems and that face-to-face conversations are important for addressing issues and improving processes.

Agile Games

Andrey Rebrov

The document discusses using business games to teach and promote Agile principles and practices. It defines what a business game is and notes they focus on results rather than process and involve more participant engagement than formal processes. The document outlines different types of business games for innovation, requirements analysis, and explaining Agile concepts. It provides recommendations for facilitating the games, such as not highlighting solutions and following the rules, and ideas for introducing Agile through a presentation and game with a success story. Resources for finding and creating additional business games are also included.

Agile тестирование в enterpise проектов: путь трансформацииAndrey Rebrov

Building deployment pipeline - DevOps wayAndrey Rebrov

Test Automation Canvas - не наступайте на глабли автоматизацииAndrey Rebrov

Не превращайте ваши логи в клинописьAndrey Rebrov

Карго культ инструментов в DevOpsAndrey Rebrov

как инженерные практики помогают экономить бизнесуAndrey Rebrov

грабли автоматизации тестирования мобильного веба с помощью Selenium 2Andrey Rebrov

DevOps от и до - что, зачем и почемуAndrey Rebrov

Agile Testing: вопросы и ответыAndrey Rebrov

DevOps модное слово или следующая ступень эволюцииAndrey Rebrov

Как научить людей общаться с помощью Spec By ExampleAndrey Rebrov

Rebrov selenium camp2013Andrey Rebrov

Курс молодого бойца-автоматизатора - как остаться в живых и стать ветераномAndrey Rebrov

Саморазвитие

Recommended

Recommended

More Related Content

More from Andrey Rebrov

More from Andrey Rebrov (20)

Саморазвитие