Low-code adaptation to Agile in a week

Adapting a Low-Code Platform for Agile: A Week-Long Transformation

Low-code platforms enable rapid process adjustments to meet evolving business needs. In just one week, a team adapted a Waterfall-oriented ITSM 365 system to Agile methodology by adding sprints, Scrum boards, and backlogs. This resolved issues with multiple tools and manual data entry, saving on licensing costs and time.

A typical scenario: a company purchases a system for waterfall projects, then the R&D department switches to Scrum, and marketing adopts Kanban. The result is three separate tools with annual expenses of around 1 million rubles plus manual data synchronization.

Problems with Rigid Systems and Low-Code Solutions

Rigid systems require separate projects for changes, force processes to fit the tool, and overload the interface.

Problem 1: Changes as a Separate Project.

Adding a "Risks" field takes months. With low-code: an administrator creates a custom field in the visual editor in minutes—a list type with values "Low/Medium/High/Critical."

Problem 2: Processes Conforming to the System.

Scrum sprints mimic stages, losing boards and priorities. With low-code: a new "Sprint" entity, parallel to Gantt.

Problem 3: Overloaded Interface.

In a waterfall task card, story points are hidden under budget and resource fields. Solution: a separate Agile view with relevant fields.

Problem 4: Lack of Scalability.

Company growth leads to methodology adjustments and extra costs. Low-code expands with modules without migrations.

The Essence of Low-Code for Project Management

Basic configuration covers 70-80% of needs: project-stage-task hierarchy, Gantt charts, critical path, effort tracking, dashboards.

Low-code adds:

• New entities (sprint, user story);
• Interfaces (Scrum boards);
• Automation (triggers, calculated fields);
• Custom metrics.

Configuration ratio:

• 80% — visual editor;
• 15% — simple scripts;
• 5% — developer.

Step-by-Step Agile Transformation

Step 1: "Sprint" Entity.

New project type "Agile." Attributes:

• Name (Sprint 1);
• Goal;
• Dates (2 weeks).

Waterfall stages are hidden.

Step 2: Modifying "Task."

Fields:

• Link to Sprint;
• Type (User Story/Bug/Technical Task);
• Estimate (days/hours).

Optional: story points, acceptance criteria.

Step 3: Scrum Board.

New view "Board":

• Columns: Created/In Progress/Code Review/Test/Done;
• Grouping by assignees;
• Colors by type;
• Card fields: number, subject, priority, avatar, estimate, deadline.

Step 4: Backlog.

List with filter "sprint = empty." Columns: number, subject, status, responsible, priority, deadline. Bulk assignment to sprints, sorting, filters.

The "Sprints" tab shows tasks by breakdown, list of sprints.

Key Takeaways

• Savings: One system instead of three—minus 1 million rub/year on licenses and manual work;
• Speed: 80% of changes without code, transformation in a week;
• Scalability: Support for Waterfall/Agile/Kanban mix without migrations;
• Efficiency: Reduced Shadow IT, cognitive load, errors;
• Automation: Triggers, dashboards for routine tasks.

Such adaptation preserves basic functionality for classic projects while adding Agile without data loss.

— Editorial Team