Your plan must have a calendar, with both group and individual views, a complete hierarchical breakdown of the plan to five-hour or less tasks, with a name associated with each task. You should have a total time for each level of the hierarchy, and a must have a total time for the whole project. You must have a dependency graph for the tasks, and have defined a critical path through the project.

We will go through these features twice. The first time you pick interesting items that recommend the group. The second time you let us pick to prove that the whole project has been planned at the same level of quality.

1. You pick: Show the group view of the calendar by "click"ing on any part of the calendar to show details of who is doing what for that date.

2. You pick: Show the individual view of an active group member so that we can clearly see the collection of tasks for which she is responsible, and what her or path through the calendar looks like.

3. You pick: Show the dependencies for an interesting module, showing what else has to be completed first, and which other modules depend in this module being complete.

4. We pick: Show the group view of the calendar by "click"ing on any part of the calendar to show details of who is doing what for that date.

5. We pick: Let us choose an individual and show us the view of that member so that we can clearly see the collection of tasks for which he is responsible, and what his path through the calendar looks like.

6. We pick: Show the dependencies for a module we choose, showing what else has to be completed first, and which other modules depend in this module being complete.

7. Demonstrate how your planner acknowledges completed tasks in the group formum. Good job!

8. Give a static (or dynamic if you have software) example of replanning, and how dependencies are re-scheduled. That is, give an example of how something would be re-planned. Show us before, after, and the changes to the calendar that would be required because of the dependencies.