Kanban Digest 26, c’est le meilleur du #Kanban lu cette semaine sur le Web

Lu sur Twitter
Lu sur Twitter
@alshalloway managing WIP (queues) is a proxy for managing delays. Other half is implementing feedback loops-provides ideas for better workflow-eg ATDD
@maukoquiroga It’s not about deliverything before, but on time. Allocate capacity by risk, cost of delay and opportunity cost of delay.
@maukoquiroga The first change drove by #kanban isn’t a despicable one: become aware of where we are.
@cyetain Flow… and continuous delivery allows us to « sample » reality more frequently @hakanforss
@pawelbrodzinski Portfolio Kanban isn’t about choosing the work you do; it is about choosing the work you don’t do. The conclusion from my #lkna13 session
@hakanforss A kanban system is the MVP of a process control system #klrat
@hemppah Why focusing on the system should be attractive for managers? Because about 85% to 95% of variation in performance is due to the system!
@ojuncu #accit13 #kanban Demand is higher than capacity:we don’t 2 load servers & network beyond 80% capacity, still we do that w/ ppl #LimitWIP
@hemppah « An organization organized around ‘pull’ and flow needs a very different kind of leadership from the traditional C&C. » -John Seddon
@hemppah Flow of work indicates how organization’s parts interact together. Thus, greater economy can be achieved through flow rather than scale.
@djaa_dja « Should we use #scrumban or #kanban? » is an illogical question. Scrumban = Kanban where the starting condition is Scrum. Scrumban is Kanban!
Lu sur les blogs
Lu sur les blogs
A lire l’article « Il était un fois un projet IT en Kanban (Episode 1 : Du Story Mapping au Kanban) » de Couthaïer Farfra. Au menu :
  • Story Mapping
  • Kanban pour PO
  • Kanban pour l’équipe de réalisation
  • Kanban des actions/obstacles