-
Notifications
You must be signed in to change notification settings - Fork 0
1. Team Development
The SimCoast team uses Trello to organize our tasks and divide them among team members. Our strategy is based loosely upon Agile development, but pared down to be compatible with the more flexible lifestyle of students as opposed to the structure of a full-time employee team.
This section of the board is dedicated to, as should be clear, general information that is necessary for all team members. This currently includes meeting times and the Label Key.
As of now there are 6 different colored labels that we can use for our Trello cards, so that developers can tell at a glance what areas of SimCoast a given card touches. These are:
- Green: Documentation
- Dark Yellow: HUD
- Orange: User Interactions
- Dark Red: Bug Fixes
- Purple: AI/Core Mechanics
- These are things required for the game to run, such as desirability calculations, population tracking, and the economy AI.
- Blue: Features
- These are features that will not "break the game" if they are absent. This includes things like weather, or adjustable tax rates. These features are good to have and important to the game, but theoretically could be removed and the game would still be playable.
The Backlog is where all cards start their life cycle. Any concrete changes, bugs, feature additions, etc. will be added to the Backlog with as much detail as possible when they are deemed realistic goals. This last part is crucial, since we don't want the Backlog filling up with tasks that we won't be able to tackle for months.
Cards in the Backlog do not need to be claimed by any developer. Once claimed, cards do not have to be removed from the Backlog. Cards should only be moved out of the Backlog when work is being actively done on them.
Cards from the Backlog that have been claimed are eligible to be moved here. Once a card has had active development (i.e. actual lines of code being written), it should be moved from the Backlog into this section. Cards should not remain unclaimed in this section.
Cards from In Progress can be moved here once their task is completed--or at least when the developer believes it to be completed. Once moved to this section, a Pull Request for the card should be opened in this repository. At least one reviewer should be requested on this Pull Request as a general rule for good practice, but there are no enforced protections on this repository that require that review process to take place. Once open, the Pull Request should be linked in the comments of the Trello card, so that other developers can easily access any features in review.
Cards from In Review may be moved here once their Pull Requests are approved and successfully merged. As of now there is no protocol for removing cards in the Completed section, so please do not remove/archive/otherwise disturb cards in the Completed section unless necessary. Typically, cards transition from In Review to Completed during the weekly developer meetings, since that is when everyone is able to sign off on a given Pull Request.