kanban

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Is anyone using Kanban (or scrumban) for the agile management practices? What is your experience with Kanban? How does it work in large complex environments with dependencies on waterfall projects? I know the BBC use it quite extensively. See David Joyce's

Is there any plug-in/app for presenting/managing tickets from Trac bug tracking system on Kanban board? For example, I want to be able to change the status of Trac tickets by dragging-dropping them accross the board. I tried some standalone tools like AgileZen but but I couldn't find a way to integrate them with Trac. I've written two blog posts about Trac and Kanban (and the new T&K - Redux ) where we just fill a wiki-page with three columns of TracQuery-macros. There's some example source in there. It's dead-simple (no drag and drop) but it works well for us. We use the GridFlow and

I would like to start by saying I have read Rally Kanban - hiding Epic Stories but I'm still having trouble on implementing my filter based on the filter process from the Estimation Board app. Currently I'm trying to add an items filter to my query object for my cardboard. The query object calls this._getItems to return an array of items to filter from. As far as I can tell the query calls the function, loads for a second or two, and then displays no results. Any input, suggestions, or alternative solutions are welcomed. Here's my code $that._redisplayBoard = function() { that.

I'm curious as to what other people use for physical Kanban/Scrum boards in their companies. I appreciate that because of sensitive business information you may not be able to provide a photo of the board. I"m looking at to find out what does your board looks like , and how you organize user stories and tasks as they move through a typical sprint/iteration? Typically I've worked in a places that organize the board as follows with each User Story | Todo | In Progress | Ready for QA | Done | UC-001 | Domain Object, Service | DAO(Bob) | | | UC-002 | Payment UI Screen | | Payment Srv (Don)| | UC