Managing Requirements for Your Agile Team

A big selling point for going agile is that it reduces the requirements “burden.” The emphasis on face-to-face communication suggests that you don’t need to write much down. This is either a tremendous relief or terrifying depending on your role and expertise. It is also flatly untrue. This presentation examines the intersection between the SCRUM methodology and requirements management. How do you determine what to document and where? What are the working relationships among standards, definition of done, conditions of acceptance, and requirements? How do you exploit the benefits of agile -- team empowerment and rapid development of business value -- while maintaining the right amount of functional documentation? How do you effectively use an RM tool without losing the agile momentum? The experiences of the Clinical Looking Glass development team at Emerging Health Information Technology provide the real-world backdrop for this discussion of strategies and solutions beyond the basics.