Yes, haveing something pushed down on the developers is not very agile.
The fact that you didnt know this tool, should have pushed the
estmations thru the roof.
Haveing one or two guys doing the research and poc, is better than
haveing the whole team craming in.
Look at what Maven has to offer thru all it's plugins. I bet you will
something of good use.
Sendt fra min iPhone
Den 23. feb.. 2009 kl. 18.40 skrev "Todd Thiessen"
<[email protected]>:
The issue to us was fairly simple: We had a working build
process. The developers knew the project. Everything was fine
and dandy. We moved to Maven and lost three weeks of work.
Developers don't understand the new process as well as the
old process, we've fallen behind schedule.
I am sorry it didn't work for you. All I can offer is what we did in
our
environment that worked well.
We assigned one individual to research Maven and worked towards
Mavenizing our project. Everyone else continued working on features
using the ant process. So very little work was lost. Once a stable
Maven
environment was acheived, the rest of the team was cut over. There of
course is a learning curve here but the rest of the team didn't need
to
get it working, but rather they had to learn how the new environment
works. This saved a lot of frustion between developers.
Maven is now starting to spread like wildfire ;-).
At any rate, I don't think anyone should be trying to shove Maven down
your throat. It is good to share experiences and I am glad you have
shared yours. I hope it works out better for you in the future.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
