This product specification document contains the following for foodal: A product plan. A project plan. The product plan is essential, to list all the features. It is a high level vision document for engineering teams, however it lists all the product requirements. In this document, the user interactions display many screens. Usually, if the product is not implemented, there are mocks, whether hand drawn, balsamiq, photoshop or HTML. However, we already have these UI components and user interactions implemented. The screens are real, the code is done, we just need to integrate the components and build the first release candidate, the minimal viable product (MVP). The project plan translates the product plan into actionable tasks, that engineers can understand and implement. The tasks are also sized, so project management leads can create a release schedule, i.e. when the various software releases will be launched. We will use Agile Development methodology for building foodal. The enhancement requests are growing, so we will track them in jira. We will continue to prioritize the backlog and build a product roadmap for next 12 months of software development. Agile development methodology is a handshake between project managers and engineers. For engineers, a task can easily be assigned from jira and we can start working on them. Make sure to size each ticket, so the project manager knows how long it takes to code the feature, or a bug. The code always needs to be reviewed and checked in properly in various code branches on git, git flow via github. The engineers team must follow best engineers practices, for example continuous deployment, and always stay on top of all technology stacks. We will setup Jenkins for continuous deployment, integrated with github and deployed on rackspace cloud servers. Our agile sprint will have a backlog grooming session, sprint kick off, daily standups, demo when ready, sprint postmortem at the end of the two weeks. The agile sprint cycles continue on, over and over. Make sure all tickets are executed as promised, as sized, so we can determine engineering velocity, i.e. how good each engineer is.