Note: You will be turning in revised versions of these documents two more times throughout the semester. So you probably want to make sure they are produced in an easily modifiable way.
Name of team members
Overview of system you will be building
Identify your customer and expected use scenarios (tell story of who will use your system to do what, hardware and software
needed, description of problem being solved and target user)
Requirements and priorities of your customer
Priortize list of functionality or use scenarios ( what pieces will you do first, possibly scope out several iterations of a working system to manage risk, time estimates for achieving each one)
A proposed project schedule identifying interdependencies among
team members, major checkpoints, in the form of a GANT chart (Immendio Planner)
A description of any structure within the team
A list of the top risks
you will face in meeting the proposed schedule and
a plan for dealing with these risks if encountered
Description of any "spike projects" you have completeted or plan to complete to validate your approach/schedule/estimates (could also describe previous experience with technology being used)
A description of the development environment you are planning to
use: hardware and software needed for development (programming language, compiler, any important libraries or tools, operating system, hardware requirements, etc
A description of the records (project metrics, time tracking) you will to keep
A description of
the tasks they are personally going to do
Personal estimates of the time
it will take to perform each one including a justification of how
those times were estimated
A description of dependencies on the work of
other team members
A list of any "unknowns" things you
must learn or try before you know whether you can complete the
tasks assigned to you and a plan with time estimates for
investigating these unknowns.