-
Notifications
You must be signed in to change notification settings - Fork 14
Working Process
Anton Kovalenko edited this page May 31, 2025
·
4 revisions
When it is required to create UI designs, an issue is created in YDB UI repo. Issues is labeled with area/design label.
Design issues are assigned to an iteration in YDB UI project and are discussed during regular daily meetings.
When prototypes are agreed to be good and the design effort is considered to be over, main design issue is moved to Done column in YDB UI project and linked with issues for development, assigned to YDB UI project.
Once a quarter we have a whole roadmap review session with ydb team. Frequently as a result of this meeting we alter public roadmap.
- Team uses sprints for planning. Every sprint results in a release.
- Every week we have one 1-hour meeting internally to discuss current issues and design future tasks.
- Every week we have one half-hour meeting as a demo for users.
Every day team has a half-hour sync similar to daily scrum or stand-up meeting.
Team uses story points for estimation.
- 1 sp – The minimal change that requires neither development nor test revisions. For example, updating text, refreshing an image, or removing unnecessary code.
- 2 sp – The smallest development task. This estimate is assigned to clear tasks that involve modifying one component and its tests.
- 3 sp – A complex development task that may involve modifications in multiple components or in the logic of backend interactions. Typically, it's possible to complete two such tasks in half sprint.
- 5 sp – An unclear task that obviously hides some complexities; it is not clear at the beginning how to proceed. Usually, it's not possible to complete such a task within half sprint.