Comments on: Try Kanban for Ticket Driven Projects https://blogs.perficient.com/2010/04/11/try-kanban-for-ticket-driven-projects/ Expert Digital Insights Thu, 12 Aug 2010 01:20:28 +0000 hourly 1 By: Manage requirement changes inside a Sprint | Multi Shoring https://blogs.perficient.com/2010/04/11/try-kanban-for-ticket-driven-projects/#comment-2782 Thu, 12 Aug 2010 01:20:28 +0000 http://blogs.perficient.com/delivery/?p=192#comment-2782 […] of projects – we call it Ticket Driven Development. Sam Tong contributed his experience on using Kanban technology for ticket driven projects in one of his […]

]]>
By: Getting useful information out from the CFD - Multi Shoring - A Perficient Blog https://blogs.perficient.com/2010/04/11/try-kanban-for-ticket-driven-projects/#comment-2781 Thu, 15 Apr 2010 17:02:59 +0000 http://blogs.perficient.com/delivery/?p=192#comment-2781 […] As I mentioned in the previous post, CFD is the chart we can use to monitor the ticket driven/maintenance project status, while CFD […]

]]>
By: Sam Tong https://blogs.perficient.com/2010/04/11/try-kanban-for-ticket-driven-projects/#comment-2780 Wed, 14 Apr 2010 01:54:16 +0000 http://blogs.perficient.com/delivery/?p=192#comment-2780 The response to your questions:
1. The WIP set for the pipeline will enable the team to keep a healthy workload. Since from the client point of view, once they throw the tasks to the team, they already starts the counting of the time you take to get those done. So the time that the tasks are pending in the pipeline will be also consider as part of the time you spend on finishing those. For maintenance projects, that time will impact the SLA.
While, setting the WIP for pipeline or not really depends on the project reality.

2. It is OK for not setting the WIP for “In Progress” while most cases the WIP should be there, it depends on the project reality. After the team experience the project for a while, there will be a WIP no matter it is formally announced or not. To set the WIP will help you to control the workload for the team.

Overall, Kanban is very flexible, all depends on the project.

]]>
By: Steven Si (Hangzhou, China) https://blogs.perficient.com/2010/04/11/try-kanban-for-ticket-driven-projects/#comment-2779 Mon, 12 Apr 2010 19:10:15 +0000 http://blogs.perficient.com/delivery/?p=192#comment-2779 This is very educational for me. With this we can monitor ticket driven projects clearly. Thanks!

I have two questions here:
1. Why we need to set the WIP limit for pipeline?
2. Is it OK we do not set the WIP limit for “In Progress”, and keep monitoring the velocity and capacity using this model, and make it public to team?

]]>