Talk to sales

Development Process: Agile Scrum, Kanban & Jira

Strapi Vietnam runs projects with 2-week Agile Scrum sprints and Kanban for maintenance, using Jira so clients can track the backlog, board, burndown, and Definition of Done with automated tests.

Talk to sales

Scrum for Development

During development, Strapi Vietnam runs 2-week sprints to keep a predictable pace. Each sprint includes sprint planning, daily standup, review, and retrospective, so clients see concrete results after every cycle.

  • 2-week sprints with clear goals
  • Concise daily standups focused on blockers
  • Reviews for clients to see real results
  • Retrospectives to improve the process
See How We Work

Kanban for Maintenance and Operations

For maintenance and operations, we use Kanban to handle emerging tickets continuously. WIP limits prevent the team from taking on too much, reducing bottlenecks and prioritizing work that directly affects users.

  • Board shows clear work status
  • WIP limits reduce context switching
  • Prioritize by operational value
  • Fits maintenance tickets, incidents, and small improvements
Discuss Your Project

  1. Scope Discovery

    Define goals, scope, acceptance criteria, and priorities before building the backlog.

  2. Backlog Refinement

    Break requirements into epics and stories, estimate work, and set priority order.

  3. Sprint Planning

    Select suitable stories for a 2-week sprint, assign clear responsibilities, and set the sprint goal.

  4. Development & Testing

    Follow the Definition of Done, with automated tests and code review to maintain quality.

  5. Review & Acceptance

    Demonstrate results to clients, collect feedback, and confirm story completion.

  6. Retrospective & Handover

    Capture lessons, improve the process, and hand over documentation and operational guides.

Transparent Project Management in Jira

Clients don't just receive reports; they can see directly where the team is working.

Clear Backlog

All requirements are captured, categorized, and status-updated in the backlog.

Epics & Stories

Large requirements are broken into epics and stories small enough to develop, test, and accept.

Visual Board

The board shows work in progress, awaiting testing, completed, and bottlenecks.

Burndown & Reports

Burndown reports help track sprint progress and detect risks early.

Clients in Jira

Clients are invited to Jira to view status, comment, and confirm work items.

Learn more →

Definition of Done

A story is complete only when it meets quality criteria, has automated tests, and required documentation.

Frequently Asked Questions

Can clients track progress?

Yes. Clients are invited to Jira to view the backlog, board, story status, and burndown reports. When needed, we can explain directly on the ticket.

Can 2-week sprints handle requirement changes?

Yes. Changes are added to the backlog, reprioritized, and scheduled for a suitable sprint. Work already in a sprint changes only when it seriously affects the sprint goal.

How is Kanban different from Scrum in Strapi Vietnam projects?

Scrum fits development phases with clear sprint goals. Kanban fits maintenance, operations, and emerging tickets that require continuous flow and WIP limits.

What is included in the Definition of Done?

A story is considered complete when code is reviewed, automated tests pass, documentation is updated, and agreed acceptance criteria are met.

Want Your Project to Be This Transparent?

Let's talk so Strapi Vietnam can advise how to apply Scrum, Kanban, and Jira to fit your scale, team, and goals.

Start a Conversation