Certainly! There's no need for different levels to have the same workflow. Instead, every flow is fit to the local context. One the same board at InkuBook...
We never set a level at InkuBook, we relied on the professional judgement of our team, tempered by our collective understanding of the near-term product vision...
Eric, I see. However, I never felt the need for tracking individual tasks, since the tasks are usually mapped to steps on our workflow (such as ABAP code, ...
Given the numbers you shared, I actually suspect that some of those 40 would be in the realm of what we call MMF's. We intentionally allowed MMF's to be bigger...
... This is what we are doing as well. We've also established a floor of 10% to ensure that development gets some time for general technical activities. ...
LeanKit Kanban looks promising. However I need a fully customizable board including swimlanes and multi tiers and it must support more than 300 "notes" on the...
I'm actually the President of Bandit Software, the makers of LeanKit Kanban. We're currently working hard on swimlanes - our goal is to deploy the first ...
Community should also find interesting about Chris' company is that they actually seem to be using a continuous community multivote for feature selection......
Ok sounds very good. I really like your user interface. Basically I would like to draw my own board with the freedom as if I was drawing on a spreadsheet or on...
my teams have been playing with AgileZen early tool, but good start. Developers are open to share what they are working on and getting feedback from customers....
... Yes, and keep doing so. It's good that one doesn't need all that much theory to get started, but I very much appreciate that it sits on strong foundations...
Hi Karl, ... Making a stand for theory is all well and dandy. What we need to be conscious of though is prior work in our field were it exists and competing...
Hi Paul, Sorry I couldn't keep up with yesterday's responses on this thread. I'll try not to repeat too much of what's been said (again, not too different...
Hi Karl The big difference about the "blue cards" was that the requirement was "Make it go faster so that it can handle five times the volume". There was huge ...
Hi Karl Purr. I like it when you light my sue. Purr. I think there are some interesting discussions come out of this thread, thank for being Wise to my...
Hi Karl I agree that we need theory. As a group we need to be very disciplined about when we talk theory and when we talk experience. When someone is asking...
This is interesting. I have not used WIP limits at the MMF level, but rather a WIP limiting policy similar to yours at the task level. one per developer. the...
Dear All So Value trumps Flow, and Flow trumps Value....... But what do people do to ensure they are delivering value rather just features or user stories? ...
5919
Viktor Klang
viktor.klang@...
Nov 4, 2009 12:36 pm
FWIW, Flow trumps waste. My split: sales increasing <-- A feature that Generates an increase in sales expense reducing <-- A feature that Reduces expenses...
Chris, <<What do other people use?>> I usually ask the one that's paying for it if he/she wants to pay for it. I guess it all comes down to it. Regards, Pablo...
Pablo, ... I'd like to think that this approach is all you need. My experience is that just because somebody's got it in the budget doesn't necessarily mean...
Brandon, << I'd like to think that this approach is all you need. My experience is that just because somebody's got it in the budget doesn't necessarily mean...
Hi Matt, We have a maximum WIP limit of 1 per developer pair. This is often reduced to say 0.5 per developer pair by splitting stories into tasks and having...
