I guess I’m not alone when I say that a large number of the workshops that I’ve facilitated in the past have been based on gut feel and some sort of practical, logical approach to getting the desired outcomes. It was therefore good to read “Requirements by collaboration”. Agile practitioner Ellen Gottesdiener published this book in 2002. It provides some very useful pointers to anyone looking to facilitate a requirements gathering workshop, concentrating heavily on best ways to get the most out of your workshop participants.
The main problem that I’ve found with requirements gathering for digital products / software is to find a good balance between thinking about technical viability on the one hand and addressing customer needs on the other. I believe it’s critical to take user needs (even those needs that users might not yet be aware of) as a starting point for thinking about use cases and requirements.
However, I believe it’s equally important to keep sight of technical viability and the incremental nature of software development. This means that it’s very hard to fully predict what the final product is going to look like or how exactly it’s going to function, but one can still foresee – even on a high-level – the technical complexity or risks involved in a specific product. In short, both the user element and the technical aspect need to be taken into account when gathering requirements.
“Requirements by collaboration” by no means provides the holy grail towards resolving all the common problems with regard to gathering and prioritising requirements (nor does it promise to). However, the book does go a long way in providing useful ingredients of a successful requirements workshop:
- Create a shared purpose – Spending time drafting a purpose statement pior to the workshop is likely to be of great value when it comes to both planning the workshop structure and instilling a shared purpose among your workshop participants.
- Questions to ask as part of the workshop preparation – Thinking upfront about your workshop purpose and desired outputs means that some of the following questions are bound to creep up. Who has a stake in the product? Which user problems is the product looking to solve? Who will interact with the product or software? I like the way Gottesdiener in which positions these questions against a context of ‘ending with the beginning’. She subsequently applies the ‘plan-do-check-adjust’ approach to thinking about desired workshop outputs first.
- Techniques and deliverables to match your purpose – Whilst Gottesdiener sometimes gets a bit too academic for my liking, the book does provide a wide range of practical techniques and deliverables to consider in relation to the workshop objective(s) you’re trying to achieve. Techniques like “the parking lot” (to deal with topics that are relevant to the project but not to current activities) or suggestions on how to best deal with ‘difficult participants’ are all very useful in thinking about ways to get the most out of your workshop.
Main learning point: I found “Requirements by collaboration” particularly helpful in the way it focuses on creating a clear purpose statement for a workshop and practical workshop deliverables to aim for. The way in which Gottesdiener weaves workshop purpose, structure, participants and outcomes together is very useful. At the times the book tends to get a bit too ‘academic’ for my liking but it nevertheless gives readers plenty of practical techniques and suggestions to run with.
Related links for further learning: