Запад и восток: ценовые модели через призму особенностей менталитетаConformato
16 апреля на конференции Conformato Conference 2015 выступил Александр Пронин, СЕО компании Region IT.
Александр рассказал про общение с заказчиками с запада и востока, о целях, ценовых моделях. Также о спецификах рынков запада и востока.
Поделился практическими кейсами о специфике рынков, такими как:
- Семь красных прозрачных перпендикулярных линий.
- Стартапер-перфекционист.
- Стартапер-фантазер.
- Идеальный заказчик.
- Региональный барон.
- Столичный строитель.
- Холдинг холдингов.
А также ответил на множество вопросов от слушателей.
Было только 8 докладов, впереди ещё 22. Присоединяйтесь!
Регистрируйтесь на БЕСПЛАТНУЮ конференцию до 1 мая 2015 года.
=http://goo.gl/kS7mJM=
This document discusses disaster recovery (DR) testing. It defines DR as an IT service that uses documents, procedures, people, architecture, skills, testing and continual improvement to ensure business continuity when disasters occur. DR testing is important to validate DR plans and solutions. The document outlines different types of DR testing and challenges for software testing in the DR environment, such as documentation mismatches, lack of test cases, hardware differences between production and DR sites. It emphasizes the importance of testing applications and business processes in the DR environment to ensure data consistency and validate recovery time objectives.
DaKiRy_PMStandUp_Євген Філяк “What Product Managers do in Ukrainian IT compan...Dakiry
The document discusses the role of product managers (PdMs) in Ukrainian IT companies. It notes that PdMs are responsible for identifying market pricing, buyers and users, launch plans, prioritizing features, orchestrating product development, creating roadmaps, and owning budgets. Charts show increasing vacancies for PdMs from 2013-2016. PdMs look outside at the market while BAs look inside at requirements. The roles of PdMs are compared to those in marketing, sales, and pricing. While some CEOs see PdMs as important for growth, others argue they are not needed for outsourcing companies.
DaKiRy_PMWeekend2016_Євгеній Лабунський “Conflicts like the tool of successfu...Dakiry
The document discusses how conflicts can be a useful tool for successful project delivery if managed correctly. It presents a conflicts management model involving different stages of a team's development from "Forming" to "Performing." At the Forming stage, the leader should watch for reactions, find active/inactive members, and push discussions. At Storming, the leader needs to take a neutral position, ensure all voices are heard, and facilitate compromises. Managing conflicts properly and converting them to disputes based on facts can help a team progress from Storming to Norming and Performing, where discussions and disputes are more constructive. The leader's role involves calling for disputes, selecting important topics, keeping neutrality, and switching conflicts to be based
DaKiRy_PMWeekend2016_Роман Павлюк "Product Management: Signs that You’re doin...Dakiry
This document summarizes signs that a product manager may be doing their job wrong. It discusses common mistakes like focusing on how a product will be made before what problem it solves, not involving developers in decisions, and thinking work outside the office is a waste of time. Other mistakes include prioritizing execution over positioning, committing to hourly estimates, and delivering partial solutions instead of fully solving problems. The document provides tips on how to properly scope projects, write requirements, and stay focused on business needs using the Pragmatic Marketing Framework.
Запад и восток: ценовые модели через призму особенностей менталитетаConformato
16 апреля на конференции Conformato Conference 2015 выступил Александр Пронин, СЕО компании Region IT.
Александр рассказал про общение с заказчиками с запада и востока, о целях, ценовых моделях. Также о спецификах рынков запада и востока.
Поделился практическими кейсами о специфике рынков, такими как:
- Семь красных прозрачных перпендикулярных линий.
- Стартапер-перфекционист.
- Стартапер-фантазер.
- Идеальный заказчик.
- Региональный барон.
- Столичный строитель.
- Холдинг холдингов.
А также ответил на множество вопросов от слушателей.
Было только 8 докладов, впереди ещё 22. Присоединяйтесь!
Регистрируйтесь на БЕСПЛАТНУЮ конференцию до 1 мая 2015 года.
=http://goo.gl/kS7mJM=
This document discusses disaster recovery (DR) testing. It defines DR as an IT service that uses documents, procedures, people, architecture, skills, testing and continual improvement to ensure business continuity when disasters occur. DR testing is important to validate DR plans and solutions. The document outlines different types of DR testing and challenges for software testing in the DR environment, such as documentation mismatches, lack of test cases, hardware differences between production and DR sites. It emphasizes the importance of testing applications and business processes in the DR environment to ensure data consistency and validate recovery time objectives.
DaKiRy_PMStandUp_Євген Філяк “What Product Managers do in Ukrainian IT compan...Dakiry
The document discusses the role of product managers (PdMs) in Ukrainian IT companies. It notes that PdMs are responsible for identifying market pricing, buyers and users, launch plans, prioritizing features, orchestrating product development, creating roadmaps, and owning budgets. Charts show increasing vacancies for PdMs from 2013-2016. PdMs look outside at the market while BAs look inside at requirements. The roles of PdMs are compared to those in marketing, sales, and pricing. While some CEOs see PdMs as important for growth, others argue they are not needed for outsourcing companies.
DaKiRy_PMWeekend2016_Євгеній Лабунський “Conflicts like the tool of successfu...Dakiry
The document discusses how conflicts can be a useful tool for successful project delivery if managed correctly. It presents a conflicts management model involving different stages of a team's development from "Forming" to "Performing." At the Forming stage, the leader should watch for reactions, find active/inactive members, and push discussions. At Storming, the leader needs to take a neutral position, ensure all voices are heard, and facilitate compromises. Managing conflicts properly and converting them to disputes based on facts can help a team progress from Storming to Norming and Performing, where discussions and disputes are more constructive. The leader's role involves calling for disputes, selecting important topics, keeping neutrality, and switching conflicts to be based
DaKiRy_PMWeekend2016_Роман Павлюк "Product Management: Signs that You’re doin...Dakiry
This document summarizes signs that a product manager may be doing their job wrong. It discusses common mistakes like focusing on how a product will be made before what problem it solves, not involving developers in decisions, and thinking work outside the office is a waste of time. Other mistakes include prioritizing execution over positioning, committing to hourly estimates, and delivering partial solutions instead of fully solving problems. The document provides tips on how to properly scope projects, write requirements, and stay focused on business needs using the Pragmatic Marketing Framework.
Ігор Яковлєв "Як бюджетно побудувати відділ продаж для молодої ІТ компанії"Dakiry
Чи можливо робити все власноруч і до яких пір?
З чого почати делегування?
Яка оптимальна структура відділу продаж?
Яка мотивація у кожного елементу відділу?
Traditional testing approaches involve post-development testing phases where quality is expected to be boosted after code is complete, but this illusion of control can lead to delays if requirements are not fully delivered. Agile testing is iterative and incremental, with testers testing each coding increment as soon as it is finished so that programmers never get ahead of testers and a story is not done until tested. True agile teams focus on repeatable quality and efficiency rather than just delivering specified requirements by a release date.
DaKiRy_PMWeekend2016_Андрій Рифяк "Product development for Enterprises: Short...Dakiry
This document provides guidance on product development for enterprises. It discusses business models for product development versus outsourcing. It also outlines key considerations for the product itself including features, architecture, and development process. Additional topics covered include product support, documentation, versioning, marketing, budgeting, integration with other systems, security, and lessons learned. The overall message is that product development requires planning across many areas to balance expectations with reality.
Dakiry social night _daniil leping_startup.-lottery-or-business-Dakiry
This document discusses reasons why startups often fail and provides perspectives on entrepreneurship. It lists sources that identify 5-20 common reasons for startup failure, including issues with the market, business model, management team, running out of cash, and product problems. The document then discusses the realities entrepreneurs often face, such as dealing with ego and wanting validation. It emphasizes the importance of professionalism for experienced entrepreneurs and that success comes despite, not due to, challenges that arise along the way.
DaKiRy_PMWeekend2016_Валентин Будкін "Мітинги в Scrum - the Good, the Bad and...Dakiry
The document discusses various Scrum meetings and provides classifications of "The Good, The Bad, and The Ugly" for each meeting. It summarizes the Daily Standup meeting as having a timebox of 15 minutes where the team updates each other on work, which is good, but can be bad if driven or includes silent members or micromanaging. It also notes implementation talk and using the improvement board as ugly aspects.
DaKiRY_BAQ2016_QADay_Яків Крамаренко "Автоматизація - це просто! (C#)"Dakiry
This document discusses automation testing and provides tips for getting started with test automation. It recommends starting with end-to-end smoke tests using an easy language and tools. Specific suggestions include using C# with the nSelene library or Java with Selenide. The document emphasizes that automation is a tool to help testers do their work more efficiently, and that one can start automating even without manual testing experience if they have support and learn the basics.
This document contains brief inspirational sayings and quotes encouraging people to step outside their comfort zone, see other perspectives, follow their passions, live in the present, leverage others to get things done, and travel somewhere new each year. It ends by thanking the reader for their time.
Бизнес-модели для стартапов. 9 основных блоков. 29.11.2014Peri Innovations
«Бизнес-модели для стартапов. 9 основных блоков» — это отличная возможность познакомиться со всеми необходимыми инструментами и навыками, которые позволят разобраться в мире современных стартапов. На семинаре вы узнаете, что представляет собой бизнес модель, ее выбор и этапы построения.
Как попасть на следующий уровень карьеры и зарплаты в C#geekfamilyrussia
Есть ли потолок заработной платы? Что делать, если Вы уперлись в него. Как преодолевать уровни сопротивления и избегать в ловушек в карьере .net разработчика. Результат анализа более 6.000 резюме C# разработчиков в Москве.
Доклад для потенциальных заказчиков digital-услуг базового уровня. Как выбрать оптимальный веб-продакшен/digital агентство. Для конференции "Прокачка Бизнеса".
Ігор Яковлєв "Як бюджетно побудувати відділ продаж для молодої ІТ компанії"Dakiry
Чи можливо робити все власноруч і до яких пір?
З чого почати делегування?
Яка оптимальна структура відділу продаж?
Яка мотивація у кожного елементу відділу?
Traditional testing approaches involve post-development testing phases where quality is expected to be boosted after code is complete, but this illusion of control can lead to delays if requirements are not fully delivered. Agile testing is iterative and incremental, with testers testing each coding increment as soon as it is finished so that programmers never get ahead of testers and a story is not done until tested. True agile teams focus on repeatable quality and efficiency rather than just delivering specified requirements by a release date.
DaKiRy_PMWeekend2016_Андрій Рифяк "Product development for Enterprises: Short...Dakiry
This document provides guidance on product development for enterprises. It discusses business models for product development versus outsourcing. It also outlines key considerations for the product itself including features, architecture, and development process. Additional topics covered include product support, documentation, versioning, marketing, budgeting, integration with other systems, security, and lessons learned. The overall message is that product development requires planning across many areas to balance expectations with reality.
Dakiry social night _daniil leping_startup.-lottery-or-business-Dakiry
This document discusses reasons why startups often fail and provides perspectives on entrepreneurship. It lists sources that identify 5-20 common reasons for startup failure, including issues with the market, business model, management team, running out of cash, and product problems. The document then discusses the realities entrepreneurs often face, such as dealing with ego and wanting validation. It emphasizes the importance of professionalism for experienced entrepreneurs and that success comes despite, not due to, challenges that arise along the way.
DaKiRy_PMWeekend2016_Валентин Будкін "Мітинги в Scrum - the Good, the Bad and...Dakiry
The document discusses various Scrum meetings and provides classifications of "The Good, The Bad, and The Ugly" for each meeting. It summarizes the Daily Standup meeting as having a timebox of 15 minutes where the team updates each other on work, which is good, but can be bad if driven or includes silent members or micromanaging. It also notes implementation talk and using the improvement board as ugly aspects.
DaKiRY_BAQ2016_QADay_Яків Крамаренко "Автоматизація - це просто! (C#)"Dakiry
This document discusses automation testing and provides tips for getting started with test automation. It recommends starting with end-to-end smoke tests using an easy language and tools. Specific suggestions include using C# with the nSelene library or Java with Selenide. The document emphasizes that automation is a tool to help testers do their work more efficiently, and that one can start automating even without manual testing experience if they have support and learn the basics.
This document contains brief inspirational sayings and quotes encouraging people to step outside their comfort zone, see other perspectives, follow their passions, live in the present, leverage others to get things done, and travel somewhere new each year. It ends by thanking the reader for their time.
Бизнес-модели для стартапов. 9 основных блоков. 29.11.2014Peri Innovations
«Бизнес-модели для стартапов. 9 основных блоков» — это отличная возможность познакомиться со всеми необходимыми инструментами и навыками, которые позволят разобраться в мире современных стартапов. На семинаре вы узнаете, что представляет собой бизнес модель, ее выбор и этапы построения.
Как попасть на следующий уровень карьеры и зарплаты в C#geekfamilyrussia
Есть ли потолок заработной платы? Что делать, если Вы уперлись в него. Как преодолевать уровни сопротивления и избегать в ловушек в карьере .net разработчика. Результат анализа более 6.000 резюме C# разработчиков в Москве.
Доклад для потенциальных заказчиков digital-услуг базового уровня. Как выбрать оптимальный веб-продакшен/digital агентство. Для конференции "Прокачка Бизнеса".
BDD. The Outer Limits. Iosif Itkin at Youcon (in Russian)Iosif Itkin
Exactpro is supporting the 3rd annual IT-conference YouCon to take place on 14th October in Saratov, Russia. Over 900 programmers, systems engineers and architects, software QA engineers, and marketing specialists will gather to discuss the latest trends in programming technology. It is the largest IT industry event in Saratov.
Iosif Itkin, CEO of Exactpro, part of London Stock Exchange Group, will deliver a "BDD. The Outer Limits" presentation named after Iosif's favorite Sci-Fi series.
The topics to be covered are:
Behavior Driven Development concepts
Applying BDD in trading and clearing systems
Specification by Example and using production data
Combining Model-based testing and BDD
The Outer Limits
There will be an opportunity to ask questions, share thoughts and expertise in BDD, or just chat with a representative at the Exactpro stand at any time during the event.
Don't miss out, stop by and ask how you can get your Exactpro souvenir :)
We look forward to meeting you there!
#Exactpro #Youconsaratov
21 мая состоялся мастер-класс Алексея Черняка на тему "Основы бизнес-моделирования". На мастер-классе рассматривалось, что такое и какой бывает бизнес-модель, как ее выбрать и построить.
Що ми будемо робити на вебінарі? Ми розберемо такі явища
✅ як нарцистичний розлад особистості,
✅ грандіозний нарцисизм,
✅ газлайтинг,
✅ знецінення,
✅ гойдалки вина-лють-вина,
✅ нарцистичне розширення,
✅ бомбардування любов’ю,
✅ мімікрування,
✅ створення ілюзорного майбутнього,
✅ контроль,
✅ спалахи гніву,
✅ вгадування майбутнього,
✅ вибір перебором, трошки хлібчика, щоб не подох,
✅ відштовхування/кидання/блокування,
✅ покарання мовчанням.
МАНІПУЛЯЦІЇ: ХТО КОГО І ДЛЯ ЧОГО? - Інна ТіторенкоDakiry
ВЕБІНАР: "МАНІПУЛЯЦІЇ: ХТО КОГО І ДЛЯ ЧОГО?":
Що таке маніпуляції?
Які бувають види маніпуляції, як їх відрізнити?
Хто і чому маніпулює?
Чи добре чи погано маніпулювати?
І звичайно, як їм протистояти?
Під час доповіді поговоримо про участь бізнес-аналітиків і розкриємо основні складові discovery workshop:
- Організація. Коли проведення воркшопу, окрім стартової фази, є максимально ефективним?
- Підготовка. Як почати з нічого і якісно підготуватись до воркшопу у стислі терміни?
- Проведення: Workshop Do’s and Don’ts. Приклади технік і вправ, а також приблизний план самого воркшопу.
- Оформлення кінцевих результатів або презентації, що запам’ятовуються
З понеділка йду на новий проект. The tester’s version - Олександра ЗубальDakiry
З понеділка йду на новий проект. The tester’s version - Олександра Зубаль:
- Коли тестувальнику починати тестувати? Очікування VS реальність
- Новий проєкт. Шо робити?
- Старий проєкт, але змінюється тестувальник. Шо робити?
- Як все зібрати докупи, розкласти по поличках і почати нормально спати ночами?
Oleh Shpyrna "Security Testing Basics: Check your Webapp for gaps before l_unch"Dakiry
This document provides an overview of security testing basics. It discusses adding security checks to testing by following best practices like the OWASP Top 10. The agenda includes who penetration testers are, integrating security into the SDLC, and basic tools for security testing like BurpSuite and Nmap. Common issues covered include injections, cross-site scripting, and insecure design. Resources are provided for training like PortSwigger Web Security Academy and HackTheBox.
Oleksandra Zubal "Project starters: test automation view"Dakiry
This document discusses test automation and the fundamental testing process. It covers the typical stages of testing including planning, monitoring and control, analysis and design, implementation and execution, and completion. Other sections provide overviews of typical industry domains for testing, considerations for planning like budget and dependencies, and important aspects of testing like goals, methodology, documentation and reporting, tools, and ensuring quality. The overall message is the importance of establishing a thorough and well-executed testing process to deliver high quality products and services.
Vladyslav Romanchenko "How to keep high code quality without e2e tests"Dakiry
This document discusses how to test React and Redux applications without end-to-end tests. It recommends using unit and integration tests instead to test individual components and functions. It provides examples of how to test helper functions, action creators, reducers, selectors, and component rendering and interactions using Jest and libraries like Enzyme. Key steps include mocking dependencies, dispatching actions, and asserting on output or UI states. Following these techniques allows testing isolated pieces and catching errors early without relying on unstable end-to-end tests.
Діана Пінчук "Як відрізнити авторизацію від аутентифікації та перестати бояти...Dakiry
Authentication (AuthN) is the process of verifying a person's identity, while authorization (AuthZ) determines what resources that person can access. AuthN uses factors like passwords, tokens, and biometrics to confirm someone is who they say they are. AuthZ implements access controls based on attributes, roles, rules or policies to govern resource permissions. Identity and access management (IAM) combines AuthN and AuthZ with user management to provide the right access to the right individuals. When testing, it is important to distinguish AuthN from AuthZ and understand how each can be exploited through vulnerabilities like weak credentials, authorization bypass, or privilege escalation.
Yuriy Malyi "E2E testing organization in multi-system projects"Dakiry
The document discusses end-to-end (E2E) testing organization for multi-system projects. It addresses determining team roles and responsibilities, defining the testing process and bug workflow, analyzing environments, and outlining steps for organizing E2E testing for project drops or releases. The presentation provides diagrams of user story and environment workflows and recommends getting an overall project picture, setting quality gates at each stage, and preparing test cases and environments to ensure smooth project drops or releases.
Petro Tarasenko "You've become a TL. What's next?"Dakiry
The document provides advice for a new QA team lead on next steps. It suggests creating a solid plan that addresses current challenges, future vision, timeline, and key performance indicators. The plan should be shared with key stakeholders like testing team, managers, developers, and product teams. It also emphasizes learning about priorities, challenges, and allies/detractors. Finally, it advises rehearsing the plan to concisely convey necessary information to busy managers.
Maryna Shulga "Mission Impossible. Впровадити тест процеси, якщо ніхто цього ...Dakiry
This document discusses an individual who is a test manager and provides various training services including QA fundamentals courses, ISTQB certification courses, and corporate soft skills training. It also mentions their work in industries such as healthcare, retail, and infrastructure. The document then discusses objections that can come up during presentations and how to address objections by turning them into benefits or requests for more information. It emphasizes that objections are not rejections but buying signals and opportunities to provide additional details.
QA manager Alona Tudan discusses her experience in QA and her dream of working with Microsoft Azure. She provides an overview of how to analyze logs and track failures on Azure using analytics queries. Tudan also demonstrates how to send and receive messages from Azure queues and topics using manual tools like Azure Storage Explorer and automated testing with Java code.
Зоряна Борбулевич "Підхід, який трансформував компанію Microsoft: ННК і його...
Dakiry pmweekend Oleksandr Pronin zakhid i skhid
1. Запад и Восток: ценовые модели через призму
особенностей менталитета
2. Карта местности, или о чем разговор
Цели заказчика - наше все
Цель -
удовлетворенная
потребность
заказчика
Ценовая модель
(pricing model)
Продукт
Сервис
3. Карта местности, или о чем разговор
Важность ценовой модели
Ценовая модель
(pricing model)
Фиксированные
затраты
(Fixed Cost)
Время и материалы
(Time&Material)
5. Карта местности, или о чем разговор
Пусть слоники бегают
Lead
generation
Leads
Presale
Prepayments
Contacts
Accounting
Services
Postpay
Contacts
Recommendations
Reviews
6. Специфика рынков
Запад
1.Есть языковой барьер (особенно Европа)
2.Есть сложности ВЭД
3.Имеем специфику работы в западном
правовом поле
4.Как правило, есть жесткие требования по
срокам
5.Всегда есть высокие требования к уровню
компетенций и качества
6.Часто есть разница во времени (8-9 часов)
7.Есть фактор дистанционного
взаимодействия
8.Необходимо понимать специфику
западных бизнес-моделей и обладать
экспертизой в knowledge-domain
Заказчика
1. Готовы работать по модели T&M
2. Обладают бОльшим финансовым
ресурсом
3. Имеют высокий уровень технических и
управленческих компетенций
4. Обладают историей и традициями в сфере
ИТ (более 20 лет)
5. Практикуют нейтральную или
положительную обратную связь
7. Специфика рынков
Восток
1. Предпочитают ценовую модель FC (до 90%)
2. Ориентированы на низкий бюджет. Фактор
цены в подавляющем большинстве случаев
приоритетный.
3. Меняют требования при выполнении проекта
(более чем на 50%)
4. Практикуют негативную обратную связь по
результатам работы (в том числе
промежуточным)
5. Не готовы платить за исправление ошибок
6. Часто имеют низкий уровень технических
компетенций
7. Почти всегда имеют низкий уровень
компетенций проектного управления
8. Часто не могут сформулировать свои
требования
1.Отсутствует языковой барьер
2.Работаем в общем финансовом и
правовом поле
3.Как правило нет большой временной
разницы
4.Есть общая ментальность и система
ценностей
5.Есть больше возможностей для личных
встреч и оффлайн-коммуникаций
6.Часто более лояльны по срокам
9. Специфика рынков
Кейс №1. Семь красных прозрачных перпендикулярных линий
o Область: Mobile, Android
o Страна: РФ
o Ценовая модель: FP
o Продолжительность: 9 мес
o Бюджет <= 10 k USD
10. Специфика рынков
Кейс №2. Стартапер-перфекционист
o Область: Mobile, Android
o Страна: Канада
o Ценовая модель: FP
o Продолжительность: 6 мес
o Бюджет <= 20 k USD
11. Специфика рынков
Кейс №3. Стартапер-фантазер
o Область: Mobile, Android
o Страна: РФ
o Ценовая модель: FP
o Продолжительность: 11 мес
o Бюджет <= 20 k USD
12. Специфика рынков
Кейс №4. Идеальный заказчик
o Область: Mobile, Android
o Страна: USA
o Ценовая модель: T&M
o Продолжительность: 4 мес
o Бюджет >= 100 k USD
13. Специфика рынков
Кейс №5. Региональный барон
o Область: 1C
o Страна: Украина
o Ценовая модель: ТБР
o Продолжительность: 12 мес
o Бюджет <= 20 k USD
14. Специфика рынков
Кейс №6. Столичный строитель
o Область: 1С
o Страна: Украина
o Ценовая модель: FC
o Продолжительность: 12 мес
o Бюджет <= 200 k USD
15. Специфика рынков
Кейс №7. Холдинг холдингов
o Область: 1C
o Страна: Украина
o Ценовая модель: FC
o Продолжительность: 24 мес
o Бюджет >= 250 k USD