How much agile are your processes?

Some times we read opinions about the stiffness of traditional development methodologies versus agile methodologies. In many of these it is confused models with methodologies. As I understand it, a model tells you what to do, while a methodology gives guidelines on how you can do it. I see it totally complementary and necessary.

I imagine that phobias against models come because of stiff processes have been defined and phobia against agile comes because of understanding the agility as an excuse for anarchy.

As virtue is in the middle, I would like to express my opinion about what should be done, and see examples of how we can do it.

In any project we have to take special care about the expectations of our client's requirements. If we want to obtain a profit, we must keep track of the changes, as these aren't free, they can have a big impact on that we have made. We probably have to rework on something finished. Then I don't understand how somebody can say that as the agile methodology is, we do not need:

• Requirements management
• Changes management
• Project management
• Test management
• Configuration management
• ...

If your project is run by a team of medium size, it is bestter that your system will be a collaborative management. That all members have access to the latest information and latest known dates. Each team member must know who is doing what and in what state it is. It may be that what the person is doing on your right, it will be need by the person you have on your left.

How to implement all this effort?
What support tools are you using?
Do you have more or less established process?

When the project size rise and / or the number of simultaneous projects rise and / or when you go to pass from an informal group to a company known as serious one, or you have  a model, using a methodology and defined processes or it will be very difficult to have everything under control, and sooner or later you will be in trauble.

Stories should not told by anybody. We can not improve that it is not there, so we need a process to be improved. We can not know that we do not measure or observe, then we need to measure in order to compare the previous with present.

You need a quality model. You need a methodology that is aligned with your quality model. You need a process to help you following your methodology. You need that one that fits your personality better and with your organization. To summit that one that will help you to identify how you can be more competitive.

The question should be: How much agile are your processes?