We've already got sets of requirements which have been documented (via the traditional not agile approach) for a few months now. We'll be using SCRUM as part of our Agile methodology but we are still a few weeks off getting this work underway. In the meantime I've been reading up on the subject and determining best practice etc as well as trying to learn what it is all about (it looks good so far). I'll keep you posted especially when it all kicks in.
I do have a question.....I'm looking into the documentation produced and I'm happy enough with the Use Cases and Storyboards which are much, much easier than ploughing through piles of word type documents. But am obviously concerned about how detailed these should be ie, should they cover valid scenarios but also "valid invalid" scenarios etc to make sure all bases are covered (my concern if if we don't do this we give developers to scope to do what they want rather than what the business wants. I know the Scrum meetings and everyone working together should overcome this however people can be sneaky!). What are others experience in producing documentation as part of this methodology and can anyone suggest any good books, websites etc? There is an Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects however have not been able to get hold of a copy of it to review (other than one seeing one review on Amazon) as well as one or two websites. I'm coming across alot of opinions on docmentation but no examples of it (I am aware that they do have to be agile which is why there may not be any!).
I would be interested in knowing what books/resources you have found and are reading on the topics of Agile and SCRUM. Also, which did you find to be most informative, intuitive, and overall helpful.
I think documenting invalid scenarios is important. If you don't know how the system should react to invalide scenarios then something is going to break.
I haven't worked a lot with Agile methodologies myself. My knowledge of them is mostly academic.
Currently, I'm reading the book "Scrum and XP from the Trenches: How we do Scrum" by Henrik Kniberg which is basically a walkthrough of how one team has implemented scrum and how it worked for them. Not too far through but it's very easy to read as it's not your typical dry, theory textbook. My work are ordering a few more , one by Mike Cohn and another by Alistair Cockburn on Use Cases. The rest have mainly been websites:
Websites: http://www.agilemanifesto.org/, http://agilemanifesto.org/principles.html, http://jeffsutherland.com/scrum/ScrumPapers.pdf, http://video.google.com/videoplay?docid=-7230144396191025011, www.objectmentor.com, http://www.agilemodeling.com (great for the BSA/BA role and a good articile on documentation), http://www.mountaingoatsoftware.com., alistair.cockburn.us which has a great articile for Use Cases on his blog.
brought to you by enabling practitioners & organizations to achieve their goals using: