Skip to main content

Main information



Working hours UTC +3

8:45 - Chatbot sends a message in the Slack app in the android-1. In a comment to a bot message, developers fill out a report according to the structure set by the bot, before the start of the daily zoom meeting:


1. Name of the project (like in jira): what tasks do you plan to do today;

2. Approximate time of completion of the PROJECT;

3. Blockers: describe all that prevents successful development;

*Reports must be written by all team members no later than 5 minutes after bot message


8:50 - Daily begins on ZOOM, in which the whole team, Tech Lead and Project Manager participate. At daily meetings, the team discusses the tasks for the day according to the Slack report


12:15 - in the Slack app in the android-1, the chatbot sends a message to the comment on the bot message, developers fill out a report according to the structure set by the bot:


1. Name of the project (like in jira): At what stage of the task you are now;

2. Blockers: describe all that prevents successful development;

3. Approximate time of completion of the PROJECT;

*Reports must be written by all team members no later than 15 minutes after bot message


17:45 - Chatbot sends a message in the Slack app in the android-1. In a comment to a bot message, developers fill out a report according to the structure set by the bot, before the start of the daily zoom meeting:


1. Name of the project (like in jira): What you’ve done today.

2. Which of your planned tasks haven’t been done today

3. Blockers: describe all that prevents successful development;

*Reports must be written by all team members no later than 5 minutes after bot message


17:50 - Daily begins in ZOOM, in which the whole team, Team Lead and Project Manager participate, during which it is discussed what the team managed to do during the day, whether they managed to complete the tasks set on the morning daily;


18:00 - end of the working day. At the end of the working day, you need to make a commit with the work done on gitlab.


*Time Doctor must be switched on during all calls

**In the morning TD should also be switched on from 8:50!!! 


  • Reporting order, according to the location of the report in the comments to the bot message. The reporting procedure is announced by the PM according to the list of developers’ reports. Team Lead, regardless of the location of the report in the comment to the bot’s message, reads it last.

  • You need to connect to ZOOM 5 minutes before the start of the Daily;

  • In the morning and evening Daily, the camera must be turned on. We turn on the sound only during our report. The background in ZOOM is prohibited, except for the blur effect. Neat appearance required.

  • Before the start of the morning Daily PM should warn who will be absent, for how long and for what reason;

  • If you need to leave work during working hours, you need to warn your project manager about this by informing him in advance of the time of your absence and the reason for which you will be absent. 

  • When you go on a break for more than 15 minutes, you need to write about this in the android-1 group, according to the design rules:

1. The amount of time you will be absent

2. The reason for which you will be absent


A few organizational points regarding Zoom:

  • Everyone should connect to the call in advance, latecomers enter without comments and greetings, at the end of the call they must report on the reasons for being late

  • On the daily, a strictly daily format is discussed - in the morning a plan for the day and blockers, in the evening a report on the work performed and blockers

  • No more than 2 minutes are allocated for each employee, if there is a clarifying question - conduct a separate call with the employee

  • Everyone must look neat, it is forbidden to attend a call with bare shoulders, not to be at the workplace (indoors), not in a taxi on the street, etc., to be with the camera turned on, not to smoke

  • We call from a computer. Not from a phone.

  • Everyone must be signed in Zoom with their first and last name in English, as in Slack.

  • Everyone must be on silent except the speaker

  • The camera must be set up so that the shoulders and the whole head are visible.

  • Everyone should be well heard

  • Each participant in the call must delve into the topic of discussion

  • It is forbidden to show symbols, nationality, religion or conduct discussions on these topics

  • On calls, the presence of third parties or other distractions is prohibited

  • It is forbidden to use any devices during the call, to be distracted from the call

  • It is forbidden to use profanity, familiarity

  • It is forbidden to breed a farce, to discuss non-working moments

  • It is forbidden to sit in hats and outerwear


Delivery of the project to QA:

  • How to Create ipa File to Transfer to QA: Video

  • After that, the received file should be uploaded into https://filebin.net, attach the link in the comments to the task, and drag it to QA. After that, you need to write to your PM in Slack that the task has been sent to QA.

  • If they find bugs, tasks will be sent to the development, and issues will be described in the comments.

  • After all the revisions, you should repeat the project transfer procedure.

  • All actions are repeated until the QA engineer writes “It's OK”.


Note:

  • We make commits on git every day. 

  • If there is no commit, the working day may not count. Or we explain the reason why there is no commit. 

  • Cause a lot of people forget or don’t want to write the daily reports. Now enter the following: Who does not write the daily report for 5 minutes after the bot message - should do 30 push-ups or 40 squats, record on video and drop to the group.







No Comments
Back to top