The below is a very simple and basic Agile workflow we are trying to create, but could not achieve this in JIRA Agile. Can anyone point me a video or a link that allows us to do this end-to-end?
Release
+-------- Sprint(s)
-----------+-------- Stories
----------------------+-------- Tasks
---------------------------------+-------- Sub-Tasks
In the above the only thing that is missing is Epic, but since we can have Epics spread across a Release or Sprints I have not shown it above. But we still want a way to filter the stories by Epics, Release, and Sprint.
Apart from this we are looking for the basic burn-down chart that shows our progress at Release and Sprint level.
Can anyone help on this?
Hi Peter, Thanks for your answers. I tried to create a scrum board, and trying experimenting adding existing stories and so on with the information you had provided.
There are various ways to achieve that. If you are using JIRA Agile whate I would do is the following.
Release will be modeled in the system as Project Verison. So under project "Web Application" you will have versions 1.0, 2.0, etc.. based on your definition of a release.
https://confluence.atlassian.com/display/JIRA/Managing+Versions
Sprint will be something you create in Agile - there is a Create Sprint button in the planning view of a board. You have to create a board for that, let us know if you need help with that. In this case Sprint will be a field that JIRA Agile will control for you.
https://confluence.atlassian.com/display/AGILE/Creating+a+Sprint
Stories - you can use the issue type User Story that comes with JIRA Agile
Sub-tasks - configure sub-task issue type to your liking - quite often customers are asking for separate Dev Task, QA Task or Doc Task, but this is realy up to your specific needs.
Agile goard with give you burndown chart that you need for a sprint.
https://confluence.atlassian.com/display/AGILE/Viewing+the+Burndown+Chart
For release level you can go to the Agile tab under Project.
https://confluence.atlassian.com/display/JIRA/Viewing+a+Project's+Burndown+Chart
Again there are other ways to do that which are still very good and working. But I find this to be the most straight forward.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter, Thanks for your answers. I tried to create a scrum board, and experimenting by adding existing stories and so on with the information you had provided.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would like to view like the below.
-------------To-Do-----------In-Progress-------------Done
Story1--------------------------------------------------------
-------------Task-111---------Task-222-----------Task-333
------------------------------------Task-444-----------Task-555
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I found the reason for points 1 & 2.
For 1. Though I have added a new column, I did not map the statuses - ref: https://confluence.atlassian.com/display/AGILE/Tutorial+-+Adding+a+Column+to+a+Board
I for some reason feel this is uncomfortable. I have added QA ready as my task but don't have an appropriate mapping in the system and had to choose something like resolved but not closed
For 2. The filters had an issue
But now, I am still not done... I need some help on the getting the Burn down chart up... the estimation vs tracking are little dicey, and its not entirely clear with the documentation here https://confluence.atlassian.com/display/AGILE/Configuring+Estimation+and+Tracking.
My query is how do I really see the burn down.
For example: I have a story
It has 5 tasks as below:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.