For this inaugural deliverable for the team project, do the following:

• Vision statement

  • Write a draft vision statement for your team project. A vision statement is a short (usually a 1-2 paragraph) summary of the high-level requirements and the business case for a project. It should be both clear and compelling. Jeff Atwood gives some useful guidance on creating and delivering vision statements: Can Your Team Pass the Elevator Test? Include a brief, comparative analysis of other related/competing systems.

  Publish your statement and a list of your team members in the README.md file for your main project repo in GitHub (e.g., CS 262 sample project) and be prepared to deliver a one-minute, project-pitch presentation in lab 4 to us and your project stakeholders.

• Prototype

  • Create a (simple) client application for your team project. At this point, it won’t implement any key functionality, but it should at least display a screen with an appropriate title. If you doubt the value of early, potentially simple prototypes, consider the points made by 37Signals here: Chapter 6.1: Race to Running Software.

  Push this application to your “client” repo on GitHub. You will use this as the main repo for your client throughout the semester. Be prepared to demo this prototype.

In addition to the basic deliverables specified in these project specifications, we will check to see that your project management materials (e.g., Slack, Trello) are active and that the whole team is participating. For easy access, make sure that your Slack, Trello, and GitHub links are set on the Moodle teams page.

Note that your team stakeholders, specified in Moodle, will be following your work on GitHub.

Checking in

Submit this work in your team project repository and share it with us. We will grade your work according to the following criteria:

• 40% — Vision statement
• 40% — Prototype
• 20% — Management

These deliverables are generally due by the beginning of the Friday lab period on the last week of their three-week iteration, but this deliverable requires that you use the GitHub repo created in the lab, so it is due at the same time as lab #3.

We’re happy to give comments on any of your project artifacts free of charge if you talk to us about them and publish updated versions before the due date/time.