Hi all,
I'm trying to figure out how to use Jira Components in my organization. I have to admit that it's really hard for me matching together the concepts of User Stories and Components.
Here is our setup:
- one product
- one Jira Scrum project
- one Scrum board
- team of 5-9 developers, Product Owner and Scrum Master
To implement a User Story and create value to our customers we have to work on back-end tasks, front-end tasks, data base tasks and may have an UI mockup first. All tasks will be sub-tasks of the given User Story. If and only if all sub-tasks are done the User Story is done, too.
Our Scrum board shows the progress of the sprint in a transparent manner.
Reading about Components it tells me that they can be used to group tasks like front-end or back-end and display them in individual boards and having individual leads.
In my opinion (in reference to our project) it does not make sence to group tasks like this respectively use components.
- To create value to the customer it's necessary to handle all types of tasks (e.g. front-end and back-end) in one User Story.
- The overall sprint progress is not transparent, if we would use individual boards.
- Our developers are able to work on different types of tasks and try to solve User Story by User Story.
But even in bigger projects or products (thinking of Amazon website) I would expect that there a User Stories that will result in sub-tasks like front-end and back-end very often which have all to be done to create value to the customer.
What is your opinion and experience about matching or combining User Stories and Components?
Thanks in advance.
Markus
