- Kanban basic principles state: “Start with what you have.”  No one’s roles or responsibilities change up front, whereas with Scrum, you start with (potentially) new roles, which can lead to the ‘kicking and screaming’ of which you speak.  Especially in today’s economy, the idea that a new process introduces from the start new roles is easy for individuals to interpret as “This new process is going to end my job.”

- your description of the entire process looks like a pretty good textual description of a value stream mapping for an organization.  As such, it plays a role in showing why so many ‘developer-oriented’ changes are local optimizations.  “Look at how much faster I can write code when I use Resharper.”  That’s nice, but if the bottlenecks in your process are either up or down stream from the development process, you aren’t really addressing what’s most important.

Nice post, thanks.