После годов труда в качестве разработчика, открыл для себя мир тестирования, где, пройдя путь инженера, занимает позицию Test Team Lead.
Many companies, working both with classical development methodologies and using Agile approaches, risks to get in a trap of the order during working with requirements. This is dangerous especially there, where is much more difficult - even not impossible - to plan the process of creating the specification or the final product due to increased variability of requirements focus that the customer can change daily.
I want to tell my experience of refusal from a flow generated by the customer on the basis of some of its priorities and the transition to the FIFO queue (First in - First Out).
The key to an effective definition of functional requirements is the minimization of incorrect interpretations and ambiguity. Using consistent syntax in your requirements you can improve legibility, to be sure that every team member precisely understands what product needs to be developed. In my talk I will tell how to improve the creation of requirements using Easy Approach to Requirements Syntax (EARS). EARS is a simple and powerful method to obtain functional requirements. High-level requirements to a system are usually formulated in a natural language. Free formulations in a natural language can cause various problems of interpretation of the text and, as a result, influence quality of requirements. I'll suggest the simple manual which will help to write better requirements, will tell how we introduced EARS and what benefit from this we had received.
Analyst and tester. It seems, they are colleagues, whose tasks are densely bound, but, from the other hand, their relationship often is a place of the real battles which brings problems for team and for the project both. I will show a view from both barricades in my presentation will show how easy it can be if no barricades exists at all.
*Pomodoro Technique* – very simple technique, which is possible to learn in half an hour, but it will bring benefit from first minute. Twenty five minutes of work and five - of rest. There are a lot of advantages at such technique. The first one – short intervals of work allow to be tired less, and breaks give the chance to look at work with a fresh eyes. And the second – a full-fledged picture of working day: the number a pomodoros and their distribution between tasks shows your efficiency, showing also ways to improvement.