Sunday, July 19, 2009

AgileAustin Workshop: Rapid Requirements

First, let me begin by saying how incredibly blessed we are to have such an active, talented and passionate groups of folks in the Agile community here in Austin.

In the interest of giving back, let me share some information about the AgileAustin Workshop: Rapid Requirements, led by Scott Killen. The session was about 2 hours long and after a brief overview of the process, we dove right in. Actually going through the exercise was a great way to communicate the process and how it works, and it made the time fly by. In a real-world setting, I've tried versions of this requirements elicitation exercise, but I love these types of workshops because I always seem to pick up a nuance or detail that I didn't consider before.

Here are few high-level concepts from the session (see my link below to full notes if you are interested).

This process is great for brainstorming & group collaboration, although it might not be ideal for large groups (over 20) and remote teams.

The main steps to Rapid Requirements process are:
1. Familiarize - let everyone know the goal of the session and the main topic at hand
2. Itemize - have everyone write down the top 3-5 requirements or issues that come to mind (on post-it notes)
3. Review - collect the stickies, reading out the issues identified to the group, and place them all around the room
4. Associate - have everyone get up and begin grouping similar issues together
5. Categorize - review sets of issues and determine which 'Category' best describes those items
6. Clarify - ask the group about unclear issues and/or ask the contributor to explain
7. Prioritize - have everyone go back to their categories and hard rank the items
8. Top 3 Review - review the top 3 from each category with the group
9. Vote - give each group member small dots or stars and ask them to 'vote' for ANY item(s) they feel are very important

Some notes here: Any 'step' can be performed at any time, but you should continue to move the group ahead. For example, in the 'Review' step, the group might identify additional items, that's fine. Finally, after you Vote, do not re-order the items in the category. Leave them in place and collect the stickies in order. The Product Owner will need to sort that out later.



No comments:

Post a Comment