reQuest - conference for those who want more

We would like to present you the reQuest – conference intended for people involved in the broadly understood area of business and system analysis in IT.

reQuest is a new brand on the Polish market. A fresh and fast-growing brand, which flagship product is conference for analysts, carried out by analysts. Our goal is to build a community focused on the subject of analysis, business requirements and needs; a community that will actively participate in the creation of a new dimension of analysis – an innovative and interdisciplinary field, effectively transforming business needs into effective and innovative solutions. We want to combine knowledge and experience from different areas and disciplines in order to expand the competence and capabilities of analysts. We would like to encourage questions, discussion and move away from the established pathways towards alternative opportunities.

If you feel part of the community described above, we invite you to the reQuest conference. Change your IT industry with us!

We kindly invite
  • Business and system analysts
  • IT Solution designers
  • Product Owners
  • Business representatives
  • Testers and QA Specialists
  • Everyone who wants to know and be able to do more!
Date and place of the conference

The conference will take place on 4-5 October 2018

Location:

Hotel Boss
Warsaw, ul. Żwanowiecka 20

Conference organizer

Stowarzyszenie Jakości Systemów Informatycznych
ul. Poznańska 16 lok. 4
00-680 Warszawa

http://www.sjsi.org

LECTURES

WORKSHOPS

DAYS

TICKETS

Speakers

We present our speakers.

Eric Riou du Cosquer

