Data is clearly an important aspect of software-based systems, a fact that the information technology (IT) industry has understood for decades, yet many agile development teams are struggling to involve data professionals within their projects. The Agile Data (AD) methodology defines a philosophical framework for data-oriented activities within agile projects, defining ways that application developers and data professionals can work together effectively. However, philosophy isn’t enough, you also need proven techniques which support those philosophies. In this presentation Scott Ambler discusses techniques for agile database development, including: database refactoring, Agile-Model Driven Development (AMDD), Test-Driven Design (TDD), and environment/tool strategies

Agile Estimating and Planning" author, and Agile Alliance co-founder, Mike Cohn, provides detailed, proven techniques for estimating and planning any Agile project.

Agile Estimating and Planning supports any agile, semiagile, or iterative process, including Scrum, XP, Feature-Driven Development, Crystal, Adaptive Software Development, DSDM, Unified Process, and many more. It will be an indispensable resource for every development manager, team leader, and team member.

This video discuss how, for many years, we were sold the idea that Agile does not scale when it is actually Waterfall and plan-driven are the approaches that do not scale.

"Agile Estimating and Planning" author Mike Cohn discusses SCRUM certification and shares his thoughts on whether or not Scrum Master Certification is Good for the Agile Community.

Google Tech Talks, December 9, 2005, Elisabeth Hendrickson

As more teams are adopting Agile practices such as XP and Scrum, software testing teams are being asked to become "Agile" as well. But what does that mean? Is the Agile label yet another buzzword? Or could it be Agile practices are actually changing the way software is built? In this talk Elisabeth Hendrickson shares her perspective on how test teams can be more Agile based on her experiences working as a tester on Agile teams. Along the way, she'll provide an overview of how Agile practices differ from traditional practices and discuss what those differences mean for independent test teams.

Agile Development is all about developing code and seeking feedback from your users to make sure you’re developing what’s relevant. When changes are suggested, they must be affordable and reliable. Grails, along with its facility to develop test driven, is a killer combination for rapidly developing web applications. In this ZePo (Zero PowerPoint) presentation, Venkat took a test driven approach to developing a small, but, fully functional web application in Grails. Venkat covered the fundamental features of Grails along with utilising other capabilities like Ajax. At the end of this presentation Grails eXchange delegates were not only confident, but eager to roll their own web applications using Grails.

A 10 Minute introduction to test driven development and unit testing using NUnit and C#.

Test Driven Development (TDD) has become quite well known. Many developers are getting benefit from the practice. But it is possible that we can get even more value. A new practice is getting attention these days: Behaviour Driven Development (BDD). BDD removes all vestiges of testing and instead focuses on specifying the behaviour desired in the system being built. This talk will be focus on Ruby and will introduce a new BDD framework: rSpec. The ideas, however, are language independent.

Of course, "anything more than 'barely sufficient' process is waste," but what does that mean for your team, or my next project? In this 60 minute presentation from the APLN Leadership Summit at Agile2006, Todd Little shared a model to help choose the right "flavour" of Agile for different kinds of projects, and discussed the importance of 'steering' throughout the project's duration.

Duvall and Glover discuss their Jolt Award winning book, Continuous Integration: Improving Software Quality and Reducing Risk and illustrates how to transform integration from a necessary evil into an everyday part of the development process.