Agile is all about closing the gap between business and software development. Agile teams work closely with a Product Owner who prioritizes user stories on their business value. So how does a team make sure they don’t lose sight of non-functional requirements? Are user stories of any use to make infrastructure more visible in the product backlog? This talk is based on coaching experiences with many agile teams. Come and hear how these teams attempted to resolve these concerns. Find out about patterns and anti-patterns that apply to non-functional requirements …

This video demonstrates an example of agile requirements traceability. We discuss an example user story and show how detailed requirements captured as test tables can be used to build executable specifications and aid the design process. Finally we wrap up by a brief example of how we would track the progress of multiple user stories across our scrum or kanban wall.

Jeff Patton describes the different ways Agile teams deal with users and then digs in deep into story mapping – a technique that is more information rich than a simple backlog.
http://www.infoq.com/interviews/patton-story-map

We are agile, so we don’t have to estimate and have no deadlines, right? Wrong! This session will consist of an overview of the concept of agile estimation and the notion of re-estimation. We’ll learn about user stories, story points, team velocity, how to apply them all to estimation and iterative re-estimation. The lab will consist of an estimation project and doing a round or two of “planning poker”.

Jeff Patton briefly reviews the different ways that software is currently built and then describes how to create and use user personas to design and build software that has a better user experience. Jeff walks us through how to collaboratively build a user persona, what a user persona should include, and how to use these personas to write user scenarios that end up as user stories wit.

http://www.infoq.com/presentations/pragmatic-personas
Related resource
Article: Agile, Multidisciplinary Teamwork by Gautam Gosh