Hi Mike

Sorry for the delay replying to you.

The difference between "injection" and "push" is really that the features are injected in order to deliver the value. i.e. The value determines the features and not an expert user who tells you what is needed. When someone tells you the features ( especially on the inputs ), they are "pushing" features into the application. The features are dependent on the value sought, not what a user says.

I've been doing analysis this way for a few years so I can say it works with Waterfall, Agile or otherwise. Its just taken me several years to work out what I actually do. So yes, this is not only for Kanban. I like the sound of Sally's Snazzy Agile Process.

Chris

Very inspiring serie, feature injection seems to be the right path to lean software development. Can't wait to read the next article ! Getting ready to share and apply it as soon as possible, your comics are a great way to explain the process.

Chris,

I'm digging this format, very cool.

I'm a bit confused about the comparison to XP at the start. What is the difference between "pushing a feature in" and "injected a feature in"? The idea that the feature is a bi-product of "pulling" something of value?

If so, I wouldn't quite agree that this is purely a Kanban thing- really, this a matter of establishing stories (features) that bring value, whether XP, Kanban, or Sally's Snazzy Agile Process. Isn't it?

Cheers,
MB