Agile Development Tool

Manage Product Backlog and Sprint Backlog with agile user story map and scrum tools.

Manage Product Backlog with Story Map

User Story Mapping, a popular scrum tool, helps manage product backlog effectively by grouping user needs into user tasks, epics and user stories. A Story Map provides a list of project features required to be developed. The Scrum User Story Map in Visual Paradigm Online provides two map structures (3 or 4 levels). You can adopt the one that works best for your project's scale and complexity.

User activities, tasks and stories

Break-down a product backlog into manageable product backlog items. The standard 3-level structuring covers user activities, user tasks and user stories.

The Epics tier

The 4-level map introduces an Epics tier in between user tasks and user stories, allowing you to manage projects with higher degree of complexity.

Release planning & management

User stories are further grouped into releases, which reflects a delivery schedule agreed upon by the team and stakeholder.

Advanced drag-and-drop

All elements in a story map can be re-arranged by dragging. And when you drag a user activity in the top layer, the entire branch of user tasks and user stories will follow. Prioritization and re-arrangement of stories can be made intuitively and easily.

Inline editing

All elements can be renamed inline. You don't need go through any further windows or steps.

Click-to-add elements

To add a user story under a user task, or to add a sibling of user activity, all can be done with a single click. The ad-hoc hovering button allows adding story map elements intuitively.

User Story - 3C's, and something more

The 3C's refer to the three critical aspects of a complete user stories. The concept was suggested by Ron Jeffries, the co-inventor of the user stories practice. Visual Paradigm Online supports the 3C's, and something more

Conversation notes

Identify stakeholders' problems and find solutions through discussions, and then write down key ideas and important discussions as note items. These items provide references on user's needs and provide developers with guidelines to follow when implementing the software.

Confirmation items

List the acceptance criteria of user stories raised by the stakeholders during the discussion of requirements. This defines under what conditions and criteria the working software would be accepted or rejected.

Besides listing the acceptance criteria, you can optionally define the steps with which acceptance testing will be performed in confirming the completion of work.


Categorize user stories by adding tags.


Crystal clear log of changes made to user stories.


Configure the statuses (e.g. Todo, Pending, Confirming, etc) of user stories for progress monitoring.


Set the team member who are responsible to the user story.


Want to be informed about changes made to a user story? Just follow it.


As your project progresses, you may want to document the details of a user story somewhere. The description editor is there to serve this purpose.

URL reference

Add URL reference to a user story. Example usage: The testing page for acceptance testing of story.

File reference

Add supplementary files to a user story through the file reference feature.


Share a user story with someone by sending him a URL of the user story.

Estimate user stories based on effort and risks

A wise allocation of user stories in a sprint can result in a win-win situation for project team and end users. Two benchmarks to consider when choosing the right user stories is the effort required and the risk involved.

Visual Paradigm Online provides you with a configurable column based or two-dimensional Affinity Table to assess and compare between user stories based on their effort and risk. Through an affinity assessment, you will obtain the story points and hours for user stories, which can be used in sprint planning.

Effort and risk assessment

Drag user stories to the table cell that indicates their effort and risk. Both hour and story point will be obtained, which is a useful reference in sprint planning.

Customizable table

To assess stories based on criteria other than effort and risk, simply change the caption for x and y axis. Besides, you can change the number of rows and columns of table to fit your need.


Want to focus on user stories in particular user activity, task, release or tag(s)? The filter is there to help.

Sprint Backlog management

Create and manage sprint using the drag-and-drop GUI. Manage and organize stories with multiple sprints. Stories make in one place will be kept synchronized among story map and sprint board in real-time.

Scrum board for story status tracking

Keep an eye on the project's progress. Stories' based scrum board consists of a big board with user stories placed in different columns representing the progress status. You can view and update the progress of stories by drag-and-drop around the staged columns.

Identify right stories - 'As a _ , I want to _ , so that _'

A user story represents a small piece of business value that a project team can deliver. User story statements is a list of simple description of features told from the perspective of end users who desires the new capability with a good reason behind it. You can write user story statements under an Epic, and split it into a set of related user stories.

Let's get started!