In a followup to last weeks meeting with NDM's business analysts on how we can better incorporate user needs in requirements Chrissie forwarded an interesting set of slides from some Agile guru who walks through another means of prioritising stories/ themes and epics. Probably worth a read for another perspective on prioritisaion. Normal 0 false false false MicrosoftInternetExplorer4

http://www.mountaingoatsoftware.com/presentation/84-prioritizing-your-product-backlog

http://www.mountaingoatsoftware.com/system/presentation/file/76/Cohn_SDWest2008_PriReq.pdf

Personally, I wonder if there are actually several different levels of requirements that should be nested and prioritised throughout the design process. e.g. we take the high level business and user goals, turn these into requirements, prioritise, brainstorm around high priority goals, increase the fidelity of the goals (functional themes), prioritise within the functional themes, brainstorm around themes, increase the fidelity of the themes (features) and then start design from there (this probably needs a diagram)... not too sure, open for debate and discussion, or someone telling me that's already what is being done.