How is your team work organized?

Question

Project management

The three of us are working on a remote project for Canadian customers.
There are svn, some discussions on skype, but everything is somehow in a heap and unorganized.
Tell us how your work is organized and how best to build a process?
Github, code review, CI, task manager, etc. What services do you use?

Answer 1

I recommend Bitbucket !
You can create a private repository, create your own wiki in it .
You can create your own team and create repositories for different projects in it.
There is built-in integration with HipChat . You create a room for your team and all the commits that you make will arrive there. And the chat is pretty handy. Saves links and files in history.

Answer 2

Slack -> TargetProcess (Kanban) -> *Process* -> Git
Such a bunch has formed over the year. Yuzali first Asana, but it turned out to be not very convenient even with Slack integration.

Answer 3

Skype, Gitlab.
In the gitlab repository, as a bug tracker we use the same issue in the gitlab.
We thought about Redmine, but decided that we don’t need it because it’s clearly an unnecessary functional.
I found a problem, started an issue in a turnip, corrected it, boasted, closed the issue :)
But no one is above us and we control ourselves.

Answer 4

JIRA, Slack, GitHub, Google Hangouts.
Our team is divided into the main one in the office and remote workers.
All projects are maintained in Jira, it is integrated with GitHub & Slack. As soon as the task changes status, it can be seen in the slack. Commits and pull requests contain issue tags, so you can see which issue was closed by which code.
GitHub is also integrated with Slack. Code review, pull requests are immediately visible.
When managing the code, we use a slightly adapted model from here
nvie.com/posts/a-successful-git-branching-model
Code from master is always deployed, development by pull requests in development. There is a separate branch for each task (group of joint tasks).
Pull requests make code easier to review. Inside we have a rule - a pull request must be read by someone else, except for the author. Author merjit after approval.

Answer 5

We use BitBucket + Trello + Google Docs (the main project docks, layouts, database schema and all that - very convenient) + Telegram (when online, it means you work).
Previously, there was a document on Google Docs in excel format. Forms were connected to it, which each developer filled out at the end of the work with an assessment of their activities and a brief description of what tasks they did, what problems they had, and generally writes what they think is necessary. When you enter a document, a script written in basic inside GoogleExcel (a macro is called something like this) is triggered, which forms all the data (grades and nicknames) and draws up a productivity graph. Now this is irrelevant, because. the team decreased) but it worked well. This is such a fun bike.

Answer 6

For small projects it is very convenient:
Trello (for tasks)
+ Slack (for correspondence)
you can replace Trello with something like Wrike, but in my opinion Trello is very convenient for simple projects.

Answer 7

Self-hosted Gitlab for code and code reviews. There's also documentation for developers on the wiki. TeamCity as a build server. Correspondence in Slack. In Slack, notifications from Gitlab and TeamCity are falling (very convenient, Gitlab has built-in support for Slack, there is a plugin for TeamCity). As a task tracker, we use the antediluvian version of Redmine. I plan to try YouTrack as it has great integration with TeamCity.
Documentation for managers on the Sharepoint wiki.

Answer 8

Skype, JIRA, GitHub

Answer 9

In the last place Slack, GitHub, CircleCI.
Lack of a sprint tool: without them, the workflow is difficult to track.

Answer 10

Due to the abundance of .net projects - Team Foundation Server. Requirement there, managerial Tasks for them, Test Case for them, and Change Set. Developers have the right to hit subtasks in any number. The team leader is doing this. If the PM was approved by the requirements and set as a task, then he planned it, handed it over to the team leader, then he is already responsible for the execution. Essentially a conveyor.

Answer 11

Slack, Trello, GitHub & BitBucket. Skype and mail in some places.

Answer 12

Skype, Jira, Bitbucket, Google docs

Answer 13

Good question. I asked myself this question over and over again.
I want to leave Skype.
Thanks Slack!!!

Answer 14

We store the code in GitLab, actively use Merge Request (one wrote, the other does code review).
We communicate via HipChat (+ notifications), Skype - for group calls, pair programming via screen sharing.
Continuous integration via GitLab CI - when few projects, TeamCity - for microservices (more than 10 projects).

Answer 15

We at Appomart use the following stack of productivity and communication tools for our projects:
text/audio - slack
video - skype/teamviewer task
manager - asana
API - swagger / postman
repository - Bitbucket
design / styles / layout - Zeplin / Sketchapp bug
tracking - Fabric (by the way, there is a feature to open / close a bug, many do not notice this feature, but it is useful)
prototyping - Justinmind (it is convenient to distribute prototypes to partners' devices /clients/colleagues + there is an export to PDF of the specifications of all screens in the paid version)

Answer 16

But why does no one take Bitrix 24?