Communote - Die neue Art der Zusammenarbeit. Communote ist die Kommunikationsloesung fuer projekt- und teamorientierte Unternehmen. Social Enterprise Network made in Germany.
On one of the Microsofrt conferences the key speaker asked the auidence (mostly developers) who uses a standard methodology and who has some home-brewed.
Approximately one-third followed a standard, one-third had own methdology, and the rest had probably nothing.
The question is very good, i also wouldnt go to a company without a formal method for development. Especially if the PM happy with this. Usually the developers are against a method and the PM who can enforce it.
Developers tend to develop on their own way, they get upset if somebody wants to tell them how to do programming.
(I guess he wasn’t a real PM, just a fake one)
But you MUST have a method, even if the folks don’t like it. If you don’t have starndards and you don’t document, then your project will fail.
Even if the project starts as small, there is a chance that it grows, you add a few more developers to the project, and then all will collapse because of the lack of procedure and documentation.
It is funny you mentioned agile development. When people don’t want to follow formal method, they claim they prefer agile development. But what they are really doing is cowboy programming.
I like the cowboy synonym. Although, I am pretty sure that the real cowboys had strict procedures, cattle are prone to wander off either with help or on its own if you are disorganized.
As for the general Agile practice, I think here you can find some explanation: Dilbert on Extreme and Agile Programming
zum Blog 
On one of the Microsofrt conferences the key speaker asked the auidence (mostly developers) who uses a standard methodology and who has some home-brewed.
Approximately one-third followed a standard, one-third had own methdology, and the rest had probably nothing.
The question is very good, i also wouldnt go to a company without a formal method for development. Especially if the PM happy with this. Usually the developers are against a method and the PM who can enforce it.
Developers tend to develop on their own way, they get upset if somebody wants to tell them how to do programming.
(I guess he wasn’t a real PM, just a fake one)
But you MUST have a method, even if the folks don’t like it. If you don’t have starndards and you don’t document, then your project will fail.
Even if the project starts as small, there is a chance that it grows, you add a few more developers to the project, and then all will collapse because of the lack of procedure and documentation.
It is funny you mentioned agile development. When people don’t want to follow formal method, they claim they prefer agile development. But what they are really doing is cowboy programming.
This comment was originally posted on http://fracturedbloughts.heszroland.hu/)”>Fractured Bloughts
I like the cowboy synonym. Although, I am pretty sure that the real cowboys had strict procedures, cattle are prone to wander off either with help or on its own if you are disorganized.
As for the general Agile practice, I think here you can find some explanation: Dilbert on Extreme and Agile Programming
This comment was originally posted on http://fracturedbloughts.heszroland.hu/)”>Fractured Bloughts