The big problem with intrdoducing schemes like Extreme Programming is that they are usually met with a chorus of scoffing from coders. Nobody likes writing unit test plans for every piece of code they write. Most coders want to dive straight into the code and ask questions later. So the big challenge is to convince coders of the huge benefits of such schemes, even for teams of experienced coders who are often harder to convince. If the coders aren't fully convinced that its a good thing, they'll put in a half-assed effort, or they'll try to debunk it, and it won't work.
How to convince them? Theres only one way I can think of - first hand experience, being put through a full software development cycle with Extreme Programming style procedures in place - and at the same time, motivating the coders to give this new thing a proper try. A big ask.
Slashdot Mirror
The big problem with intrdoducing schemes like Extreme Programming is that they are usually met with a chorus of scoffing from coders. Nobody likes writing unit test plans for every piece of code they write. Most coders want to dive straight into the code and ask questions later. So the big challenge is to convince coders of the huge benefits of such schemes, even for teams of experienced coders who are often harder to convince. If the coders aren't fully convinced that its a good thing, they'll put in a half-assed effort, or they'll try to debunk it, and it won't work.
How to convince them? Theres only one way I can think of - first hand experience, being put through a full software development cycle with Extreme Programming style procedures in place - and at the same time, motivating the coders to give this new thing a proper try. A big ask.