How to manage your Sprint Backlog in Eijel

In a previous post, we learned how to manage the Product Backlog. In this tutorial we will learn how to manage the Sprint Backlog.

Once you have determined the user stories you would like to include in the sprint, click their Start link in the Product Backlog and they will change their status into In Progress.

in progress stories

All of these In Progress user stories will show up in the current Sprint Backlog.

You can find out which sprint is currently active by going to your sprints at


You can now view all active user stories in the Sprint Backlog at

sprint backlog empty tasks

To add tasks to a user story, click on Add Task. A form will show up where you can enter the title of the Task and its estimate in hours.

add task

Once you have completed adding tasks to all your user stories, your Sprint Backlog will look like this:


You can easily see the total number of hours your team will need to complete the sprint. The total hours for done and in-progress tasks are also shown.

Once your team has started working on the tasks, the Sprint Backlog will be similar to this:


When your team has completed all the tasks for the user stories, the stories will show up as Done in the Product Backlog.

done product backlog

You can now end your Sprint by clicking End at the Sprints.


After clicking End, the Sprint will be marked as Done.

done sprint

You will still be able to view previous Sprints by clicking View. This way you can know what tasks were included and who worked on the tasks on previous sprints.

sprint history


How to manage defects in your agile project

Defects can occur in any project, regardless of the methodology followed during the development. We consider them as normal and accept them as part of life.

For this reason, we gave our best in creating what we believe is the currently best defect tracking tool in existence. And this tool comes free with Eijel.

Introducing the Eijel Bug Tracker.


At one glance, you can easily know the state of your project with regards to defects. You know right away the following important statistics:

  • Count of Open defects
  • Count of Show Stopper open defects
  • Count of High priority open defects
  • Count of Medium priority open defects
  • Count of Low priority open defects
  • Count of Unassigned open defects
  • Count of Fixed defects
  • Count of Ready for Retest defects
  • Total number of defects for the project

The Eijel Bug Tracker is a grand example of an opinionated software. It will not allow you to sort the columns, as it sorts itself on its own.

It follows the following rules

  1. The list is first sorted based on importance – with the highest severity on top. It follows the following order: Show Stopper, High, Medium, Low. Closed issues are always at the bottom.
  2. The list is sorted afterwards based on progress – with the newest on top. It follows the following order: New, Assigned, In Progress, Fixed, Ready for Retest. Closed issued are always at the bottom.

Once you have experienced this smart auto sorting, you will never come back to other defect tracking tools.

The bug tracker has also one of the best search functionality – as most of the time – developers are searching for specific issues and do not want to see the whole list. Most of the time, they just want to see the issues that are assigned to them or the issues they have worked on.

By clicking on the Search Icon, the search functionality will show up:

bug search

With this feature, you will be able to filter on any of the columns in the bug list.

The best features of Eijel’s Bug Tracker are not limited only on the list and on the search – when you click the title of the defect, it will bring you to a wiki page exclusive for that defect.

In our experience, the true value of a defect tracker comes from user interaction that happens within the defect. This means communication and clarification by means of comments and attachments, all fully supported by Eijel’s bug tracker.

When you click on one of the issues, you will see its wiki.

best bug tracker

The developers involved in testing and fixing can easily attach files and create threaded conversations in this wiki page.

How to manage your Scrum Team in Eijel

Once you have created a project in Eijel, you can start building your team. There is no limit to the number of members for a Scrum Team, but there are guidelines:

  1. There can only be one Scrum Master – this is mandatory and it defaults to the creator of the project.
  2. There can only be one Product Owner – you will not be able to add more than one product owner.
  3. The development team – all developers will be under this role regardless of skill set.

You can add your team members at

add team

Click on Add Member and a form will show up. Enter the details of the member and click on Send Invitation.

add dev

The member will receive an email and he will be able to accept the invitation on his own Project list.

accept delete

Once he has accepted, he will show up as a member in the Scrum Team.

After inviting all the members, the Scrum Team will look like this:

scrum team complete

There are some rules on changing the roles of members:

  1. The Product Owner can not be changed to other roles.
  2. The Scrum Master can not be changed to other roles.
  3. A Developer can be changed to a Product Owner or a Scrum Master.
  4. When the role of a Product Owner or Scrum Master has been take away, he will have a role of a Guest.
  5. A Guest role is a read-only role in the project

Here are the rules for removing members in a team:

  1. The Product Owner can not be deleted.
  2. The Scrum Master can not be deleted.
  3. When a developer is deleted, all relevant data assigned to him are smartly managed by Eijel.
  4. A Guest can be deleted.

With the rules stated above, you can easily manage the team especially when new members join or old members leave the team.

How to manage your Product Backlog in Eijel

For a new project in Eijel, your product backlog will be initially empty. The whole Scrum Team has capability of adding user stories in the product backlog, which you can access at

empty pb

To add a story, click on Add Story and a form will show up.
Create Product Backlog

Enter the title and category for the user story. Categories that you add will be available next time you add new stories.

After adding several use stories, your Product Backlog will look like this:


You can easily reorder the stories in the Product Backlog by drag-and-drop. This feature is a delightful way of organizing the stories based on importance, with the most important placed on top of the list.

To update a user story or to set its points, click on the icon after the story’s title. A form will show up after clicking the icon.

update story

You are now familiar on how to create and update user stories for your product backlog.

User Story Status and the Sprint Backlog

Each user story has a status – Todo, In Progress, and Done.

  • Todo – the user story is in queue for future sprints.
  • In Progress – the user story is in the current sprint.
  • Done – the user story has been completed and it passed the team’s definition of done.

To include a use story in the current sprint, click the Start link of the user story. The user story will have a status of In Progress then and it will show up when you view the Sprint Backlog at

active story

A user story that is In Progress can only move to Done when all the tasks assigned to it in the Sprint Backlog are complete.

story in sb

And finally, you can easily see your Product Backlog’s ideal burndown chart at





How to contact Eijel support

One of the signs of being a good company is allowing your users to contact you when they have issues or problems with your service.

With Eijel we do this by exceeding expectations. You can contact the phone number of the founder himself.


How to retrieve a lost password in Eijel

If you have forgotten your password in Eijel, don’t worry. You will still be able to access your account by creating a new password. Your old password will no longer be needed as it will be replaced by a new one.

Here is how:

  1. Go to the Password Reset page in Eijel –
  2. Enter your email and click Send Email.
  3. You will receive an email with a link to reset your password.
  4. Click the link and enter your new password.
  5. You should now be able to login to your account.

How to manage defects in an agile project

Defect management is an important part of software development, regardless of the framework you are using. For this reason, we have added a built-in bug tracker in Eijel.

In comparison with other stand-alone defect management tools like HP QC, Eijel’s bug tracker is one of a kind and definitely among the best.

A unique feature in Eijel’s bug tracker you will not find anywhere else is the built-in one-glance summary. You will know the state of the project with respect to defects in just one view.

The summary will tell you how many defects are open, show-stoppers, high, medium, low, unassigned, fixed, and ready for retest. You can also see the total number of defects for the whole project.


Searching is also not a pain compared to other tools. Eijel’s bug tracking search is one of the best available today.

issue 2

And with the integration of bug tracking with the rest of the features, Eijel is indeed the one and only complete and end-to-end solution for managing agile projects.

The beauty of Eijel’s bug tracker does not yet end there though – every issue in the list has a wiki associated with it – where you can put file attachments and threaded comments. This completely blows away any competition – not even the full stand-alone defect trackers have this feature.

best bug tracker