Conferences for professionals in the information technology industry

Казяк Евгений

Stone Labs


How to Stop Worrying and Start Talking With your Customer


Case: finally you are entrusted to lead brand new and prospective project. You are preparing to bask in your glory and predicting quick promotion because you'll deal easily with this task. Nevertheless, the sooner is your first meeting with the customer, the bigger are your fears. What are you going to talk about? How should you impress the customer by seriousness and professionalism as well as become his fellow? And if the customer is thousands of miles away from you?  Let's try to figure that out.

Here is what we'll talk about:

  • Communications - types, approaches, basics
  • Interview - how to get maximum of profit having minimum of time
  • Remote communications - let's make it effective
  • Stylistics - what should you keep in mind
  • Cases)
Audience level
Regular Talk (40 min)

Remote workers, offices and outsourcing


Good news, Everyone! We've got a big fat project! But look like we've got a problem here - all our onsite developers are 200% busy at other projects and our chief tells us to find executors as soon as possible. After rummaging in local market you realize that all "correct" people are already occupied and have no willing to change their job. What would be our plan - look for remote workers, open new development office in another city or outsource? Let's try to figure that out.

Here we'll talk about:

  • selection, training (?) and motivation of all remote workers
  • tips and tricks regarding remote office
  • outsourcing - is it possible?
  • real cases
Audience level
Regular Talk (40 min)

Mobile Apps Prototyping

Probably every company has faced the following problem - you are starting new Mobile app with really outstanding idea. All tech processes are adjusted and the project is being developed by experienced developers, designers and QA engineers. Seems that everything should be fine, but when the app was uploaded to the App Store the users receive it coldly. "It's so inconvenient, the app's logic is unclear at all!" - they say. Then we try to find out whose fault is it and blame everyone - the Designer has done wrong Interface, the Developer hasn't thought over the logic. But everyone forgets that all team members' work is based on one initial document - the Specification. And usually the root of all problems is hiding here.
Audience level
Regular Talk (40 min)
Code copied to clipboard