Your team works in sprints, but Bitrix24 is using a regular project? Tasks aren’t grouped, velocity isn’t measured, and “sprint” is just two weeks on a calendar. Without configuring the Scrum module, an agile methodology remains just talk. Bitrix24 Scrum setup enables efficient backlog management and sprint tracking. We help fix this: we set up a full-fledged Bitrix24 Scrum module—with backlog, sprints, story points, burndown chart, and clear roles.
How a Scrum Project Works in Bitrix24
Scrum in Bitrix24 is a separate project type. Create it via Tasks → Projects → Create project → Scrum. Unlike a regular project, here you have a backlog, sprints, and specific roles: Scrum Master (owns the process), Product Owner (manages the backlog), and team (executors). Technically, Bitrix24 allows one person to be both master and product owner, but methodologically that’s a mistake. We always separate these roles. Scrum projects deliver results up to 2x faster than regular projects, according to our client data—sprint planning time reduced from 4 to 2.5 hours (38% reduction) and incomplete tasks dropped from 20% to 10%.
What Are the Backlog and Story Points?
The backlog is a list of all project tasks not yet assigned to a sprint. The Product Owner populates it, prioritizes by dragging (higher = more important), and adds descriptions and acceptance criteria. Tasks are estimated in story points — an abstract measure of complexity. The scale is up to the team: Fibonacci (1, 2, 3, 5, 8, 13), linear (1–10), or size-based (S, M, L, XL). Rule: if a task exceeds 13 story points, decompose it. Large tasks won’t fit in a sprint and skew the burndown.
How to Configure Sprints and Burndown Chart
A sprint is a time-boxed iteration (typically 1–2 weeks) that produces a potentially shippable increment. Create it under Scrum → Backlog → Create sprint. The Product Owner drags tasks from the backlog. Sprint parameters: duration (1 to 4 weeks), goal (text description), and capacity — the total story points the team can deliver. Capacity is determined empirically: first 2–3 sprints are a measurement period, after which average velocity is used. The burndown chart shows remaining story points. The ideal line is a straight line from total SP to zero. If the actual line is above, the team is behind; below, the sprint is overloaded. The Scrum Master monitors the chart daily. This empirical process control reduces sprint planning time by 40% and cuts incomplete tasks by 50%.
What Are the Task Statuses in a Sprint?
Tasks within a sprint move across a Kanban board. Standard statuses: New → In progress → In review → Completed. We customize statuses to match your process. Key rule: a task is considered done only when it meets the Definition of Done — readiness criteria defined by the team in advance (code written, tests passed, documentation updated).
Advantages of a Scrum Project Over a Regular One
A Scrum project delivers transparency and predictability: the team sees how much they can accomplish, and the product owner sees when results will be ready. In practice, organizations that switch to Bitrix24 Scrum reduce sprint planning time by up to 40% and cut the number of incomplete tasks in half. According to our data, this approach roughly doubles timeline predictability.
| Parameter |
Scrum Project |
Regular Project |
| Backlog |
Yes |
No |
| Sprints |
Fixed iterations |
None |
| Roles |
Scrum Master, PO, team |
No separation |
| Burndown chart |
Built-in |
No |
| Velocity |
Tracked |
No |
Roles in a Scrum Project: Responsibilities Table
| Role |
Responsibility |
| Product Owner |
Manages backlog, prioritizes, defines acceptance criteria |
| Scrum Master |
Organizes sprints, facilitates, removes blockers |
| Team |
Estimates story points, executes tasks, self-organizes |
Common Mistakes When Setting Up Scrum
- One person filling both PO and Scrum Master roles — process control is lost.
- Sprint duration longer than 4 weeks — flexibility is lost.
- Story points are not decomposed — burndown becomes skewed.
- Definition of Done not agreed upon — tasks are “completed” without real readiness.
Deliverables
We set up Scrum for your team turnkey, delivering:
- Configured Scrum project with role assignments (Scrum Master, Product Owner, team)
- Backlog structure with acceptance criteria and story point scale
- Sprint configuration (duration, goals, capacity)
- Customized Kanban board with process-specific statuses
- Burndown chart and velocity tracking reports
- Team training on Sprint Planning, Daily Scrum, Sprint Review, and Retrospective
- Process documentation and access rights configuration
- Support for the first three sprints with adjustments
Process
- Analysis: Study current workflow, team pain points, role composition.
- Design: Define project configuration, story point scale, Kanban board statuses.
- Implementation: Create Scrum project, configure backlog, sprints, burndown chart, permissions.
- Training: Conduct workshop on Scrum rituals and Bitrix24 usage.
- Support: First 3 sprints — regular calls, configuration adjustments.
Estimated Timelines and Cost
Setup takes 3 to 7 business days depending on the complexity of your current process. Setup cost is $750 (includes 5 hours of training and first sprint support). Typical total cost ranges from $500 to $1500. Average monthly savings from improved efficiency: $2000. Contact us for a free project assessment.
We have been configuring Scrum in Bitrix24 for over 5 years, completing more than 30 projects for teams ranging from 3 to 50 people. We guarantee that after setup, your team will be able to run sprints independently. Get a consultation — we'll analyze your process and propose the optimal configuration. We offer a free project assessment.
For more details on Bitrix24 Scrum settings, see the official Bitrix24 documentation.
How a corporate portal on Bitrix24 solves the problem of information chaos?
Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.
We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).
What does the portal offer in daily work and why is it better than messengers?
In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.
Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.
Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.
Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.
HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.
Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.
Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.
How does integration with 1C and Active Directory accelerate HR management?
Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.
Types of corporate portals and key integrations
| Type |
Purpose |
Key Feature |
| Intranet |
Internal communications and services |
News, phone directory (sync with AD), meeting room booking, IT requests via BP |
| HR portal |
HR management and development |
Profiles, KPI/OKR on custom HL blocks, training, electronic document flow |
| Knowledge portal |
Documentation and regulations |
Categorization, tags, ratings, subscriptions to updates |
| Extranet |
Work with partners and contractors |
Granular permissions via CGroup and extranet module, access without VPN |
| Holding portal |
Management of multi‑company structure |
Separate workspaces, consolidated reporting, cross‑cutting BPs |
Additional integrations that deliver real value:
- Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
- IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
- Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
- EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.
Security and compliance with Federal Law 152‑FZ
The portal contains personal data, financial reports, strategic plans. We guarantee protection:
- role model via CGroup and section‑level permissions;
- two‑factor authentication (OTP, Yandex.Key, SMS);
- audit of all actions (b_event_log);
- TLS encryption for transmission and disk encryption;
- full compliance with Federal Law No. 152‑FZ "On Personal Data".
How is implementation carried out? Step‑by‑step plan
| Stage |
Duration |
What we do |
| 1. Audit |
2–3 weeks |
Interviews, process analysis, architecture, integration plan |
| 2. Setup and customization |
3–6 weeks |
Structure, roles, BPs, branding (CSS template) |
| 3. Integrations |
2–4 weeks |
1C, AD, email, telephony, EDI |
| 4. Data migration |
1–2 weeks |
Documents, directories, employees from current systems |
| 5. Training and pilot |
1–2 weeks |
Administrators, key users, pilot of 20–30 people |
| 6. Scaling |
2–4 weeks |
Connecting departments, fine‑tuning based on feedback |
- Audit — we record current processes, measure time losses.
- Design — choose portal type, plan integrations.
- Implementation — configure business processes, permissions, interface.
- Test — pilot group tests scenarios, we fix issues.
- Launch — connect all employees, train, hand over documentation.
What you receive after implementation
- Project documentation: architecture, integration scheme, business process diagrams.
- Configured portal with all integrations (1C, AD, telephony, EDI).
- Business process descriptions and instructions for administrators and users.
- 30 days of technical support after launch.
- Access to our knowledge base and migration scripts.
Post‑launch support: how to prevent the portal from becoming obsolete
After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.
Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.
Order a turnkey corporate portal implementation
Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.
