October 6, 2011

Webinar Recording - Requirements and Agile: Keeping up with Change

Events
Agile
Thanks to everyone who joined us for the Requirements and Agile: Keeping up with Change webinar. If you missed the event, take some time to watch the Requirements and Agile: Keeping up with Change recorded webinar. Attendees asked several interesting questions, all of which we weren’t able to address during the webinar. To follow up, and invite others to participate, we’ve included the Q&A below. http://youtu.be/SV4Xtsqyf00

Q&A

What is the flow in Agile? For instance, requirements will be broken down to user stories and then tasks… I think the flow can be anything that works for you and your project. If your customers, market, or users are used to working with requirements, you don’t want to change that relationship, but you do want to supplement it with stories for the benefit of your Agile team. In other cases, often the story comes first, then requirements, then tasks. So the story is "as a user, I want to be able to check my account balance from my mobile phone" then requirements would add details on security, platforms supported, and nonfunctional items. Does Seapine provide robust requirement management solutions? We do. TestTrack RM, our requirements management tool, excels at managing the entire chain: story > requirements > test case > test execution > issues > code. Can a CCB (Change Control Board) co-exist with Agile? There is nothing in Agile that says you cannot include other traditional activities. However, it does state that you want to minimize documentation and make decisions quickly. So, if your CCB meets once a month and only considers issues that are written up with impact analysis and so on, it’s probably not the kind of board that would easily co-exist with Agile. However, if your CCB meets more frequently and is on board with faster decision making, there is no reason why it can’t co-exist with Agile. Are there any specific guidelines for writing better requirements and user stories in an Agile environment? There are a number of books and web sites that provide advice about writing requirements and working with user stories. Bob Galen just gave me a copy of his book, Scrum Product Ownership, that covers the entire product ownership process, including working with the user community to build user stories and working with the Scrum team to refine stories. Thought Clusters is another good resource. Of course, you should also check out Seapine’s blog, The Seapine View, for Agile-related articles and best practices.