Team Assignments

Team Project Planning Guidelines

Week 1
Tuesday

Team formation
Introductions Renegotiate Team Pizza Make preliminary Job Assignments

Create name tags for new hires.
Create Team Vision (pg86) and Expectations.
Everyone reads Project Plan. Study carefully the sections that pertain to your job description.
Change Control Manager creates CVS repository on team account (if necessary).
New hires: Read all team project documents from last quarter and critique using QA standards and bring suggestions for improvement.
Returning team members: Brainstorm a task list of activities needed to bring your product to a stable state where it is ready for further development work. Assign action items and begin work on these tasks.
Create budget and cost estimates.
If you don't have an individual falcon account, get an account form in the CSL and have instructor sign it.

Week 1
Thursday

Finalize job assignments
Each person presents a "mini" project plan for the duties associated with their specific job role. Include "mini" deliverables and a detailed calendar.
Team mgr combines "mini" calendars to create Detailed Schedule showing Release Dates.
Begin revising system design as needed.
Each person customizes documents related to their role based on course templates, post on team web site.

Update Team Home Page with

Reorganized format according to 206 template
new team members, job assignments, and contact info
draft Staged Delivery Plan, ready to be negotiated with instructor.
Verify that team home page is correctly linked from class web site.

Week 2
Tuesday

Finalize Staged Delivery Plan approved for Release 1 and 2.
Individuals write pseudocode for their Stage 1 modules.
Schedule Informal Review sessions for psuedocode.

#3 Week 2
Thursday

Source code files containing class & method definitions and javadoc comments is available in CVS.
Write Daily Build procedure and test it.
Finalize Detailed Schedule
Revise Risks List
Post Progress Indicators and calculations
Design revisions due today.
Pseudocode Internal Reviews for Stage 1 modules happen about this time.

At the end of week 2,

the team web site should have all documents linked
all project plans should be customized and complete for your team
all procedures in place and being carried out
tracking and reporting underway
everyone should be carrying out all of their job duties.
Daily Build begins today.
Pseudocode is reviewed.
Do System Test Training Activities.

Beginning Week 3

Write System Test Cases.
Unit development can begin in parallel with writing System Test Cases (See McConnell).

Due at the end of the last lab meeting.

Read Chapter 18 in McConnell (5 pages).
Hold a Project Review Meeting as described in Ch 18. Submit a written Post Mortem report after the meeting.