8
votes
Accepted
Can an Epic span multiple versions / releases?
TL;DR
Yes. There is no issue with this at all.
Discussion Points
The concept of Epics are pretty amorphous and undefined. You can find descriptions of Epics as large user stories that need broken ...
6
votes
How should a daily stand up meeting be performed in Kanban?
There aren't any Kanban-specific rules for how to run a standup. The concept of a regular - often daily - synchronization meeting exists in a number of methodologies and frameworks, and the same ...
3
votes
Can an Epic span multiple versions / releases?
"Allowed" by who/what?
Allowed by Scrum? Yes.
Scrum is a framework, entirely encompassed by the Scrum Guide. There is avast array of processes that Scrum does not prescribe, assuming/...
3
votes
Accepted
Trying to configure 2 swimlanes in Jira to be similar
If you really want to do this, you could base the swim lanes on queries. And use either a label or the flagged field to decide if something should be in the On Hold swimlane or not.
2
votes
Accepted
How to handle blocked tickets in Kanban
You could split the ticket in two. Lets say you have to deploy an application and that means you have to request access. Granting you access can take an amount of time unknown to you.
You could split ...
2
votes
Group not finding value in using a visualization board
Visualization ≠ Dependency Management
Visualizing the work is a technique, and generally solves for a problem that this group of individuals may not actually have. To find value in a solution, you ...
2
votes
How to break down work in Kanban?
In Kanban, how can we break down work?
You first need to answer
In Kanban, why do I break down work?
Is there any specific reasons to break down the work? How would this help your team?
Then, for ...
2
votes
How should a daily stand up meeting be performed in Kanban?
The daily stand-up meeting or a daily kanban meeting, should kick off your team's workday and lay out a basic strategy for completing tasks. Gather your team for a 15-minute update (an hour after the ...
2
votes
Accepted
estimating time for a step that has batch process in project management
TL;DR
It really just depends on what information you're trying to communicate. In the end, the kanban is simply yielding data points. It's up to you and your organization to collaboratively determine ...
1
vote
How to use Azure DevOps with Kanban
Here is the link to Kanban in DevOps
As for your concern, "items with estimates that vary in size from 4 hours to 14 days, or 2 to 55 story points". I think it would be better if we could ...
1
vote
Accepted
WIP vs. Value-adding cards for Kanban in IT operations / IT support
This is a pretty common situation in most work settings - where teams work on a mix of work large (projects/ epics) and small (tasks/ user stories/ tickets, etc.) Work also occurs in "natural&...
1
vote
Can an Epic span multiple versions / releases?
In my opinion – driven here mostly as a well-seasoned software developer, I would recommend that you subdivide your "epic" to consider both releases and (especially!) versions separately. ...
1
vote
Can an Epic span multiple versions / releases?
There are no rules, so yes! But this is a question to ask your team(s). If they want to do so, go for it. If not, don't.
1
vote
How to handle blocked tickets in Kanban
If tickets are frequently blocked by external teams, I'd focus on preventing those things from being blocked. Prior to starting work on the items, try to identify things that are needed from external ...
1
vote
In kanban, what should we do about routine work in each day?
I would propose that 'Keep The Lights On' (KLO) work is important in any team, as you would use it to track work as well as work against WIP limits. I personally would choose to track this through a ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
kanban × 314agile × 126
scrum × 97
kanban-board × 37
jira × 33
lean × 16
software-development × 15
user-stories × 15
scrumban × 15
team-management × 14
work-in-progress × 14
project-management-style × 12
estimation × 9
backlog × 9
multi-projects × 9
methodology × 8
development-process × 8
pm-software × 7
wip-limit × 7
scrum-master × 6
product-management × 6
tasks × 6
agile-coach × 6
meetings × 5
project-team × 4