Starts with a good introduction to Kanban as applied in TPS. I am wary of extending Kanban so literally from manafacturing to software. I believe software development is a design process and thus needs a different set of underlying principles. I think the Toyota Product Development (Michael Kennedy has a good book on it) is a better starting point. The flow is around funneling design decisions using set based design to come up with the optimal design given all the known constraints. I think we are heading in that direction, but the picture isn't clear to me yet.
Hope is Not a Risk Management Strategy
A good post on software delivery, risk management and other good stuff. This gem is worth repeating "..many teams adopting agile practices start with perhaps the worst practice of all - stand-ups. Effective stand-ups rely on a high level of trust and a willingness to put yourself out there, and to challenge others when they aren't. A team who doesn't have that [TRUST] typically finds stand-ups that end up not actually exposing impediments."
An interesting look at Lean fast food.
The Seven Pillars of an Agile Team: Introduction
An interesting take on what makes an Agile team successful. I wonder if Agile adds anything?
Coding: Keep method/variable names positive
An interesting look at making code more clear by being positive.
Dreyfus Model of Kanban Adoption
Some good info in helping identify different levels. It wouldn't be hard to generalize it.
Good exploration of simple versus elegant in code design.
No comments:
Post a Comment