Hi,
First of all, thank you for your interest. I'll try to give you some answers. 1) The demo data were just corrected by me right now in the last module version, so it'll be more clear to understand how things are going. I think there is a missunderstanding: The methodology divides a project in four phases: Overall project planning, Functional analysis of all processes, Deployment by iterations and Project closure => Yes, this is the main structure and bring a overview of the planning and thing to be implemented. But then, in the deployment process, every iteration has his own planning, analysis, deployment, and closure => This are the steps ! Steps are the different "phase" of an iteration. 2) In our vision, the analysis GAP contain every question related to the "sale" phase in the way that we need to identify how big will be the work to integrate OpenERP. But, the preparation phase is more about the sale process it-self. We imagine that the sales man can select the functional bloc needed for the customer and ask for the tasks related to the "preparation" phase. Doing this, you'll receive a list of "good question" to ask the final customer in order to make a quote. 3) I think yes, agile_methodo_support is more about managing the iterations their-self as an Agile project. Every iteration contain every steps (phase). But, we though that we can summarize the planning, the functional analysis and the project closure in tasks related to the main project. Doing this will allow you to deal with those phases. 4) We do not handle our support with that module. In fact, the support is a project in their self... We need other tools, like request tracking, etc.. So We usually start a new standard project to manage support tasks and so.. A last things, I do not know if it is clear how to build a project with this module : a) Create a New Draft MODEC project, choose type and version b) In the fourth tab, create every needed iteration. In each of them, add the wanted functional bloc in the MODEC tab. c) Open the project. This will create for every iteration the related tasks according to functional bloc, project type, step and so.. d) To now what to do, use the Get specified task from project and ask for the task to be done (for a certain functional bloc and step, like Finance + GAP analysis). I hope those explanation are enough. I remind that this module is only a proof of concept. We want to improve it with your ideas and remarks. We also will work closely with OpenERP SA to merge their own vision and our work, so at the end, we'll have a unique methodology for OpenERP. Best regards, Joël P.S. Link to the methodology doc: http://www.camptocamp.com/images/stories/c2c/corporate/business/20100323_agile_openerp_methodology_description.pdf ------------------------ Joël Grand-Guillaume <b>Camptocamp SA</b> PSE-A EPFL CH-1015 Lausanne -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=54411#54411 -------------------- m2f --------------------
_______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