Audit, Consulting, TMMi Accredited Assessor and Trainer

    Tomasz Dubikowski

    Ocado Technology / Software Development Manager

      Karl Wiegers

      Principal Consultant with Process Impact, author

        Marcin Sikorski

        Test Engineer at Tieto

          Petra Boušková

          Coordinator of Cemex Go Deployment team, professional Soft Skills Trainer

            Olivier Denoo

            Vice-president ps_testware SAS, President of the CFTL, Governance Officer of the ISTQB

            Tomasz Furgalski

            Psychologist, coach, trainer

            Arnika Hryszko

            Senior quality assurance specialist, accredited ISTQB trainer

              Anna Jankowiak

              Founder and owner of GrywIT, vice-president of the Management Board of INNOKREA Sp z o.o.

              Krzysztof Kołosowski

              SoftServe / Business Analyst

                Agnieszka Kugler

                Director of the Analysis Department of the Capital Market Division at Asseco Poland S.A.

                Hans van Loenhoud

                2nd chair of IREB, trainer/coach/consultant at Taraxacum

                Jarosław Łojewski

                Main IT Architect at Nest Bank S.A., author of the DobraPorazka.pl blog

                Monika Perendyk

                Analyst, trainer, lecturer, co-founder and president of the Association of Requirements Engineering (SIW)Analyst, trainer, lecturer, Editor-in-Chief of REQ Magazine

                  Andrzej Sobczak

                  Professor at the Warsaw School of Economics, editor of the Robonomika.pl

                    Hanna Tomaszewska

                    Business Analyst, author of the Analiza IT blog

                    Jacek Wieczorek

                    Consultant at 202procent.pl, co-founder of agile247.pl, creator of the blog agilecoaching.pl

                      Michał Wolski

                      MODESTO consultant, author of the blog https://www.michalwolski.pl/

                        Elena Zhukova

                        Business Analyst

                        Piotr Źrołka

                        Designer and consultant, service design specialist, UCD

                          Agenda

                          09:40 - 10:10
                          Internet of Things loves data - analysis of Industry 4.0

                          If Internet of Things is all about connectivity and cooperation then Industry 4.0 is based on data. In fact - lots of data! We are no longer talking about GigaBytes or TeraBytes but rather such abstract ideas and units like ExaBytes. And that's the main topic of this presentation - how huge is IoT, what is the value of switching from reactive to predictive company and why we use lambda architecture in the first place. And even if the concept of security, ethics, rules and regulations regarding data itself is also interesting on its own, this time we will focus directly on Industry 4.0 itself. Fast paced and intense presentation dedicated for Analysts and people loving and caring about IoT.

                          Marcin Sikorski

                          To explore strange new worlds, to seek out new life and new civilisations, to boldly go where no man has gone before.” Just like the crew of the USS Enterprise, we explore the IT universe – seeking out new solutions, new technologies, and frameworks – from which we can learn to help us work better and more efficiently. We do this to create more functional and usable software for our customers, to put a big smile on their faces, and maybe – if we do our job really well – to make them stand back and admire what we have crafted. I was lucky enough to work in BDD (Behaviour Driven Development) quite early in his career, but I also had the misfortune to see how this great idea so often tends to fail. In my presentation I wanted to show what it is like working with BDD and what value can it give to business people. Finally I would like to propose an effective, alternative solution for well-known BDD tools, which is „Spock” – a convenient, lightweight framework, based on the Groovy language.

                          Tomasz Dubikowski

                          “The final users are fully satisfied with their new software”, “The software development project was carried out exactly as expected, and ended successfully”, “The communication between business, technical and user stakeholders was easy and efficient”… are statements we rarely hear. It is a fact that many projects fail and they fail for reasons that are often the same: the unability to identifiy the right needs, to derivate them into requirements and to manage them throughout the project. In this presentation you will be presented a couple of real life examples illustrating good and bad practices, together with a set of techniques recommended to limit the risk that the project fails. Even if there is a very large number of BA and Requirements Development techniques, you just need to remember some of them and to be able to select the most appropriated depending on the context. During this presentation, starting from good and bad real life examples of large IT Projects of different sectors such as the medical industry we will identify some good practices required at the beginning of the project to ensure the elicitation and collection of the right needs. We will also answer questions such as: -which software development model is the best to ensure an efficient BA and Requirements Development process? - what to do if the business side of the project keeps moving even after the IT Project starts? - in case of a real issue between sides, what kind of evidences should both side be able to provide? - which level of documentation, (if any) is expected with an agile project.

                          Eric Riou De Cosquer

                          Accessibility is a legal requirement in almost every country in the world. WCAG 2.1, Section 508 of the Rehabilitation Act, Equality Act 2010 these are examples how serious accessibility is. Accessibility means the ability of everyone regardless of their condition to have access to digital product, transport, physical products. The web and internets in whole is an increasingly resource in many aspect of our life, so it is important that the digital product be accessible to everyone in order to provide equal access and opportunity. Accessible is easy & low-cost if you as BA think about it on the early stage

                          Piotr Zrolka

                          Model-based testing is an increasingly popular trend in the world of quality assurance. The aim of such an approach is to focus on a working system model and automatically generate test cases. However, how can it become useful in the work of a business or system analyst? The essence is in the model. It is called an executable specification. In this approach, it can take the form of code, gherkin syntax or UML graphs and diagrams. The latter is something that analysts use every day. In my presentation, I would therefore like to show how model-based testing can be used in the work of analysts. And how this approach can improve the work of the project team.

                          Arnika Hryszko

                          The spread of Agile raises demanding challenges. If you’re a BA who’s faced with the situation when your organization is undergoing “agile” transformation, you might be looking for information about what this transformation means. There are some misconceptions about agile adoption​ and even more hype. The lecture introduces my personal experience of reaching organization’s Agile maturity from a Business Analyst perspective.

                          Agnieszka Kugler

                          Design Thinking, what is it anyway? A method – an approach – a culture – a mindset? Yes, indeed, all of it! Design Thinking is becoming increasingly popular among developers who want to deliver better solutions to their users; innovative solutions for wicked, ill-defined problems – the problems that organizations are really concerned with today, but that they cannot put into words for their IT staff. Design Thinking is based on two pillars, empathy and creativity, which are elaborated in five elements: empathize, define, ideate, prototype and test. These elements are not strictly linear, nor iterative; they alternate with each other in the flow of the actual project. They are glued together by the concept of the ‘double diamond’. This propagates an alternation between divergent thinking, to generate a rich set of innovative ideas, and convergent thinking, to focus on a single, valuable, working solution. The double diamond advocates that this is done twice: first to come to a clear starting point for development (the ‘point of view’ statement) and then to deliver an agreed, properly tested, working solution.

                          Hans van Loenhoud

                          Despite years of efforts to improve the professional approach to developing software systems, many of these projects continue to fail. Investigations into these failures invariably denote poor interactions between humans, both within development teams and with customers and users, as a key factor. Recent evolution in development approaches, like human-centered design and extreme programming, try to address this problem, but until now, an overall view was missing. In this presentation we integrate these initiatives into a simple model, that arranges six key skills along two axes (customer–team and problem–solution) around communication as a core. Many techniques are available to implement these skills in development teams, so failure will no longer be the usual outcome.

                          Hans & Olivier

                          Did you know, that 65% of our average workday is COMMUNICATION with our colleagues? Communication is really essential in our daily life. It can make or break a project we are working on! Bad communication makes us not only lose valuable time, but money and resources as well. Let’s have a look at the style different people use to communicate, and on the different approaches we can use to make our communication more effective, and stop wasting time in meetings, that we never needed to have if we communicated properly. I will teach you the best tips and tricks to succeed in communication with your colleagues and partners to make your project great again!

                          Petra Buskova

                          Although there are few absolute truths in software development, I have discovered several requirements principles that apply almost universally to software projects. These principles emphasize the critical contribution that excellent requirements make to a project's success, and the critical contribution that customer involvement makes to excellent requirements. You'll hear several suggestions for practices that can help any team build a more effective customer-developer partnership. These cosmic truths can help your organization produce and manage accurate, consistent, and unambiguous sets of requirements.

                          Karl Wiegers
                          09:00 - 9:30
                          Rejestracja

                          Rejestracja uczestników, wydanie pakietów powitalnych, poranna kawa

                          Business is changing. IT is changing. But are the tools and working methods of an analyst and an architect changing, or should they change, especially at a time when processes are becoming more and more robotized? In this presentation I will try to look at the interactions between the analyst-architect and the robots from two different perspectives - i.e. do we need to approach the analysis and architecture of robotized business differently than before, and how robots can help an analyst/architect in his work. It turns out that more and more companies look at analysts/architects as a cost (which can and does bring benefits, but is strongly delayed in time) and wonder whether there is any approach to improving the effectiveness of these roles. Presentation in Polish.

                          Andrzej Sobczak

                          Business analyst analyzes business? In most cases they do not. Many projects come out of the black box. Do they have any sense? Sometimes they hit like a bullet in a fence. Sometimes they are like a cannon for fly. Sometimes they do not solve the right, most urgent problem. And sometimes the decision-maker wants a toy or promotion, forgetting about the customers and the development of the company. Is this an analyst's problem? Is your project the right one for your company? Let's take a look at what's going on above the project - real business analysis, analysis of the organization and strategic analysis. We will solve the puzzle - where the sensible projects come from and we will learn how to define the necessary initiatives for the company. Presentation in Polish.

                          Hanna Tomaszewska

                          Many years ago, during a recruitment interview, the president of one company told me: mistakes made at the stage of analysis are the most expensive for the company. It was a theory for me at the time that I understood, but I did not experience too much or I could not assess the scale or feel the seriousness of these words ☺ Each project I took part in, each experience, added another piece to the certainty of what I was doing well and what was wrong, contributed to reducing the risk of making a mistake. We usually learn from our mistakes, but we also know that it is cheapest to learn from others. But this does not always work ☺ I invite you to edit my second speech "Mistakes in analysis - what to do, and whether they can be avoided" ☺ Presentation in Polish.

                          Elena Zhukova

                          Most technology companies declare that they use Scrum. Unfortunately, it is often only named 'Scrum', and the changes made, turn out to be very superficial. One of the areas that usually is not adopted for agile reality is the widely understood requirements analysis plane. As a result, despite high expectations, the results of work in Scrum do not bring the expected results. The solution to this situation is a thorough reorganization of the way products are developed in the company. These changes affect, among other things, the overall development process, the company structure, the way in which teams and requirements management techniques are managed. I have had the opportunity to experience the above aspects working with many technology companies. Thanks to this, I understood, among other things, how important it is for the team - and not for the individual - to take responsibility for understanding business requirements and needs. During the presentation you will learn how to avoid the most common pitfalls of working in Scrum, related to requirement analysis and learn agile ways of organizing work that will increase your chances of early delivery of the right products. Presentation in Polish.

                          Jacek Wieczorek

                          Analyst in the team, analyst outside the team, analyst as Product Owner, analyst as Proxy Product Owner. In this presentation I will focus on the applied models of work of an analyst with agile team (and in a team). I will mention more interesting techniques that are useful in this cooperation, such as: Living Documentation, Executable Specification, Domain Modeling, Event Storming. As a person often involved in working with development teams and looking aside at the analysts' work, I will also be tempted to make a subjective forecast of the future of this profession. Presentation in Polish.

                          Michał Bartyzel

                          On walls, boards and other surfaces you can more than once see squares, rectangles connected by lines. Next to it there are contents of what these "squares do with each other". This is how architecture is created. In many cases the drawings are covered by other drawings and the idea of architecture is lost. There is a lot of talk about business processes. It seems that modelling business processes in the software production process is the basis to which the subsequent stages of this process refer. On the other hand, there is the agile approach, where architecture and processes are discussed little or nothing. During the presentation "Corporate Architecture as an Introduction to Business and System Analysis" I will talk about my practical experience in implementing elements of corporate architecture in the world of software development. At the beginning I very briefly describe corporate architecture. I will indicate its products and the stakeholders who should be interested in them. Then I will focus on the use of corporate architecture products by business and system analysts. In my opinion, corporate architecture to exist and develop, must be included in the software development process. For this reason, I will present the value and impact of corporate architecture products on the work of teams working in both classic and agile models. Presentation in Polish.

                          Michał Wolski

                          Play engagement or how to engage a project team with gamification. Players do not need to be additionally motivated to reach new levels in the game - so why not use the game mechanisms to engage our project teams to help them achieve their goals? You can do it through gamification, which is becoming more and more popular in Poland. Fabula, points, ranking, badges - these are just some of the applied mechanisms, which of the everyday tasks of employees create their professional adventure. How can they be integrated into the work of our project team? During the lecture you will not only learn more about the gamification, but you will also have the opportunity to build the concept of the game yourself. Which one? Come and find out. Presentation in Polish.

                          Anna Jankowiak

                          Any communication is made within a relationship. Influencing, persuading, convincing are done within the framework of relationships. The work of a business analyst with a client takes place within a framework of established relationships. Those who master the art of persuasion gain an extraordinary advantage in the process of interacting with customers. This advantage, however, does not result from knowing any technique which could be used to reach the client and obtain the necessary information. It is not a technique, it is a perfect adaptation to the customer, discovering his needs and satisfying them. The most important thing is to know that all that matters is the nuances, small details and, at the same time, the whole. Presentation in Polish.

                          Tomasz Furgalski

                          Every new idea that we want to implement using either the company's resources or the support of investors, we must be able to present effectively. In most cases, decision-makers do not have much time to review all the details of a project. How do I convince them within 5 minutes? What will interest them most? What should an effective presentation look like? And the better we prepare it, the more chance we have to make a decision in line with our expectations. I invite you to take a closer look at the model of short, effective demonstration of ideas which is useful in contacts with corporate decision makers, customers or investors. Presentation in Polish.

                          Jarosław Łojewski

                          Although there are few absolute truths in software development, I have discovered several requirements principles that apply almost universally to software projects. These principles emphasize the critical contribution that excellent requirements make to a project's success, and the critical contribution that customer involvement makes to excellent requirements. You'll hear several suggestions for practices that can help any team build a more effective customer-developer partnership. These cosmic truths can help your organization produce and manage accurate, consistent, and unambiguous sets of requirements.

                          Karl Wiegers
                          9:00 - 13:00
                          Defining the goal

                          The workshop will include an introductory part - theoretical and practical - during which participants will have the opportunity to use the acquired knowledge on a given example. Business Motivation Model notation helps to understand change, business, goal, reasons for change, organize business plans, organizational development, project, changes. This notation helps to organize the knowledge, understand the motivation and verify the consistency of the requirements. It is a great tool for software developers, business analysts, strategic analysts, architects, product owners, managers, directors, everyone who has contact with business and wonders how we can support it. For anyone who wonders how to verify whether the collected requirements are consistent and complete. During the workshop, participants will have the opportunity to practice the BMM model development, ask questions and discuss the results on a real example. I sincerely invite you. Workshop in Polish.

                          Elena Zhukova

                          A common problem that is faced by business analysts is the wrong way to address the challenges faced by a product or service. As a result, we create the solutions that do not fulfil the requirements set out before them, often unspoken at the moment of analyzing the assumptions. This implies the necessity of change, frustration and negative feedback to the project participants (inter alia, to the business analyst). Because his role is also to help initiators to properly prepare the basis for project implementation. And it doesn't matter whether we use the waterfall or agile method - if the project objectives have been defined incorrectly, the result will also be incorrect. Assuming that the delivered solution is to fulfill the requirements of customers or users who will have to use it, the analysis should begin by defining their needs, expectations, features that they do not like in similar solutions, but also those that give them the pleasure of using them. Value Proposition Canvas (VPC) can help in this analysis and translate its results into appropriate product features. It is simple to use, but it has a deep sense in the concept of mapping needs and expectations of different customers and users for product features - values that the product will give to its recipients. The product itself (material or service) does not arise simply from the definition of what it is supposed to provide. To be delivered, it must be embedded in a broader context, in a certain environment. To create a product or service you need resources, partners, work that has to be done. Delivery to customers is possible thanks to specific distribution channels, and the acquisition of these customers involves the implementation of specific actions, addressed to a given product, customer and communication channel. In the economic context, all the above activities, which means specific costs, must make it possible to generate revenues allowing for the financing of investment, maintenance, sales and development expenses. All of the aspects mentioned above can be analysed using another visual tool, the Business Model Canvas (BMX). This model, which is connected to the VPC through the values provided by the product and the customers, makes it possible to conduct this analysis. It also allows you to prepare different variants of how to create a product, deliver it to customers, maintain and develop - keeping an eye on costs and benefits. By using these two tools, we can effectively help business colleagues to discover the real values of their product to customers. We will also help them to embed the idea in a broader perspective, which will have an impact on the scope and method of implementation of the project that we support. Workshop in Polish.

                          Jarosław Łojewski
                          9:00 - 13:00
                          Pisanie testowalnych wymagań (Jak pisać wymagania, aby współpraca z testerami i programistami układała się lepiej).

                          Purpose: The aim of the workshop is to provide participants with knowledge about the testability of requirements and writing them in a clear and transparent manner. This way, it is possible to facilitate their further cooperation with other team members, such as testers, programmers or architects. Improving the way of creating requirements means not only better cooperation, but also, as a result, faster delivery and increased quality of the final product. Content: The workshop will be a mix of practical and theoretical knowledge. In the theoretical part, the trainer will share her expertise in quality assurance with regard to the requirements creation and management. With particular reference to the concept of testability. She will also invite participants to exchange knowledge and discuss different perspectives and approaches. It will be also an opportunity to learn about the examples of creating good requirements. The practical part, a series of exercises, will contribute to verification of the gained knowledge and using it on real examples. Participants will be able to test their skills in creating testable requirements, as well as in improving existing ones. Techniques will also be used to facilitate work on requirements and to visualize them in a transparent way. Benefits: After the workshop, participants should: be able to explain the concept of testability; be able to describe the characteristics of a well-written requirement; properly formulate questions and provide constructive feedback in an effort to make the requirement clearer, more complete and more concise; use the principles and tools of semantics to create good requirements. be familiar with the differences between functional and non-functional requirements.

                          Arnika Hryszko

                          In recent years we have seen further dynamic development of agile techniques, but under the agile umbrella Scrum and its hybrids with other approaches are still at the forefront. Many teams choose this method, in the expectation of the ultimate success of their projects. I will not be revealing, but I will remind you that the decisions about choosing a style of work at the beginning of the project will certainly not secure our final success. We always have to work hard with the whole team during the whole project. That's why people who want to support their teams in creating a better tomorrow, want to be an effective leader, scrum master or simply a proactive member of the development team should look for less standard solutions. One of them is undoubtedly games, which will be the main theme of the workshop. Games can be used in many project fields in many different ways, among others, and to integrate a newly formed team, convince "unbelievers" or management of the superiority of agile solutions over classic, increase commitment and support for teamwork, conflict resolution, coaching or support for quiet and verbal communication, which is the key in agile approaches. During the session I will invite you to participate in 6 games where the key will be you and education through the good fun. Together we will try to deal with the topics of team formation, teamwork, focus on a common goal, prototyping, quiet cooperation and effective and positive communication. See you during the game sessions!

                          Rafał Stańczak
                          9:00 - 13:00
                          Dostępność w praktyce - nie taki diabeł straszny, jak go malują.

                          The accessibility of digital products (web and mobile applications) is becoming increasingly important in IT. When designing a product, we must remember about its future user, who would like to take full advantage of it. During the training, participants will learn how to create accessible digital products for all users and become familiar with the European Union/U.S. accessibility laws. 1. INTRODUCTION TO ACCESSIBILITY Basic concepts related to accessibility, How people with disabilities and older people use digital products, Law on accessibility: Section 508, WCAG 2.0. 2. GOOD PRACTICES IN THE DEVELOPMENT OF DIGITAL PRODUCTS Text equivalents for multimedia elements, Headers, Contrast, Keypad operations, Labels for form fields, Tables. 3. CONDUCTING AVAILABILITY TESTS 4. WORKSHOP-BASED EXERCISES

                          Piotr Źrołka

                          One of the most difficult moments in the work of a requirements engineer or analyst is not the solution analysis itself, but the right selection of vocabulary describing what has to be done in the system. This is crucial because we do not create documents for ourselves, but for the client, the developer and the tester. Each of the groups has different expectations of this document. The question is - how to describe business requirements and functional requirements in a way that makes them understandable and unambiguous? Which elements should be added to our description and what to avoid? You will learn about this and many other good practices during the workshops, which I cordially invite you to.

                          Monika Perendyk
                          9:00 - 13:00
                          Connecting PO with agile practices, traceability and testing

                          Purpose: The aim of the workshop is to provide participants with knowledge about effectiveness of Agile and the hidden power of cooperation that it can offer. We will also learn why shared documents not always mean shared understanding and what type of traceability practices allows teams to do more in less time. We will also discuss why agile is a form of art – both metaphorically and literally – of product creation. Content: The workshop will be a mix of practical (games) and theoretical (explanation) knowledge. In the theoretical part, the trainer will interact with participants to gain knowledge of their expectation and then share his expertise in terms of Agile. From basics, manifesto, roles and sprints to traceability practices and agile backbone approach. We will dive into explanation how differently we might understand Minimal Viable Product and what sort of good practices adapt in projects. The practical part, a series of simple exercises, will prove the power of the Agile approach. In final exercise we will adapt the concept of Backbone and, after successful project, we will try to adapt practices allowing us to optimize work ethics even further. Benefits: After the workshop, participants should: ● be able to explain the advantages of Agile; ● explain why cooperation with client on every level is so important; ● understand the need for tester’s role in Agile project, ● be able to describe and mention traceability practices; ● use backbone approach to create better stories.

                          Marcin Sikorski

                          PRESENTATION SKILLS: HOW TO MAKE EVERY PRESENTATION OF YOURS SUCCESSFUL? Are you a Business Analyst? Are you a Test Lead? Are you a QA Engineer? Are you… No matter who you are, at some point in your career, you need to present something to other people. No matter how good of a product you have, if you don’t know how to sell it, your stakeholders will not approve it. In software testing, we are focusing on tools, techniques and processes, while forgetting the basics. That we are humans who work with other humans. My intention is to teach you how to express your ideas and needs in understandable and convincing way. I would like to share my experience of presenting to both small and large audiences. I will talk about how important it is to be aware of the power of first impression. Imagine that in most cases, the first 7 seconds make up the whole difference between ‚win‘ and ‚lose‘ in any business. The style of your handshake, the way of your introduction. After this workshop, you will know how to get under the skin of your customer immediately. Do you know that feeling? Your presentation was good, full of many interesting and important facts. But you don’t remember anything. No key points that stick in mind. Is it a problem of presentation structure? Maybe. Or maybe you will be surprised – lots of times there is a sinificant lack of proper body language! I will teach you how to support your speech with specific gestures so that people focus, understand better and remember more. Storytelling in software testing? Not relevant. We have clear requirements, clear instructions. There is no time for stupid stories. Hold on! We all love stories. And there is a difference between these two statements: 1. ‚Our App has a functionality to order up to 100 tons of concrete ad-hoc.‘ 2. ‚Our App has a functionality to order up to 100 tons of concrete ad-hoc. Imagine, our last customer desperately needed 90tons at the very last minute, fortunately we delivered everything within 2 hours and we saved his money, time and basically the whole construction.‘ Are you talking to me? Are you presenting a new product to Stakeholders or dry dates and charts to Top Managment or strict testing process to QA Engineers? What is your goal? Know your audience, that’s the key. There are many differences in the structure, tone of your voice, words you use and specific steps of ‚Call to action‘ depending on if you want to inform, persuade or inspire your audience. What else? Much more, we have 4 hours, so don’t expect that you will sit in the corner. This session will be intense, informative, fun and engaging. Anyone who wants to be excellent in presenting shouldn’t miss it!

                          Petra Buskova
                          9:00 - 13:00
                          7 Skills for highly effective teams

                          The 7 Skills model helps IT projects to become more successful by addressing the key success factor of all teams: the soft skills of the team members. The model starts from two assumptions: (a) true success is a matter of good teamwork and (b) good teamwork is based on emotional interactions between individuals. The model is aligned along two axes: the ‘Customer facing’ - ‘Team facing’ axis and the ‘Problem facing’ – ‘Solution facing’ axis. In the center is ‘Communication’ as the fundamental skill that is the starting point for all interactions. Arranged around this core you find six key skills that are important for every IT project: ‘Empathize’ (customer/problem), ‘Explore’ (team/problem), ‘Collaborate’ (team), ‘Ideate’ (team/solution), ‘Tell’ (customer/solution) and ‘Sell’ (customer). The 7 Skills model serves as a road map to improve human interactions in development projects. To implement it, each skill has been substantiated by one or more simple but proven techniques. To mention some: communicate – Shannon-Weaver model; empathize – Personas; Explore – goal trees; Collaborate – Belbin team roles; Ideate – Wallas’ creativity model; Tell – storyboarding; Sell – Cialdini’s principles. These techniques of the 7 Skills model can easily be presented and explained. However, to make them work, one should exercise them. Therefore, a workshop is an excellent way to transfer the concept: you will learn most by actually doing it. In this workshop, you will work with other participants in a small team to design the outlines of a simple IT system. We will explain all techniques and give you some practical exercises with a challenging selection of them.

                          Hans & Olivier

                          As Business Analysts we encounter difficult customers every day. That is why we need a specific toolset to deal with such people and create win-win situations for our projects. The main goal of this workshop is to give you such an arsenal. The whole workshop will be divided into three parts: 1. How to identify different type of customers and how to negotiate with them – you will get familiarized with several different types of personalities and learn how to analyze your own stakeholders with these properties. For each type we will define the specific set of tools to be used during meeting and in day-to-day work. Afterwards I will ask you to characterize some of the people that you are working with to seek out the best approach to negotiate with them 2. Visualizing goals as a part of creating interactive meetings – you will learn how to create impact maps and how to use them in your work. As Impact Maps may be used not only in IT projects it’s a viable tool to be used even in your personal life. On this part we will also talk about design thinking and how it can be used to make your kick-offs/discoveries better. Therefore during this part of the workshop we will: a. Learn how to create good business goals b. Draw our own impact map (based on a created goal) c. Learn how to validate requirements using impact mapping technique d. Transform impact map into a backlog e. Learn about design thinking approach and how to use it in your work 3. Case studies and discussion – I will present several complex cases that I’ve encountered during my career and will describe business analysis techniques that I used. Afterwards we will analyze your own cases and try to find the appropriate solutions together.

                          Krzysztof Kołosowski

                          Sponsorzy

                          Patroni medialni i przyjaciele

                          Location