Comment 5 for bug 882528

The organization of a project is not natural for new users. Most newcomers are used to work with MS-Project or alikes products, and thus the first approach is to think in projects and interrelated tasks, where dependencies among tasks are defined at the task level.
The two path approach of OpenERP (Projects with tasks OR projects with phases and tasks, with different schedule methods and additional object like project phases) is counter-intuitive
In memory project managers use to reschedule and compute on the fly dates whenever the user change task status or dependencies. Perhaps on OpenERP is technically difficult to get this kind of response, but at least rescheduling should be handled on the project form, whithout different paths for project with phases and projects with just tasks.
Additionally, it seems counterintuitive not to have programed start and end dates on tasks lists. For the user is most of the time the only important information to watch.
It is also to note that with the current approach of navigation, in the case you have a list of several projects with many tasks, whenever you change from project to tasks or when you are assigning task dependencies, you loose the domain information, and thus you keep entering the project name in the search view to keep the list at an usable size