First, determine your resources. You have a team of only N people, and you have to get the job done by the due date. Establish with your team what considerations are to be taken into account. Does anyone have co-op interviews, midterms, family visits, projects in other courses, etc? Establish any and all constraints that limit your ability to work 24 hours a day, 7 days a week exclusively on the project.
Next, lay out the subgoals (tasks and milestones) that will lead to the completion of the project. These will be such things as the implementation of an entity, completion of a scaffolding, review of a phase of work, revision of a document, etc.
Prioritize your tasks so that you are assured that the most important goals will be met, if you find you won't be successful in meeting all your goals. Order tasks so that the important ones are done by the most appropriate individuals and so that there is a backup person for every critical task. Assign people to tasks and milestones.
Next, estimate times required for each task. Use summaries from past terms, pertinent historical material from the book, your recollection of how long assignments typically took, and educated guesses. You might select an estimation technique from the book that seems most relevant (e.g. so and so many person hours per functional unit, best-worst-median-time average, etc.). The outcome of this exercise should be a list of the expected duration for each task implied by the Design and Test Plans.
Finally, you must make assignments of work to people. How much in estimated time is supplied by each team member? Who is assigned to do what? What team members fill what roles? Who is the final authority on testing? On implementation? On scheduling? On style and form? On documenting? The time-task-person-resource data is the basic input to Microsoft Project (or any similar scheduling tool). The outcome is a time-dependency chart and layout of time lines for each task and individual that provides the schedule for project completion. An important byproduct of these charts is a critical path that is threaded through the tasks whose slippage will impact the final completion of the project. All tasks and milestones on the critical path are to be monitored very closely.
After charts are completed and tasks and milestones are
ordered in time, you will need to establish tracking and control mechanisms
What regular schedule of meeting and review will you use?
What communications channels will you use to keep each other
up to date on progress? What provisions are made for emergencies?