A few days ago I was with a friend talking about technology, and he told me about Agile Methodology. He told me that all projects can be managed using agile methodology with Scrum. Of course, I stayed listening for a long time. In the end, I asked a simple question: What kind of project are you talking about?
We know that a project delivers a unique product or service that has a start and end date. [very good to start]
Why is so important to understand the kind of project we will manage to decide the best methodology? For some projects, like the building of a bridge, is important to map all the requirements before we start the project. In this case, normally we do not change the project during the execution. In this case, we need to define a budget before we start it. In this case, is better to use traditional methodology.
But, if we are talking about software projects, it may be a little bit different.
What we really have before we start the project:
- The customer never has all the ideas in mind;
- The ideas are not enough clear;
- The environment may change.
We need to be capable of adjusting our direction quickly. In my opinion, the Agile team accepts the changes with more resignation.
The project manager needs to understand the project objectives and all the environments around the project to decide the best methodology.