It's because of that, I tried to define at a very high level steps and tasks for a methodology that I think it's valid for little and big projects. This methodology is based on my own experience on ERP and other propietary software deployments. When everything seems to be trivial and easy and you think control is not necesary, something happens, project returns more complicated and problems could appear.
Of course this is still first step, but I can tell you I'm applying it by now and it works. But It's true I loose a lot of time trying to follow it with different tools instead of having everything under control with OpenERP. I think normally many people considers a deployment as a development project and it has nothing to do with that. Imaging a deployment with quality modules. imaging a deployment even with Odoo. In that case, if customer wants to contract some consultancy, learning or functional support, that is a project and it should be controlled like a project, even if customer does not need customized developments. ------------------------ Manuales, Videotutoriales de OpenERP en http://www.openerpsite.com http://www.aulaerp.com -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=41148#41148 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
