Skip to main content
Project Management

Return to Question

Tweeted twitter.com/StackProjects/status/1388463230440419328
explained situation better in response to comment
Source Link
nonthevisor
nonthevisor
  • 141
  • 2

Problem

When creating Kanban cards, I don't know how I should size them, i.e. if I have one task that I estimate to take a week and one task that should take only half a day, should they both just get one card, or should I somehow split them into cards of more equal sizes?

Situation

I don't work in a group which uses agile project management. I am trying to adapt this kind of thinking and working to optimize my own output, and if that goes well, I want to propose agile methods to my team.

What I found

I have found some related questions/answers, but none exactly like mine.

  • This answer recommends using one card and then coding it for size, following an S,M,L approach.
  • This answer says that size only matters when using WIP limits, but then cards should be of similar size.
  • This answer recommends bundling small tasks together on one card.

Question

Is there a commonly agreed upon size for Kanban cards, and if not, is there a recommended way to determine that size on a per project basis?

Problem

When creating Kanban cards, I don't know how I should size them, i.e. if I have one task that I estimate to take a week and one task that should take only half a day, should they both just get one card, or should I somehow split them into cards of more equal sizes?

What I found

I have found some related questions/answers, but none exactly like mine.

  • This answer recommends using one card and then coding it for size, following an S,M,L approach.
  • This answer says that size only matters when using WIP limits, but then cards should be of similar size.
  • This answer recommends bundling small tasks together on one card.

Question

Is there a commonly agreed upon size for Kanban cards, and if not, is there a recommended way to determine that size on a per project basis?

Problem

When creating Kanban cards, I don't know how I should size them, i.e. if I have one task that I estimate to take a week and one task that should take only half a day, should they both just get one card, or should I somehow split them into cards of more equal sizes?

Situation

I don't work in a group which uses agile project management. I am trying to adapt this kind of thinking and working to optimize my own output, and if that goes well, I want to propose agile methods to my team.

What I found

I have found some related questions/answers, but none exactly like mine.

  • This answer recommends using one card and then coding it for size, following an S,M,L approach.
  • This answer says that size only matters when using WIP limits, but then cards should be of similar size.
  • This answer recommends bundling small tasks together on one card.

Question

Is there a commonly agreed upon size for Kanban cards, and if not, is there a recommended way to determine that size on a per project basis?

Source Link
nonthevisor
nonthevisor
  • 141
  • 2

How to size Kanban cards

Problem

When creating Kanban cards, I don't know how I should size them, i.e. if I have one task that I estimate to take a week and one task that should take only half a day, should they both just get one card, or should I somehow split them into cards of more equal sizes?

What I found

I have found some related questions/answers, but none exactly like mine.

  • This answer recommends using one card and then coding it for size, following an S,M,L approach.
  • This answer says that size only matters when using WIP limits, but then cards should be of similar size.
  • This answer recommends bundling small tasks together on one card.

Question

Is there a commonly agreed upon size for Kanban cards, and if not, is there a recommended way to determine that size on a per project basis?