[Closed] Kanban and concurrent activities... Anyone?

Im torn.

Is this an elaborate nigerian scam advert, a dating site advert or someone looking for ideas on how to build a titanium frame ?

It's how to deal with Broken Bronsons

I do this with sub-tasks on a user story. The story is the overall requirement,and I'll have subtasks for analysis, design, graphics, implementation, documentation, test, etc. Each on tied to the acceptance criteria for the story.

Subtasks can then be assigned to different people and have dependencies set up between them to show the bottlenecks and blockers.

I don't know if you're using any tooling, but this approach is supported by Jira and by Rational Team Concert.

<edit>

Although if the tasks are sequential I'll just pass the story on from one person to the next and have it gradually be completed.

Subtasks as mentioned would be my vote. Also make sure your WIP limits are set appropriately - definitely not more than the number of people in the team - and keep any eye on cycle time and cumulative flow to spot bottlenecks. JIRA is working well for us with kanban.

Is this about the price of curtains?.

Is it Mornington Crescent Evo?

Is this what caused that sunset ?

I'll use subtasks in JIRA, that's a good call. Ran it through my demo project and looks like I can push that live easy, got a Kanban set up showing the progress of subtasks by user story, so looks easy.

I've also drawn up a physical Kanban that'll let me track start date, completion date for each story or epic. That way I can measure a huge amount of data amount individual cadence to flex WIP effectively.

Cheers chaps, 🙂

Simulation model, I'll sell you one 🙂

Sorry to respond late. Sub-tasks would be my call too.

I come here to get away from all this kind of nonsense ... ban hammer!

Coming from Operations floor point of view, and I am known for shooting out random things.

Swim lanes are good way (not too sure how you would present it, not knowing your world)
That way you could have multiple lanes showing the time line, and what processes are taking place.
When more than one thing (not nec a process) is happening at the same time, this could be a bottleneck for you.

2 ways of doing this

1. use sub-tasks

2. don't worry about it and encourage people to do the right thing to figure out and address the bottlenecks for themselves. Self organizing team and all that.

I prefer option 2.

Option 1 in Jira makes your board instantly look very confusing.

I find that people like option 1 if they are new to agile, or are used to a culture where they only do what their manager tells them.