I started off as a nay-sayer and doubter around user stories in the Agile/Scrum space. I haven't completely revised that view, but kind of. I like the way stories let people work together. Stories are so much friendlier as a metaphor for discussing requirements. Everybody's got a story to tell - right. Of course. Everybody's got a voice and they want to be heard. I like that. It's inclusive.

Hello again,

When i did my PhD I came up with a requirements pattern language that I still use. It's really good for database driven applications and gives the analyst a running start on producing a first specification. It's at the heart of my project management method (PrinceLite) that joins up management with engineering. You can get the paper at www.princelite.co.uk/downloads.cfm. You have to sign up, but don't be shy.

Cheers,

Peter

Hello all,

Well, work on the PrinceLite proposition continues apace. I can offer something I think is workwhile and want to let people know. I've posted my versions of stripped down (almost elegant) project brief and BRS templates along with a worked case study from a system I specified a couple of years ago (that delivered successfully - thank you for asking...)

So, I'm really interested in layered requirements according to outline, high level, mid level and possibly low level requirements. If this interests you too (and why wouldn't it?) then have a look at www.princelite.co.uk/downloads.cfm. You'll have to sign up to download the templates though so I know who you are (tell the truth!).

Cheers

Peter