proposal

Project Proposal Guidelines

• The project proposal should have the following structure
  • Context and goals for the project, namely
    • The context where the project outcome (the product) is going to be used.
    • Which problem does the product aim to solve.
    • How is the product going to solve the problem.
    • What are other products that aim to solve a similar problem.
  • A brief overview of the product's elements (e.g. an android application, a Web site) and functionality.
    • This product description should be short and concise.
    • A more detailed description can be present in the proposal appendix. For using facing products, this description can use user stories.
  • A brief overview of the product's architecture
    • An architecture is defined by a set of elements/components, the relations between them and the technologies supporting their development and execution.
  • A brief overview of the project's main risks, i.e., the things that can go wrong and affect negatively the project outcome.
  • The proposed weekly calendar, with the tasks and outcomes planned for each week.