At my work we try to be agile (though not always as successful as we might be we're not doing bad). So having put together a wireframe (see previous post starting on christmas) I'm now looking at sorting out some user stories. I'm not sure how I'll manage sprints and exciting things like velocity, but I'll try and figure out a way.
If you're not sure what the terms above are all about I'd recommend a couple of interesting books on Agile:
I've just started reading this and I'm finding it really interesting. I'm not certain I agree with everything but will give it a read.
The other book is:
This is the book our head of development recommended for us to read just as I was joining so I did, I still find it useful to return to it and see how I'm doing.
Both of those links have my special amazon give me money code in them so if you do buy them I end up with some money...
So with all of that in mind I took a look through some sites about writing user stories, it's something that I feel we don't always get right. Having read about 5 different sites this morning (there are thousands of them) I think my favourite was this:
http://codesqueeze.com/the-easy-way-to-writing-good-user-stories/
The reason is the way it breaks down the acceptance criteria into testable pieces. The other point, that lots of the sites mentioned was that it used pen and paper something as noted earlier I'm a big fan of.
When I've written a few I'll post them up here.
So with all of that in mind I took a look through some sites about writing user stories, it's something that I feel we don't always get right. Having read about 5 different sites this morning (there are thousands of them) I think my favourite was this:
http://codesqueeze.com/the-easy-way-to-writing-good-user-stories/
The reason is the way it breaks down the acceptance criteria into testable pieces. The other point, that lots of the sites mentioned was that it used pen and paper something as noted earlier I'm a big fan of.
When I've written a few I'll post them up here.
