The workshop addressed to those who tried to start risk management in their projects but not satisfied with result. On this workshop we consider how to start risk management, how to identify risks, how to (and why!) Classify them, how to choose management strategy and how to introduce risk management into your project.

An analyst is the right (and often the only, forgive my cynicism) a manager's hand. And this hand could hold manager and help to avoid the typical errors associated with cognitive biases. In my report, I will talk about mistakes, which could be avoided if the analyst takes advantage of his or her knowledge in time. By the way, it works in both ways - manager can often return the analyst to the right path with timely question. This theme is not the first time rises on conferences. And Daniel Kahneman's book "Think, fast and slow" is becoming a must read for anyone. But I think it is important to return to the subject, if we want to make fewer errors. Yes, we can not protect against accidents, but by systematic errors - have to.

It's not a big deal to start and to finish a project. The difference is in detais - is it before or after deadline, is the budget exceeded or not, is the result useful. This details is the only defference between companies. Companies, not managers, because an attention to this details is a part of project management culture in company.

In my report I'll tell about our experience in goal-based project construction and our results. I'll show on real cases how to construct a managable project and how to make risk management and desision making in project more predictable.

The key to successful work with the client is the ability to find a personal approach to him. Successful product must also be able to find this approach. It isn't enough just to release a product to the market - to gain recognition, it must also become a convenient and intuitive tool for each user. We'll talk not about user-friendly interface and usability of the product as a whole but its ability to adjust to the specific user and his tasks.

In my report i'll tell about approaches to customization of the product, the complexity arising from the use of simple solutions and implementations for different situations. We'll see what is customization, who needs it, why you have to deal with it and what to do to lessen the problems of refinement of the product for a specific customer and at the same time to make benefit.

The key to successful work with the client is the ability to find a personal approach to him. Successful product must also be able to find this approach. It isn't enough just to release a product to the market - to gain recognition, it must also become a convenient and intuitive tool for each user. We'll talk not about user-friendly interface and usability of the product as a whole but its ability to adjust to the specific user and his tasks. In my report i'll tell about approaches to customization of the product, the complexity arising from the use of simple solutions and implementations for different situations. We'll see what is customization, who needs it, why you have to deal with it and what to do to lessen the problems of refinement of the product for a specific customer and at the same time to make benefit.