Great suggestions. I'll go in a little later this week and update some of those items. I was in a hurry and just wanted to get something up there to start. It definitely needs work and assistance from everyone in the group and I appreciate the feedback and suggestions.
On Nov 8, 2007, at 2:09 PM, Arafat wrote:
On Nov 8,[masked]:21 PM, Travis Robertson <[address removed]> wrote:
I've actually put up a few ideas on the wiki. It's not an exhaustive
list, just something to get us started. Take a look, add some ideas,
start a debate - whatever works for you!
I like what you've done. I would suggest one thing: add a business case to each item. e.g. You have an item that fans should be able to link to bands. I'm not sure what this means. If you add a business case such as "so that fans have a portal page that tracks their favorite bands" then it becomes more descriptive.
From a scrum/agile perspective this format has several benefits:
- It makes estimation easier.
- It makes it easier to sort features by order of importance.
- Acceptance tests have a context for their inclusion.
- If we have an external customer then they have to defend their request for a feature. This cuts down on unnecessary requests.
This is good if you're going to do follow a "release early, release often" paradigm.
Please Note: If you hit "REPLY
", your message will be sent to everyone
on this mailing list ([address removed])
This message was sent by Arafat ([address removed]) from The Nashville Ruby on Rails / Agile Software Meetup Group.
To learn more about Arafat, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here Meetup.com Customer Service: [address removed]
632 Broadway New York NY 10012 USA