@John Funk The Kanban Maturity Model is for teams moving toward a full Kanban experience, and personal WIP are recommended at the first level, as teams begin their move to Kanban. https://kanbanize.com/kanban-resources/kanban-software/kanban-maturity-model
@Subramaniam Shastri I haven't seen this feature in jira software, but you can set up swimlanes for individual team members.
So I need to account for a specific scenario :
Currently WIP Limits are set on the delivery board at a team level. However the Tech Lead also actively spends time on discovery board. So I am trying to determine if i can account for time for the Tech Lead on the discovery board and delivery board and also for the team on the delivery board.
Any thoughts ?
I know a team lead who was having trouble fulfilling their sprint commitments because they were stretched between several different roles. After months of this, he finally just learned to take on less because he had to be realistic about his time and commitments. But I think it's easier to evaluate those limits in Scrum.
You might look into an add-on like Capacity Tracker. https://marketplace.atlassian.com/apps/1218151/capacity-tracker
Hey @Subramaniam Shastri - The user should determine how must of their available time is being spent on each board and factor that into each board's WIP limits. In other words, if the Tech Lead spends 30% on one board versus 70% on another, then factor that percentage towards the WIP limits. So, if there are 3 devs plus the Team Lead on the 30% board, then you might want to use 5 or 6 for the column WIP limit.
You don't want to be operating at a Level 0 KMM - you should be moving beyond that. Implement steps that help you mature, not stay where you are. :-)
When teams choose to split their workflow into different streams and Kanban boards, such as Discover-Delivery-Release, people who work on the multiple streams are put in a difficult position of making their capacity and WIP visible to teammates and stakeholders.
One way to mitigate that issue is what John suggests for adjusting WIP limits based upon the expected capacity for a specific stream (e.g. Discovery). Another way is to adjust the Kanban board's entry and exit points to cover more of the product lifecycle, from Discovery to Release. Using this second approach may better align with how the team works as people's capacity (and WIP limits) are applied to everywhere they help develop valuable products.
You have asked two questions:
Automated change from Discovery to Delivery:
This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events