5 hans van loenhoud - master-class the 7 skills of highly successful teamsIevgenii Katsan
The document describes the 7 skills that are important for effective teamwork: communicate, empathize, explore, collaborate, ideate, tell, and sell. It provides examples and exercises for each skill, such as creating personas to understand customers, exploring problems and goals, identifying team roles using Belbin's model, brainstorming ideas through divergent and convergent thinking, and using storytelling to present solutions. The overall message is that soft skills are critical for team and project success in addition to technical skills.
7 hans van loenhoud - the problem-goal-solution trinityIevgenii Katsan
The document discusses the problem-goal-solution trinity, which refers to the relationship between problems, goals, and solutions from the perspective of stakeholders. It defines a problem as an undesirable current state that inhibits desired behavior, a goal as a desirable future state that requires action to achieve, and a solution as a roadmap or plan to remove the problem and enable reaching the goal. It notes that problems and goals can only be identified through stakeholder elicitation, and that one stakeholder's problem may be another's goal. The document also discusses how problems, goals, and their relationships are not static and can change over time and context.
Digital disruption is defined as an effect that changes fundamental expectations and behaviors in a culture, market, industry or process through digital capabilities. It is an innovation that uses digital technologies to create change in our society and can threaten existing market players. Successful digital disruption satisfies a higher goal in a completely new way that is better, easier and cheaper, often through digital means. Design thinking is a light-weight approach using methods like prototyping to develop practical solutions to ill-defined problems, focusing on building quick prototypes to fail fast and succeed sooner through techniques like empathy mapping and the double diamond model. The lean startup approach emphasizes building minimal viable products to collect maximum learning from customers with minimum effort through pivoting based on testing and metrics.
5 victoria cupet - learn to play business analysisIevgenii Katsan
The document discusses how games can be used to support business analysis activities. It provides examples of different types of games that can be used for requirements gathering, prioritization, discovery, and innovation. Some key games discussed include Speed Boat to identify customer pain points, Spider Web to understand relationships between products, and Buy a Feature to prioritize features based on customer willingness to pay. The document advocates that games create structured activities that allow free and playful thinking to generate insights. It also provides tips for facilitating different games.
5 hans van loenhoud - master-class the 7 skills of highly successful teamsIevgenii Katsan
The document describes the 7 skills that are important for effective teamwork: communicate, empathize, explore, collaborate, ideate, tell, and sell. It provides examples and exercises for each skill, such as creating personas to understand customers, exploring problems and goals, identifying team roles using Belbin's model, brainstorming ideas through divergent and convergent thinking, and using storytelling to present solutions. The overall message is that soft skills are critical for team and project success in addition to technical skills.
7 hans van loenhoud - the problem-goal-solution trinityIevgenii Katsan
The document discusses the problem-goal-solution trinity, which refers to the relationship between problems, goals, and solutions from the perspective of stakeholders. It defines a problem as an undesirable current state that inhibits desired behavior, a goal as a desirable future state that requires action to achieve, and a solution as a roadmap or plan to remove the problem and enable reaching the goal. It notes that problems and goals can only be identified through stakeholder elicitation, and that one stakeholder's problem may be another's goal. The document also discusses how problems, goals, and their relationships are not static and can change over time and context.
Digital disruption is defined as an effect that changes fundamental expectations and behaviors in a culture, market, industry or process through digital capabilities. It is an innovation that uses digital technologies to create change in our society and can threaten existing market players. Successful digital disruption satisfies a higher goal in a completely new way that is better, easier and cheaper, often through digital means. Design thinking is a light-weight approach using methods like prototyping to develop practical solutions to ill-defined problems, focusing on building quick prototypes to fail fast and succeed sooner through techniques like empathy mapping and the double diamond model. The lean startup approach emphasizes building minimal viable products to collect maximum learning from customers with minimum effort through pivoting based on testing and metrics.
5 victoria cupet - learn to play business analysisIevgenii Katsan
The document discusses how games can be used to support business analysis activities. It provides examples of different types of games that can be used for requirements gathering, prioritization, discovery, and innovation. Some key games discussed include Speed Boat to identify customer pain points, Spider Web to understand relationships between products, and Buy a Feature to prioritize features based on customer willingness to pay. The document advocates that games create structured activities that allow free and playful thinking to generate insights. It also provides tips for facilitating different games.
3 karabak kuyavets transformation of business analyst to product ownerIevgenii Katsan
The document discusses the transformation of a business analyst to a product owner role. It notes that hierarchical management modes are no longer suited for modern business challenges. Product modes were developed to allow teams to build, run, and iterate solutions continuously rather than separating these stages. A business analyst focuses on requirements gathering, while a product owner sets vision and priorities and makes decisions to support the team. The document advises business analysts to adopt a product owner mindset by focusing more on business objectives and outcomes rather than just requirements. It provides five recommendations for when and how to shift one's mindset to that of a product owner.
3 zornitsa nikolova - the product manager between decision making and facil...Ievgenii Katsan
The document discusses the role of the product manager and describes them as being like a "mini-CEO" who must lead by example. It defines the ideal product manager as being DRIVEN, which stands for decisive, ruthless, informed, versatile, empowering, and negotiable. Each of these traits is then further explained, with examples of how a product manager can demonstrate being decisive by prioritizing important decisions, informed by verifying assumptions, and negotiable by seeking consensus or consent from stakeholders. The document concludes by having product managers assess themselves on how well they embody these DRIVEN traits in their daily work.
9 natali renska - product and outsource development, how to cook 2 meals in...Ievgenii Katsan
Natali Renska discusses cooking two meals in one pan by presenting steps such as cooking proteins or vegetables for one meal first before adding ingredients for a second meal to the same pan. The document provides tips on saving time and money by using one pan to cook multiple ingredients sequentially for two separate meals. Various techniques are proposed, such as cooking pasta or rice as a base before adding protein and sauce components for another meal.
7 denis parkhomenko - from idea to execution how to make a product that cus...Ievgenii Katsan
The document provides tips on how to make a product that customers will love. It discusses focusing on the problem and solution, targeting a specific market, and building a strong brand. It also outlines the typical stages a startup goes through, from creating an idea to releasing a minimum viable product to scaling up and harvesting returns. The overall message is that developing a deep understanding of customers, focusing efforts, iterating based on feedback, and having a clear business model are keys to success.
Anton Vitiaz has over 10 years of experience in business analysis, custom software development, and Microsoft CRM/SharePoint implementation. He discusses creating a minimum viable product (MVP) in 3 days by focusing on key features, keeping things very simple, and ensuring it works. The process involves planning simple implementations, cutting unnecessary elements, conducting micro 2-3 hour iterations with quick demos, adding demo data, presenting key concepts, and running simple tests. Motivating participants, having expertise, providing the right support tools, and limiting the timeframe to 3 days or less are important to success, while distractions, overcomplicating the task, and unrealistic deadlines can lead to failure.
5 mariya popova - ideal product management. unicorns in our realityIevgenii Katsan
The document discusses product management and how to transform unrealistic expectations ("unicorns") into practical realities. It defines product management and what product managers do, including developing strategy, managing releases, conducting research, and more. However, unrealistic expectations can cause problems if customer and product requirements do not align, or if "nice-to-have" features are prioritized over product improvements. The presentation provides tips on how to take a more realistic approach by understanding customer needs, conducting market research, determining requirements, and developing a product roadmap to guide the process. Templates are also shared for SWOT analysis, development charters, requirements documents, timelines, and roadmaps.
The document outlines a process for homework fieldwork that involves brainstorming ideas, exploring customer needs through interviews, prototyping potential solutions through storyboards and mockups, testing prototypes with customers to co-create, implementing a solution by 25% each assignment period and rolling a dice, and delivering the final solution to validate it and get feedback.
4 anton parkhomenko - how to make effective user research with no budget at...Ievgenii Katsan
The document discusses how to conduct effective user research with no budget and limited time. It provides recommendations for free or low-cost tools to conduct remote interviews and usability testing, including Zoom, OBS, Screencastify, Loom, and Lookback. It also recommends using YouTube to store recordings, Google Docs for transcripts, and Airtable to organize findings into an atomic database structure of people, sessions, jobs, pains, gains, and features linked to evidence from interviews. The methodology outlined atomizes research into small units that can be easily shared and built upon over time.
Myroslava garasym: COMPETENCE DEVELOPMENT: CHEAT SHEET FOR BEGINNERSIevgenii Katsan
This document provides a cheat sheet for developing competencies for beginners. It recommends knowing your market and keeping competencies balanced and up to date. A framework for competency development should align with business goals at the strategic level, use tools and drivers at the system level, and focus on the quality of tools at the operational level. Competency development is achieved through continuously improving in small pieces.
Florin Coada: MOBILE TESTING - A SIMPLE SOLUTION TO YOUR MOBILE SECURITY TESTINGIevgenii Katsan
This document discusses interactive application security testing (IAST) as a solution for mobile security testing. IAST analyzes applications in an instrumented environment to detect potential vulnerabilities by observing application behavior. It allows testing both the mobile application and some backend services simultaneously. IAST is presented as easier to use than static or dynamic application security testing alone, providing more actionable results while testing both the native mobile app layer and elements of the backend. The document outlines pros and cons of different testing strategies and emphasizes that IAST enables testing mobile apps and parts of the backend at the same time with ease of use.
Rolf Molich: IF THE USERS CAN’T USE IT, IT DOESN’T WORK Ievgenii Katsan
This document summarizes the key points from a presentation on usability and usability testing. The presentation discusses how usability is defined as the extent to which a system can be used by users to achieve goals effectively, efficiently and with satisfaction. It emphasizes that systems must be usable by actual users, not just meet specifications, and provides examples of usability problems encountered by users. The presentation also covers how to plan, conduct and report on usability tests in order to collect real user data about a system's usability.
MASTER-CLASS: "CODE COVERAGE ON Μ-CONTROLLER" Sebastian GötzingerIevgenii Katsan
Verifysoft provides a code coverage tool called Testwell CTC++ that analyzes test coverage of C/C++ code. The presentation discusses why code coverage is important, how it works, its support for embedded targets and compilers, and its integration with IDEs. It also covers safety standards requirements, different coverage levels, reports, and the low instrumentation overhead.
3 karabak kuyavets transformation of business analyst to product ownerIevgenii Katsan
The document discusses the transformation of a business analyst to a product owner role. It notes that hierarchical management modes are no longer suited for modern business challenges. Product modes were developed to allow teams to build, run, and iterate solutions continuously rather than separating these stages. A business analyst focuses on requirements gathering, while a product owner sets vision and priorities and makes decisions to support the team. The document advises business analysts to adopt a product owner mindset by focusing more on business objectives and outcomes rather than just requirements. It provides five recommendations for when and how to shift one's mindset to that of a product owner.
3 zornitsa nikolova - the product manager between decision making and facil...Ievgenii Katsan
The document discusses the role of the product manager and describes them as being like a "mini-CEO" who must lead by example. It defines the ideal product manager as being DRIVEN, which stands for decisive, ruthless, informed, versatile, empowering, and negotiable. Each of these traits is then further explained, with examples of how a product manager can demonstrate being decisive by prioritizing important decisions, informed by verifying assumptions, and negotiable by seeking consensus or consent from stakeholders. The document concludes by having product managers assess themselves on how well they embody these DRIVEN traits in their daily work.
9 natali renska - product and outsource development, how to cook 2 meals in...Ievgenii Katsan
Natali Renska discusses cooking two meals in one pan by presenting steps such as cooking proteins or vegetables for one meal first before adding ingredients for a second meal to the same pan. The document provides tips on saving time and money by using one pan to cook multiple ingredients sequentially for two separate meals. Various techniques are proposed, such as cooking pasta or rice as a base before adding protein and sauce components for another meal.
7 denis parkhomenko - from idea to execution how to make a product that cus...Ievgenii Katsan
The document provides tips on how to make a product that customers will love. It discusses focusing on the problem and solution, targeting a specific market, and building a strong brand. It also outlines the typical stages a startup goes through, from creating an idea to releasing a minimum viable product to scaling up and harvesting returns. The overall message is that developing a deep understanding of customers, focusing efforts, iterating based on feedback, and having a clear business model are keys to success.
Anton Vitiaz has over 10 years of experience in business analysis, custom software development, and Microsoft CRM/SharePoint implementation. He discusses creating a minimum viable product (MVP) in 3 days by focusing on key features, keeping things very simple, and ensuring it works. The process involves planning simple implementations, cutting unnecessary elements, conducting micro 2-3 hour iterations with quick demos, adding demo data, presenting key concepts, and running simple tests. Motivating participants, having expertise, providing the right support tools, and limiting the timeframe to 3 days or less are important to success, while distractions, overcomplicating the task, and unrealistic deadlines can lead to failure.
5 mariya popova - ideal product management. unicorns in our realityIevgenii Katsan
The document discusses product management and how to transform unrealistic expectations ("unicorns") into practical realities. It defines product management and what product managers do, including developing strategy, managing releases, conducting research, and more. However, unrealistic expectations can cause problems if customer and product requirements do not align, or if "nice-to-have" features are prioritized over product improvements. The presentation provides tips on how to take a more realistic approach by understanding customer needs, conducting market research, determining requirements, and developing a product roadmap to guide the process. Templates are also shared for SWOT analysis, development charters, requirements documents, timelines, and roadmaps.
The document outlines a process for homework fieldwork that involves brainstorming ideas, exploring customer needs through interviews, prototyping potential solutions through storyboards and mockups, testing prototypes with customers to co-create, implementing a solution by 25% each assignment period and rolling a dice, and delivering the final solution to validate it and get feedback.
4 anton parkhomenko - how to make effective user research with no budget at...Ievgenii Katsan
The document discusses how to conduct effective user research with no budget and limited time. It provides recommendations for free or low-cost tools to conduct remote interviews and usability testing, including Zoom, OBS, Screencastify, Loom, and Lookback. It also recommends using YouTube to store recordings, Google Docs for transcripts, and Airtable to organize findings into an atomic database structure of people, sessions, jobs, pains, gains, and features linked to evidence from interviews. The methodology outlined atomizes research into small units that can be easily shared and built upon over time.
Myroslava garasym: COMPETENCE DEVELOPMENT: CHEAT SHEET FOR BEGINNERSIevgenii Katsan
This document provides a cheat sheet for developing competencies for beginners. It recommends knowing your market and keeping competencies balanced and up to date. A framework for competency development should align with business goals at the strategic level, use tools and drivers at the system level, and focus on the quality of tools at the operational level. Competency development is achieved through continuously improving in small pieces.
Florin Coada: MOBILE TESTING - A SIMPLE SOLUTION TO YOUR MOBILE SECURITY TESTINGIevgenii Katsan
This document discusses interactive application security testing (IAST) as a solution for mobile security testing. IAST analyzes applications in an instrumented environment to detect potential vulnerabilities by observing application behavior. It allows testing both the mobile application and some backend services simultaneously. IAST is presented as easier to use than static or dynamic application security testing alone, providing more actionable results while testing both the native mobile app layer and elements of the backend. The document outlines pros and cons of different testing strategies and emphasizes that IAST enables testing mobile apps and parts of the backend at the same time with ease of use.
Rolf Molich: IF THE USERS CAN’T USE IT, IT DOESN’T WORK Ievgenii Katsan
This document summarizes the key points from a presentation on usability and usability testing. The presentation discusses how usability is defined as the extent to which a system can be used by users to achieve goals effectively, efficiently and with satisfaction. It emphasizes that systems must be usable by actual users, not just meet specifications, and provides examples of usability problems encountered by users. The presentation also covers how to plan, conduct and report on usability tests in order to collect real user data about a system's usability.
MASTER-CLASS: "CODE COVERAGE ON Μ-CONTROLLER" Sebastian GötzingerIevgenii Katsan
Verifysoft provides a code coverage tool called Testwell CTC++ that analyzes test coverage of C/C++ code. The presentation discusses why code coverage is important, how it works, its support for embedded targets and compilers, and its integration with IDEs. It also covers safety standards requirements, different coverage levels, reports, and the low instrumentation overhead.
24. 24 / 40
2018-03-30 22:16:24,139 INFO Handling the "/" request...
2018-03-30 22:16:24,139 INFO My Hostname is ”test"
2018-03-30 22:16:24,140 INFO current index is 0
2018-03-30 22:16:24,140 INFO I have been seen 1 times
2018-03-30 22:16:24,140 INFO HTML: <p>1</p>
2018-03-30 22:16:24,164 INFO Handling the "/" request...
2018-03-30 22:16:24,165 INFO My Hostname is " test "
2018-03-30 22:16:24,165 INFO current index is 1
2018-03-30 22:16:24,165 INFO I have been seen 2 times
2018-03-30 22:16:24,165 INFO HTML: <p>2</p>
2018-03-30 22:16:24,189 INFO Handling the "/" request...
2018-03-30 22:16:24,190 INFO My Hostname is " test "
2018-03-30 22:16:24,190 INFO current index is 2
2018-03-30 22:16:24,190 INFO I have been seen 3 times
2018-03-30 22:16:24,190 INFO HTML: <p>3</p>
2018-03-30 22:16:24,214 INFO Handling the "/" request...
2018-03-30 22:16:24,214 INFO My Hostname is " test "
2018-03-30 22:16:24,214 INFO current index is 3
2018-03-30 22:16:24,214 INFO I have been seen 4 times
2018-03-30 22:16:24,214 INFO HTML: <p>4</p>
2018-03-30 22:16:24,244 INFO Handling the "/" request...
2018-03-30 22:16:24,245 INFO My Hostname is " test
Задача
2018-03-3… 1356 times