Metrics at every level of the Agile organization receive scrutiny: Measuring value, team performance, progress, quality, and even code design attributes will be taken into consideration.
This talk gives practical tips for adopting an agile approach to planning, team interactions and risk management. When the culture shifts, teams achieve goals sooner and safety is greatly enhanced.
In this presentation, the causality between performance in the small (individuals and teams) and performance in the large is highlighted and explained.
This talk covers Deliberate Practice in Software Development, a.k.a. the theory behind craftsmanship. Areas covered include nature vs nurture, the value of practice, & elements of deliberate practice.
Agile came from small, colocated projects in the 1990s. Agile development now sits in a larger landscape and should be viewed accordingly. This talk discusses the new, larger agile development space.
This talk summarizes the results of 4 years of industry surveys around agile technique adoption and effectiveness. Reality can be very different from the rhetoric in mailing lists, articles and books.
Integration tests are a scam, they burden you with long-running, fragile, hard-to-understand test suites. Learn the two-pronged attack that solves the problem: collaboration tests and contract tests.
Dave Nicolette and Karl Scotland try to introduce non-technical managers to one of the most popular Agile development techniques: Test-Driven Development (TDD).
Alan Shalloway, CEO and founder of Net Objectives, presents the Lean software development principles and practices and how they can benefit to Agile practitioners.
Jeff Sutherland, co-creator of Scrum, and Guido Schoonheim, CTO of Xebia, present an actual case of reaching hyper-productivity with a large distributed team using XP and Scrum.
Craig Smith and Paul King present their experiments with new Agile ideas leading them to better results, increased productivity and quality.
Williams and Stout share their recent experience with a large distributed team, the planning hurdles they encountered and how they passed them, and their recommendation: avoid large distributed teams.