Scrum Setup in Bitrix24
Your team works in sprints — in theory. Tasks get dumped into a shared list, a sprint is just "the next two weeks," and the retrospective is replaced by "seems fine." Without proper tools, Scrum becomes chaos with hints of planning. Bitrix24 has a full-featured Scrum module: backlog, sprints, story points, burndown chart, and roles. But it comes empty — you need to configure it for your team.
Scrum Project
Scrum in Bitrix24 is a separate project type. Created via Tasks → Projects → Create Project → Scrum. A regular project and a Scrum project are different entities: Scrum adds backlog, sprints, and specific roles.
When creating a Scrum project, assign:
- Scrum Master — owns the process. Ensures rituals are followed, removes blockers, facilitates meetings.
- Product Owner — product manager. Manages the backlog, prioritizes, decides what enters the sprint.
- Team — project participants who complete sprint tasks.
Roles are assigned in the Scrum project settings. One person can technically be both Scrum Master and Product Owner in Bitrix24, but methodologically it's an error.
Backlog
The backlog is a list of all project tasks not attached to a sprint. The Product Owner fills the backlog, prioritizes by dragging (higher = more important), adds descriptions and acceptance criteria.
Tasks in the backlog are estimated in story points — an abstract measure of complexity. In Bitrix24, story points are set in the task card. The scale is up to the team: Fibonacci (1, 2, 3, 5, 8, 13), linear (1–10), or sizing (S, M, L, XL).
Rule: any task over 13 story points should be decomposed. Large tasks don't fit in a sprint and distort the burndown.
Sprints
A sprint is a fixed time period (usually 1–2 weeks). Created in Scrum → Backlog → Create Sprint. The Product Owner drags tasks from backlog into the sprint.
Sprint parameters:
| Parameter | Description |
|---|---|
| Duration | 1–4 weeks, fixed for all sprints |
| Sprint Goal | Text description: "Launch customer portal" |
| Capacity | Total story points the team can complete |
Capacity is determined empirically: first 2–3 sprints are measurement, then average velocity.
Burndown Chart
The burndown chart shows how many story points remain in the current sprint. The ideal line is straight from total SP to zero by sprint end. The real line shows actual burndown.
If the line goes above ideal — the team is falling behind. If below — the sprint is overloaded or estimates are too high. The Scrum Master tracks burndown daily.
Access: Scrum → Active Sprint → Burndown Chart.
Task Stages in Sprint
Tasks in the sprint move across a Kanban board. Standard stages: New → In Progress → Under Review → Completed. Stages can be customized for your process.
Key rule: a task counts as done only when it meets Definition of Done — readiness criteria the team defines in advance (code written, tests passed, documentation updated).
What We Configure
- Scrum project creation with role assignments (Scrum Master, Product Owner, team)
- Backlog formation: task structure, acceptance criteria, story point scale
- Sprint setup: duration, goals, capacity determination
- Kanban board customization
- Burndown chart setup and velocity tracking
- Team training: sprint planning, daily standup, retrospective