Actually, we want to use a Kanban board with sprints in Jira. Somehow we want to implement the Scrumban methodology.
What is exactly does scrumban mean to you? You likely can achieve this is simply using the scrum board.
Start with a Scrum board, and then, well, just don't use the bits you don't need.
Most of the time I hear "Scrumban", it translates into "scrum without estimating" (in Jira - the scrum rituals stuff isn't done in Jira, so there's no need to talk about them as well here) because you're using the Kanban principle of 1 card = 1 estimate unit. Of course, no estimation renders a lot of scrum reporting useless, and there is no cycle time reporting in Jira directly.
But the Kanban equivalence of 1 card = 1 estimate unit is the way to get something. If you were to enable story points or any numeric field as the scrum estimate unit, and then use automation or scripting to always populate it with "1", then a lot of the scrum reports would start working and give you something almost usable as cycle time.
actually, I want to use our kanban board with setting sprints and story points for every issue on that.
Kanban doesn't have sprints or variable estimates, so you can't use a Kanban board for this. You'll need to swap to a Scrum board.
If I understand correctly, we must first create a scrum board, then create sprints by that, and then just back to our kanban board to use the sprints?
As Jack I have to ask what scrumban means to you?
But if you start with a scrum board in Jira you do get the backlog view and in active sprint view you will see a simple kanban board (To Do - In Progress - Done) which you can adapt to your needs.
Additionally I always create 2 kanban boards in Jira for the same team:
maybe this is scrumban? - although I don't have any idea what this word really means
we have lots of issues on our kanban board with 8 columns (different phases) and now we decided to use sprints and story points for our issues?
Do we have to change our board to a scrum board to use sprints?
Hi @afsaneh rad
Often when people mention using "Scrumban", they do not mean what Corey Ladas did in his 2008 book on this idea.
More often they mean "Scrum, but..." (i.e. we use Scrum, except we don't do the following...) or they mean "Kanban, but..." (i.e. we use <X> interpretation of Kanban, except we don't do the following...) For either of these, teams may discuss what they are/are not doing, and then decide how Jira can help manage that, and experiment to improve from there.
Essentially this means:
Again, please take it to the team to discuss how they work, why they work that way, and how Jira might help.
Best regards,
Bill
It looks like you're new here. Sign in or register to get started.
