About Feature Injection

Feature Injection has been my favorite will-o'-the-wisp over the past month or so, starting from the point where I discovered that the "founding document" for the concept is a set of photos of Chris Matts's moleskine notebook which he wrote on a plane and uploaded to picasa in 2009. I'm still digesting the ideas, which I was completely unable to read in photo form, but was further able to track down as a set of comics on Agile Journal as follows:

Episode 1: getting all the information before you commit in code
Episode 2: determining project value
Episode 3: minimum set of marketable features
Episode 4: identifying variants
Afterlude: How FI fits into Business Analysis as a Knowledge Management Process

When Chris says to allow readers to "pull" information, rather than "pushing" it on them, he's serious about it! I hope it doesn't mess with the system too much to have links to all five posted in one place.

Here's another helpful link which includes the five comics plus an introductory essay: http://www.lulu.com/items/volume_66/7362000/7362946/3/print/lulu_word_comic_vFinal.pdf

I've also blogged again on this topic with more info: http://pagilista.blogspot.com/2011/11/bdd-feature-injection-and-fallacies-of.html

Comments

A Corporate Agile 10-point Checklist

I'm pretty sure my few remaining friends in the "small, collocated team agile" community are going to desert me after this, but I actually have a checklist of 10 things to think about if you're a product owner at a big company thinking of trying out some agile today. Some of these might even apply to you if you're in a smaller place. So at the risk of inciting an anti-checklist riot (I'm sorry, Pez!), I am putting this out there in case it is helpful to someone else. From http://www.yogawithjohn.com/tag/yoga-class/ Here's what you should think about: 1. Your staffing pattern. A full agile project requires that you have the full team engaged for the whole duration of the project at the right ratios. So as you provision the project, check to see whether you can arrange this staffing pattern. If not, you will encounter risks because of missing people. Concretely it means that: a. ...

Requirements Traceability in Agile Software Development

One of the grim proving grounds for the would-be agile business analyst (henceforth "WBABA") is the "traceability conversation." Eventually, you will have to have one. You may have seen one already. If you haven't, you may want to half-avert your eyes as you read further. It gets a little brutal. But if you close them all the way, you can't read. From: http://www.highestfive.com/mind/how-to-perform-a-successful-interrogation/ Dialogue: WBABA : ...so in summary, we complete analysis on each story card, and then we support the developers as they build it that same iteration! Corporate Standards Guy: but how do you do traceability in agile? You have to have traceability. It's broadly recognized as an important factor in building rigorous software systems. These software systems permeate our society and we must entrust them with lives of everyday people on a daily basis. [The last two sentences are an actu...

Your Agile Transformation Needs to Start with a Quiet Phase

From a really great blog post on agile adoption: http://smoovejazz.wordpress.com/2011/02/16/an-agile-approach-for-adopting-agile-practices/ I've observed some different agile transformation patterns, and maybe you have too: Just Do Standups (Shoot, then Aim): some people feel that since you're "agile," you should just start doing stuff, like daily standups, and then build more of the the plan as you go. Find a team and start doing some agile with them! Start a revolution one practice at a time, one team at a time. Pros: you're very busy from the start. Cons: what exactly are you doing and why? KPI-Driven Change (Aim, then Shoot) : some people who have worked in large corporations for a while will tell you that to get the respect of the people, you need to start with a plan, support the plan with awesome printed and online collateral. Then you "kick off," tell teams what to do, and measure them using "Key Productivity Indi...

Pragmatic Agilist

Search This Blog