7 ms·

Use Agile for R&D, user Waterfall for D only. E.g. use Agile and smart guys with good knowledge of application domain for first version, then drop it and rewri

• gutnor 14y ago
  It is ok if you don't change anything (or nothing significant) between version 1 and 2. But then, why would you rewrite from scratch ? In any case, if you use a different team to rewrite your application, you just lost the biggest value of the previous team: experience solving that problem the first time. No amount of documentation can really make up for the difference . The source (with doc) of a software is a compiled version of business/technical knowledge of the team that developed it and not really that good as a guide to the next team.
  • vlisivka 14y ago
    > But then, why would you rewrite from scratch? Why not? Professionals knowns their tools much better, so they will made better choices in every aspect of project. If you place restrictions on their tools, they will work less efficient, unless you are already professional developer. > The source (with doc) of a software is a compiled version of business/technical knowledge of the team that developed it and not really that good as a guide to the next team. Of course. They will ask questions, so somebody from first team should respond to them.
• kragen 14y ago
  Use agile for R&D, apt-get install for D only.