Episode transcript The transcript is generated automatically by Podscribe, Sonix, Otter and other electronic transcription services.
Hello everyone. Welcome to the Five Minutes Podcast. Today I like to go back and reinforce that there is no one size fits all solution. You know, in life we love in many times we are trapped by, I would say, articles or by authors or by consultants, always pointing, Oh, there is one magic solution. Apply that to your project will be successful, your team will be happy, and your company will thrive. You know, it's not as simple as we would love it to happen. So most of the time the solutions are complex, and the scenario is complex. And it's not easy for us to find a very simple tool or a very simple method that is able to address everything. Let me give you an example. Let's suppose you have a manufacturing company or even a software company. You should not believe that, okay, one approach to project management will solve. Don't think that, for example, Microsoft or Google only use one type of method or one type of tool for every single project because this is not true and this is not what happened, and this is a brutal simplification of reality. So what is for me critically important? I mentioned this many times your company or your PMO or your project delivery approach must have a set of principles. And these principles, as I said, they guide behavior. And they became very popular with the Agile Manifesto. The Agile Manifesto is a set of principles.
When they say that they prefer working code to documentation, it's clearly saying if you need to prioritize, it's more important that you prioritize the quality of the code than the documentation. But it's not saying how you should do that. The PMBOK Seventh Edition with the 12 Principles brings to the Seven Principles of PRINCE2. They are all underlining aspects that aim to guide behavior. I'm not saying that you should use one or another or all of them. You need to have a set of principles in your organization that will guide your approach toward the projects. Your next step is to develop a toolbox, a toolbox. And this is the key to tailoring. You need to have a toolbox that gives you the ability to address the individuality of every single project. For example, this is why I like to study different things. I like to learn tools and techniques. I like to learn methods. It's not because I would say, oh, this method is better than that method. No, no, I want to say, what is the most suitable method for that specific case? I gave you this example before. Imagine a Swiss army knife and you have a knife and a scissor. Both of them, have produced their tools to help you to cut things, but they have different uses. For example, if you want to cut paper, probably a scissor is better than a knife. But if you want to cut a cable or a hope, it's better that you use a knife.
So this is the toolbox concept. Many times I mix everything and this is tailoring. When you do tailoring, you use the best approach and the best set of tools for that specific project, to that specific scenario. This helps you to deliver a solution that a project management solution or a project management method or a project management toolbox that will help you to address the specific needs in that specific area of your company. This is why you should never create, I would say, a single roadmap or detailed roadmap for every single project. You can create a set of principles that can be applied to every single project, but different projects will require them. And they may require very different roadmaps to go from the idea to the reality. And this is why it's so important. And this is why, for example, we were talking about the jobs report of PMI recently. They just released it about the job market. One of the key competencies we are looking for today in project managers, scrum masters, team managers, the product owner is their ability to be able to understand the different methods, and the different approaches, and tailor to that specific case. This is what really makes a big difference for those who are working in this area.
So think about that and see you next week with another Five Minutes Podcast.
