Configuring Agile Methodology in Bitrix24
The team decided to work in Scrum. They set up a Trello board, started planning sprints in Google Sheets, recording retrospectives in Google Docs. Two months later, the board is abandoned—because tasks are entered in Bitrix24, but the board lives elsewhere. Two tools aren't synchronized; current info is unclear. Bitrix24 has a built-in Scrum module—it's tied to tasks, backlog, and reports in one place. You just need to configure it.
Scrum in Bitrix24
A Scrum project in Bitrix24 is a working group with Scrum mode enabled. Differences from a regular project:
- Backlog — list of all project tasks, from which sprints are formed
- Sprints — fixed-length iterations (typically 1–2 weeks)
- Scrum Board — Kanban within sprint with stages: "To Do," "In Progress," "On Review," "Done"
- Story Points — estimate task complexity instead of hours
Backlog Configuration
The backlog is an ordered list of tasks. Tasks are added, prioritized by the product owner, and grouped by epics (major features or directions).
Each backlog task has:
- Title and Description — phrased as User Story: "As [role] I want [action] so that [result]"
- Story Points — complexity estimate (Fibonacci scale: 1, 2, 3, 5, 8, 13)
- Epic — grouping by direction
- Priority — backlog order determines what goes into sprint first
Sprint Planning
The product owner selects tasks from the top of the backlog and drags them into a sprint. Sprint capacity is determined by velocity—how many Story Points the team closes per iteration.
Sprint parameters:
- Duration — fixed, typically 2 weeks
- Sprint Goal — text description of what the team plans to achieve
- Capacity — recommended SP volume based on previous sprint velocity
After planning, the sprint starts. New tasks aren't added to active sprint—they go to backlog for the next iteration.
Scrum Board and Daily Work
The Scrum board shows current sprint tasks by stage. Executors drag tasks between columns. The manager sees progress in real time.
For daily standup, use the project group chat in Bitrix24. Format: each member writes three points—what did yesterday, what planning today, what blockers. You can automate via bot: each day at 10am the bot posts a standump reminder to chat.
Burndown Chart
Bitrix24 builds a burndown chart automatically: the graph shows how many SP remain in the sprint by day. Ideal line—even decline from full capacity to zero by sprint end. Actual line shows real progress.
If actual line is above ideal—the team is behind. If below—ahead of schedule. This chart is the Scrum master's main tool for daily control.
Velocity and Planning
Velocity — team's average speed in SP per sprint. Bitrix24 calculates velocity automatically from completed sprints. Based on velocity, the next sprint's volume is planned and the entire backlog's completion date is forecasted.
Typical mistake—overloading the sprint. If team velocity is 30 SP and you load 50 SP, by sprint end there'll be unfinished tasks, morale drops. Bitrix24 setup includes capacity recommendations based on historical data.
What We Configure
- Scrum project: backlog, epics, Story Points
- Sprint parameters: duration, goals, capacity
- Scrum board stages for team process
- Auto-reminder for daily standup via bot
- Burndown chart and velocity tracking
- Team training: roles (product owner, Scrum master, team), ceremonies (planning, review, retrospective)