New answers tagged

0

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" hierarchies - portfolio initiatives - programs - projects - tasks, or epics - features - stories, etc. Luckily, Kanban is great at "scaling" as it ...


0

I have dealt with this issue when coaching hardware testing teams, and the solution was to borrow the concept of an "epic" from Agile methods for iterative development. The definition of "epic" I am using is simply a requirement or "user story" that provides customer value, but for legitimate reasons it cannot be completed in a ...


1

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. And here's why: the underlying source-code might be possibly-substantially(!) different. Therefore, I would "ask the team(!) what really makes the most ...


Top 50 recent answers are included