Work methodology

Slack

To have better comunications between different works groups we need next channels on Slack to speak to a especific groups or a specific topic:

• Managers
• Frontend
• Backend
• Meetings
• Marketing
• Off-Topics Also we can create more channels if we think it is necessary

GitFlow

To better work flow we will use a reduced GitFlow with the next branches:

• master: only for stables version.
• develop: only for version in development, when the version is finished, this branch will be merged with Master.
• feature-[FeatureName]: you have to create a branch from develop with this format to develop a feature, when it is finished, this branch will be merged with develop.
• hotfix-[HotFixName]: when you have to do a hotfix, you have to create a branch from master and when you finish the hotfix, you will merge this branch with master.

Commits

You have to do a commit for each work block or when going stop work, the title of the commit always have to start with one of the followings heads (including ":"):

• Feat: when you have worked on a feature.
• Doc: when you have worked on documentation.
• Fix: when you have worked on a fast fix that isn't a feature.
• HotFix: when you have worked on a Hot-Fix.

After the head you have to explain what you have done on one line and use the body to explain troubles or special topics and reference the issue of you work. (Ex. of reference: " refences #[number of issue] " )

If the commit closes the issue then you have to use " close #[number of issue] " or " resolve #[number of issue] "

Merging

After finish your work, you have to merge your branch with develop and delete your branch, the commands would be:

$ git checkout master

$ git merge yourBranch

$ git branch -d yourBrach

Scrum

We work with a reduced scrum, when we start a sprint we have to do a planning meeting, in this meeting we decide what we are going to do in this sprint, throughout the sprint we have a weekly meeting to explain our work during the week. Between weekly meetings we talk to each other with Slack and in small groups. At the end of the sprint we have to do a review and a retrospective meeting, it can be in the same meeting, but it has to be a different mind, we can not talk about revision and retrospective things at the same time.

summary of sprint

• Planning meeting
• X numbers of weekly meetings
• review and retrospective meeting

Issues

A issue is a definition work for a person, only for a one person, this person can ask for help, but if the work have to be started for two persons. this issue is really two issues. A issue have two labels, this labels is for category and priority:

Categories:

• Backend
• Frontend
• Documentation
• Organization

Priority:

• P1-Now
• P2-Very Important
• P3-Mandatory
• P4-Nice to have

Also is very important define when is closed a issue but it depends the category:

• back/front end: a issue is closed when the feature/fix have been tested.
• Documentation: another person who was not the author should review the document.
• Organization: it don't have a clear definition.

Kanban Board

The Issues are organized on Kanban board, it have three columns:

• To do: the issues start in this columns.
• In Progress: When someone start to work on issue, it have to be placed on this column
• Done: when a issue is closed, it have to be placed on this column