September 28 & 29, 2020 | Virtual
Please login or join to subscribe to this thread
I did not understand if you are talking about the method/system (Kanban) or about a tool (JIRA). After working with several tools to support Kanban boards (let me say that Kanban is a whole method not a board then today people call Kanban board to everything which looks like color postist in a wall or similar) the key is change the way of thinking and behave. No tool (at least tools I use like Azure DevOps) will give you alerts except for putting a label in red or things like that in a specific card if and only if you assign a date to it. The point is: a Kanban board will not show alerts or things like that. It does not matter in Kanban. The alert for each one is the position of bucket where the card is located.
Thanks for the response, Sergio. My mistake, should have listed questions separately.
1. I am interested to know about WIP limit in Kanban board, has it helped? Can you also list a threshold for MVP in backlog prioritizations?
2. Dependency management is second question, where JIRA is not very helpful so how do you manage it?
1. It is a good idea to reduce dependencies as much as possible between work items. If you are writing stories, remember the I in INVEST stands for independent.
2. Story maps can be used to highlight dependencies (drawing arrows between related work items) but if you are looking at tooling support, I'm only familiar with the Atlassian suite so not sure whether other products do a better job of handling that.
Thanks for the guidance listed, Kiron. Very helpful.
We use JIRA to map our epics and stories. However, I am more interested in tagging epic dependencies. Any thoughts? is it a manual effort in excel?
I think that VersionOne would provide you with this type of automated tool.
If there are multiple User Stories that have dependencies between multiple Epics - I would retrospect on either: A. slicing the buckets in different groupings or B. investing time in creating a dependecy & prioritization view in Jira (or one of Jira workflows) to closely manage them with PO
Thanks for the response, Andrew. VersionOne sounds interesting. We don't use that within the bank.
I will follow the guideline you provided for user stories. Just that some of my products are such that I am relying on cross channel partners who have their way of listing Epics which are too many as I feel. Mine would be 2-3 Epics as part of their larger initiative which makes it tricky to map dependency. However, I will try the method you have described for my epics set.
@ Andrew Soswa, @Kiron Bondale, @ Sergio Luis Conte
Thank You! Very helpful and timely....
Please login or join to reply