Even if you are not familiar with Agile development, Taiga makes it easy to understand and work with User Stories and Tasks.
You can view a User Story as a specific part of your product, described as seen by the end user. Working with User Stories, makes it is easy to manage your project by breaking down your product into several parts. A completed User Story means that a new part of your product has been developed and is ready to be delivered to your customers. The collection of User Stories within your project results in a complete product at the end of your project.
Complex parts of a product require more complex User Stories which can be in turn broken down into specific Tasks that can be easily managed by your team.
User Stories in your project can be combined into Sprints. For details about Sprints, you can go to Working with Sprints.
Any new User Story starts either in the BACKLOG or on the KANBAN chart:
-
to learn how to add a new User Story from the BACKLOG, please see Creating a User Story from the BACKLOG
-
to learn how to add a new User Story from the KANBAN chart, please see Creating a User Story from the KANBAN chart
In Taiga you can also work with Issues. Taiga provides a dedicated module for Issues, in order to make a clear distinction between Issues and User Stories. Issues usually refer to bugs, enhancements or questions related to your product. If an Issue proves to be more complex, it can be promoted to User Story. For details about Issues, you can go to Working with Issues.
After you create a new User Story, you can access its details page where you can manage and edit its settings if necessary. For more details, you can go to How to manage a User Story.
A quick way to edit the initial settings of a User Story is to open the Edit user story form – to do this, on the BACKLOG (for User Story that are not added to a Sprint) or on the KANBAN chart, position your pointer over the row or card of that User Story and then click 
.
