New answers tagged

0

I think there is at least one issue - cards are put on Kanban board which are not ready/have dependencies. You can solve it of course, by simply using additional columns, but I bet you will end up with more of those "dependency" states. Personally, I would suggest breaking down your process into two separate Kanban Boards. One for planning and ...


0

Personally I think moving cards backwards in Kanban OK as far as it is transparent. If it is whiteboard you are using - maybe introduce, moved to refine/replan Column to communicate the change. If you are using eletronic versions of Kanban, maybe you can use changelogs or workflow visualization features. This should also affect performance metrics/...


2

You're acting as if your bottleneck is something bad and you should rid of it. This may be true, but I'd like to list other options. There are 3 approaches to dealing with constraints: Improve their performance (Bogdan got it covered in his answer) (book) Use them to dictate the performance of the system (same book) Use them to pivot your business (another ...


0

Obviously, to start with, if a bug of this nature is found "in test," the item needs to be moved back to development. The priority of then handling the fix/re-engineering in development should be based on the importance of the feature of which this defect is a disruptive part.


2

The new workflow would work if it reduces the load on the designer. I'm not sure I understand the full picture, but you say: Due to the designer not having enough time, the team started to work on a lot of stories in parallel. The more stories got finished, the more work was there for the designer. [...] The designer was always lagging, developers were ...


Top 50 recent answers are included