Log In
Or create an account -> 
Imperial Library
  • Home
  • About
  • News
  • Upload
  • Forum
  • Help
  • Login/SignUp

Index
Acknowledgements Introduction Two axioms of Lean Software Development Why pull? Why kanban? Coffee cup kanban A kanban is more than an index card Kanban systems for software development An ideal case In search of one-piece flow Task leveling Concurrent pipelines Kanban synchronization WIP and Flow Buffers in space versus time Are we there yet? Time-boxed iteration: an idea whose time has come and gone Workflow Schedule is orthogonal to workflow Workflow examples Kanban workflow for product development One Piece Flow meets the V Model Flow requires a little bit of slack, but too much slack is waste A kanban token is a signal to pull value through the workflow Organization Guided self-organization Division of labor in Lean software development workflows What about training? Still not that simple? Enter the kanban Starting a Kanban system Evolution of a lean development process Start with something simple Scrum-ban Crunchy on the outside, chewy on the inside Level 2 Scrumban Off with the training wheels Kanban bootstrap Kanban flowing according to architecture Running a kanban System Kanban daily standup meetings Striking a different bargain with the business Throughput, lead time, and Deming Accounting for bugs and rework Bug scenario Option 1: reinsert defective WIP upstream Option 2: shared rework station Pool Queue Queue utilization is a leading indicator Work in process is a leading indicator Development workflows need buffers The joy of complementary side effects
  • ← Prev
  • Back
  • Next →
  • ← Prev
  • Back
  • Next →

Chief Librarian: Las Zenow <zenow@riseup.net>
Fork the source code from gitlab
.

This is a mirror of the Tor onion service:
http://kx5thpx2olielkihfyo4jgjqfb7zx7wxr3sd4xzt26ochei4m6f7tayd.onion