Kanban

Mögliche Teamarbeit Besipiel Olli Panda

Kanban flow details - FirmenOnline - JMP Confluence

• Created by Matuschek, Oliver (Allianz Technology SE) on Aug 04, 2025 2 minute read

Scroll page details

We had several workshops on our way of working with Kanban and here’s a quick recap of the key agreements from these workshop:

Estimation

We will estimate starting from tomorrow on in the Refinement.

• Using the Fibonacci sequence (1,2,3,5)
• Tool of choice: Jira Planning Poker (already integrated)
• We only estimate Stories – no Tasks, no Bugs
• Spikes will be handled via timeboxing (e.g., 1d, 3d, etc.)
• We also defined criteria for Story Point estimations to make the estimation process easier:
  • 1 Story Point = Very simple stories without logic or dependencies
  • 2 Story Points = Stories that contain logic but have no cross-team dependencies
  • 3 Story Points = Stories with dependencies on at least one other team
  • 5 Story Points = Stories with dependencies involving two or more teams
  • (Details are documented in Confluence)

🚦 WIP & Blockers

• No fixed WIP limit, but:
• → Ideally work on one story at a time
• If a story is blocked, please move it to the “Blocked” column
• → Always add a comment explaining why it’s blocked

📋 Board Workflow

• Column “Testing” was renamed to “Code Review”
• → To make it clear that devs are responsible for testing here
• Assignee is responsible for driving the ticket to “Done”
• Tickets will automatically disappear from “Done” after 7 days

🧲 How do we pull new work?

• Priority 1: Stories from “Ready for Development” (top to bottom)
• → Except in urgent cases – please align with PO
• Don’t pull directly from the Backlog
• → If nothing fits in “Ready for Dev”, check with PO or BA to move topics

🔍 Stories vs. Tasks – What’s the difference?

• A Task is used when no code changes are involved and nothing needs to be deployed.
• Tasks are for recurring operational work or non-code activities.
• Spikes will also be created as Tasks, timeboxed and clearly labeled.
• Stories always involve code changes and delivery of functionality.