Product Description: What is your product? What generally does it do? What is the target audience you expect to use the product? Why is it interesting? • Software Toolset: Will you use any software tools or libraries in addition to the required ones? How well do your group members already know the tools and languages you will be using, versus how much will they have to learn? Briefly explain why you chose these tools and languages, as well as why they are suitable for use on this project. • Feature Set: What are your product's major core features? Include at least 3-4 major features your product will provide, along with at least 2 other minor features or aspects you hope to complete. • Alpha, Beta, V1 Breakdown: You will have roughly 2 weeks to work on each real coding phase of the project: the initial Alpha version, the second Beta version, and the third "Version 1.0" (V1) completed version. How will you divide up the work between these phases? For each of the three phases, which features do you expect to be complete, which will be started, and which will not yet be started? Why have you chosen this particular division of the labor? • Risks, Cuts, Adjustments: It's very difficult to predict exactly how much work a group will finish in a given amount of time. Describe at least three specific adjustments you will make if the project begins to fall behind schedule. Two of the adjustments you list can be feature cuts, but at least one must be some other change or cutback, such as changing specific areas of testing, adjusting your group dynamics or time schedule, etc. • Group Dynamics: For the most part, your group organization is up to you. However, we require that you choose a single person to serve as your Project Manager (PM). Who will be your project manager? What will be the other members' roles? Will you split up the work by features? Will each person work separately, or will you have subgroups within the team? Why have you chosen these roles? If a disagreement arises, how will it be resolved?