Add to Google
Lean and Scalable Requirements Information Model Published at Modern Analyst
Posted on July 9, 2009 by Dean Leffingwell in Agile Requirements, Lean ThinkingThe latest version of the Lean and Scalable Requirements Information Model for the Agile Enterprise is now published in the July ejournal of the ModernAnalyst.com. For those of you interested in trends in requirements practices, this is a good source for all things requirements and business analyst related, agile or not.
With respect to agile development, the agile methods category there has a plethora of good content.
Hi Dean,
Interesting way to capture the big picture!
One question though: in the diagram, you show:
Epic (0,1) ————> (1, *) Feature
Did I understand correctly that you account for “Epic-less” features in this case?
I see a risk there. Reminding that Epics are the conveyors of value for a business case, the risk is that one might end up having features that don’t align with the business case if you don’ enforce features to relate to one Epic. In other words, you leave the door open to add features that don’t bring any value (apparently at least).
So, what motivated you to allow for Epic-less features then?
Andrigo,
You read it correctly. Epics are often reserved for those big business initiatives that require some business case approval, new resources, etc. Features are smaller and there are typically lots of and lots of them, sometimes even maintenance related, that don’t require an epic parent. Of course, you could always parent them to “other” or whatever for purposes of tracking, but that seems like unnecessary overhead.
Features carry business value too, as do stories, so you don’t have to have a parent to be a useful child.