Setup and installation

I would also like to see an example of how this works.

Thanks,

Sorry for the crappy UI, the currently released version was a bad hack in this respect. I reworked the module so that it can derive the users and open tasks programmatically from the other fields, so that you'll get an easier interface in the new version. I'm going to upload it today, which I didn't up to now because it requires one more dependency, my new "Value Providers" module, which I hadn't made into a project. Plus the new version only works since yesterday anyways, but it's now much cooler. (At least, I hope you'll feel this way too.)

No docs from me as I'm leaving the Drupal community for at least half a year (sorry), if you want to get involved then please contact fago who now has co-maintainer privileges for this project.

* "A "Node reference" CCK field linking to the project that contains the task" - Does this mean that content type "task" contains a CCK nodereference to content type "project"?

Yes, a "task" must refer to a "project" because time budgets are specified per project and the estimation is calculated based on that fact. In the new version, you can theoretically use another node reference mechanism than CCK by creating a new "nid" value provider, but for that you need to code one. In our company, we're currently using a slightly hackish solution to have the first node listed in Organic Groups' "Audience" field, and in principle everything will work that can retrieve a "project node" nid via Views and parse function. But as I said, you need to code a value provider for that. (Which is easy to code, but might not be feasible for non-coders.)

* "A "Number" or "Duration" CCK field that contains the time need for each of those tasks." - Where is this field to be located, in the "project" or in the "task" content type, or in both?

In the "task" content type. This specifies how much time is left in order to complete the task where the field is in. For the calculation, the view of open tasks is processed one by one (in order of the view), and for each task, Project Forecast looks if there is enough time budget left to complete this task (= more time budget left than time need specified). If the task can be completed with the available time budget in any given week then that week is the estimated completion date for it. If it can't be completed, no estimate is given, and the "Estimated task completion date" in the view stays empty.

Hope that answers most of your questions. If not, sorry, but I don't have the resources to put any more work into this in the near future. Maybe I can still add the one or the other feature after I come back from my trip abroad in a month, but for the time being this is pretty much a assemble-it-yourself-without-further-assistance module. Which hopefully works better in the new version (wait for 6.x-rc1 later today).