Team Cyclopaths Manifesto

Personal goals for the project:

Personal goals of the project are to:

1. Make an impressive app that has a decent ammount of functionality and looks good - ie not something so overly ambitious that we learn lots of new tricks but end up with a page saying "Hello, World"
2. We build an app that reinforces our knowledge of the tech languages and tools that we have already used on the Makers course to date, specifically:

• JavaScript
• Ruby on Rails
• API calls

3. Uses elements of new technologies that stretch our knowledge and allow us to learn new and useful skills, specifically:

• A React.JS front end.
• An add-odd feature written using Python (a language that we have not used to date on the course)

Working routine:

• We will build the App using Agile best-practice in two-day sprints.
• We will prioritise shared learning above creating a maximum number of features. We will take the time to explain to each other the areas that we have been working on in order to ensure that ALL team members understand ALL technologies in the App.

We will have the following team meetings to ensure we are all on track and that our learning development is tracked:

1. Planning sessions at the beginning of each sprint. These sessions will identify the user stories and features to be developed over the next 48 hours. Specifically, these planning sessions will:

• Identify the features to be developed in the next sprint.
• 'Group average' estimate the time needed to develop these features.
• Allocate agreed tasks to coding pairs/trios.

The first planning session will take place on the morning of day 2 (Tue 29 Oct).

2. Stand-ups at the beginning of each morning (when there is no planning session) and after lunch. The purpose of these will be to make sure all team members are on track and not blocked on any particular issue.

3. Team Retrospectives at the end of each day to ensure all lessons learnt are captured in this Wiki. Each team member will be responsible for updating their own lessons in the wiki. A nominated team member will be responsible for noting down the key lessons from the retrospective sessions, and chasing individual team members to update the wiki.