Training Material for Requirements Gathering
At a small software company, we have several developers who are very competent programmers but who have no formal Software Engineering training. As part of their career development it is time to offer them greater responsibilities, particularly at the earlier stages of the software lifecycle.

**What good training material is available about gathering, documenting, testing and reviewing software requirements?**  Ideally, we are looking for informal, self-guided training courses. Some of these developers would definitely prefer old-fashioned, paper books, as they commute but laptops are impractical for the journeys. We are still interested in all forms of training material though.

I'd prefer material that concentrates on practical issues, *e.g.*, how to extract meaningful requirements from the various stakeholders.

The material should definitely cover alternatives to classical requirements gathering, *e.g.*, user stories. We switch between development methodologies depending on the scope of the project and whether it is an internal or external project (and we are still learning how to do things better!).  We don't want to limit the training to techniques currently employed by my development team...
Training Material for Requirements Gathering
===

At a small software company, we have several developers who are very competent programmers but who have no formal Software Engineering training. As part of their career development it is time to offer them greater responsibilities, particularly at the earlier stages of the software lifecycle.

**What good training material is available about gathering, documenting, testing and reviewing software requirements?**  Ideally, we are looking for informal, self-guided training courses. Some of these developers would definitely prefer old-fashioned, paper books, as they commute but laptops are impractical for the journeys. We are still interested in all forms of training material though.

I'd prefer material that concentrates on practical issues, *e.g.*, how to extract meaningful requirements from the various stakeholders.

The material should definitely cover alternatives to classical requirements gathering, *e.g.*, user stories. We switch between development methodologies depending on the scope of the project and whether it is an internal or external project (and we are still learning how to do things better!).  We don't want to limit the training to techniques currently employed by my development team...