For over 20 years he has been a legal advisor for intellectual property and new technologies. He took part in hundreds of implementation, service and outsourcing projects, working both for providers and clients. He took part in creating shared services centers in capital groups, led lawsuits and arbitrations from IT and intellectual property fields. He is also advising on administrative and tax laws concerning IT. In recent years he has been taking part in agile projects as well as cloud computing and SaaS projects. He cooperates with legal departments of leading Polish companies from energy, ITC and finance sectors.
Technology law lecturer at Warsaw University (MIM UW) and at seminars and conferences connected to IT sector.
He is sure that well-written contracts help significantly decrease project risks and does not believe that contracts are only written for bad times.
Agile is nice, I like it, everyone (almost) likes it. But what happens if we have a real problem during a project? If we can’t agree what a user story means, who makes what, who is responsible if all our data vanished. The „pure” agile contract is quite different from the „waterfall” one, at least in Polish legal system.
If you are a vendor, usually it’s not bad for you. If you a client you need some not-so-common construction inside the contract to help. Real life stories, real life problems.