Making Things Done

Process

When a project starts, the following is happening:

1. A new group is created in Telegram.

2. A new Git Repository is created.

3. A new Project Board is created; as a minimum, it will have "Backlog", "To Do", "In Progress", "Verify", and "Closed" lists.

4. The Git Repository and the Project Board are integrated to the Telegram Group, so notifications appear in a chat when something important happens.

5. Team members involved in the project are added to the Git Repository, the Project Board, and the Telegram Group.

6. Task cards are added to the "To Do" list and members are assigned.

7. The responsible member moves a card to the "In Progress" list and work on an issue. If necessary, comments are added to a task card.

8. When a task is complete, the corresponding card is moved to the "Verify" list.

9. The project manager verifies the result. If everything is good, the card is moved to "Closed".

This battle-tested setup establishes a transparent collaboration environment where participants can communicate freely, follow the status of a project they are working on, and stay up-to-date with the latest changes in code.

I Have An Idea

Put your ideas, items to check or list of improvements to the "Backlog", so it's not forgotten and shared with your team members.

I Have Found A Bug

Immediately register a bug you've found in the Project Board, so others aware of a problem and responsible person can fix it as soon as possible.

I Have A Question

If you face a difficulty or something doesn't work as expected, don't just try to solve it by yourself. Let others know about it in a project's chat. Probably someone already had this issue in past and knows how to handle it.

Git Workflow

We use Feature Branching as a Git workflow in most of our projects. In this workflow a feature development happens in a dedicated feature branch and then, after review, is merged to a master branch. This scenario provides an environment when a master branch never contains work-in-progress code, and developers are able to work separately on their task not interfering with each other.

References

Git Feature Branch Workflow