Skip to content

Latest commit

 

History

History
40 lines (27 loc) · 2.44 KB

ProposalTemplate.md

File metadata and controls

40 lines (27 loc) · 2.44 KB
Raw

Final Project Proposal Submission

The following is due Sun, Aug 9 at 10pm:

*note: this deadline has been revised...An earlier version of this said it was due at 6pm.

Please create a repository for your final project, with the following contents:

  • README with your group members
  • ProjectProposal.md (template below. Feel free to use the markdown from this file and fill in your responses.)
  • Your app
  • Folder that contains Weekly Retros (template here). (Empty for now)

Access Code 2.1 Final Project Proposal

Please submit the final project proposal by 10:00pm on Sunday 8/9/2015. You will receive feedback on the proposal on Tuesday 8/11 and be asked to review and incorporate this feedback, and resubmit a revised proposal by 10:00pm on Tuesday 8/11.

Project Name
Team Name
Team Members

The Problem

Describe the problem that your app will address. This does not need to be a novel idea or product, but your app should not directly recreate an existing product. If you are basing the app on an existing product, there should be some edge to your design or feature that solves a problem with that existing product.

In this section, please frame the issue with supporting statistics about the need (market size, competitors, use cases). You should fully think through your user - who is your user? Why do they need this app? How are they using it?

The Solution

Please provide a detailed description of the app here. Map out how the app solves the problem described in section I. You should also include:

  • Baseline features you plan to implement by Demo 1 (what + why).
  • Bonus features you plan to implement if baseline features are completed in time (what + why).
  • A wireframe of the app.

Execution

Please describe how you will build this app. Include:

  • A detailed timeline for building the product, broken out by weekly sprints. Implement the training from the Project Management workshop to plan your sprints and outline which features you want to build out over the next 4 weeks. Think about the user stories you would frame your sprints around. Projects should be planned to complete the build by Demo 1 on September 1, 2015.
  • A breakdown of team member responsibilities. Team members should take ownership over a specific feature or aspect of the app.