[MUSIC] Delivering IT products and service is about resolving contradictions. The stakeholders have different objectives. The business they want to have as soon as possible a cool solution fully customized to their needs. The IT project manager, they want to deliver something that works on time and on budget. The IT operations guy, they want a robust solution, easy to industrialize, with no bugs, and a great security level. At the end of the day, it's very hard to add up all those requests, all these contradictions. So you have to make a compromise. Making a compromise creates inevitably tensions because it's about having all of those stakeholders converge on agreeing on something. If you don't mange this compromise development at the end of the day, you will have to face a huge conflict. The solution doesn't work. The project has huge overruns, a lot of delay. You have a major security breach. This is tension. If you don't want to have to face that situation, you'd better resolve the tensions ahead of time, so that you can work on the compromise together. There are two ways to do that. First way, quite obvious one, is involve all the stakeholders ahead of time around the same table, so they can come together to a compromise, identifying the contradiction, and solving those contradiction along the course of the project. Now, another way to do that which is much more holistic and comprehensive is about defining an architecture, about defining what are the rules, what can you do? How do you want to get organized? Because otherwise, you're going to pile up tons of inconsistent requests and it's going to be a big mess. Defining the set of architecture IT policy has to cover application, data and infrastructure. For application, what are the softwares I want to use, those I don't want to use, how do they come together? What is the level of customization that is allowed? For the data, what are the rules in terms of data security, in terms of data storage? For the infrastructure, what are the types of material we want to have? What is the differentiation in terms of service level? If you have defined that clear set of rules, easy to understand, easy to explain, then you can put that on the table for any project, any offer development, and the rules are clear. People know where they are going. Of course, you will have tensions as you have in the course of any projects, but at least no bad surprise.