Martin Harbolt discusses Agile leadership practices promoting self organized teams and finding the proper rhythm for completing Agile projects with success.
David Hussman, David Laribee, Jeff Patton, Richard Sheridan and Susan Standiford discuss forming and building successful teams: hiring new people, pairing, combining people of different levels, etc.
Dan North reviews many Agile practices and concepts, mentioning what has really made the difference over the years and what has not, outlining what helps high performing teams to do their job.
Randy Shoup shares 10 lessons learned from eBay: Partition Everything, Asynchrony Everywhere, Automate Everything, Everything Fails, Embrace Inconsistency, Expect (R)evolution, Dependencies Matter, Respect Authority, Never Enough Data, Custom Infrastructure.
Spike Morelli discusses best practices behind the creation of Programmatically Generated Images, a tool for building and deploying system images that remain unchanged through QA, staging and production.
Karthik Dinakar presents the case of his team which attempted to be as agile as possible in order to fulfill the short-term goals but missed the long-term ones because some of the Agile best practices were ignored. He tells the story of how his team finally managed to come back on course and which are the practices that he considers as necessary for success.
This session addresses abstract notion of simplicity, looks at why it is critical in modern UI design and answers questions: Why does simplicity matter? Is there a meaningful definition of simplicity? Why do design processes and good intentions undermine simplicity? What processes and techniques can software developers use to achieve simplicity?
In this presentation recorded during QCon SF 2008, Neal Ford, an architect at ThoughtWorks, shows 10 ways to write better code. This is practical advice for developers, but application architects can benefit from it too.
In this talk Robert C. Martin outlines the practices used by software craftsmen to maintain their professional ethics. He resolves the dilemma of speed vs. quality, and mess vs schedule. He provides a set of principles and simple Dos and Don'ts for teams who want to be counted as professional craftsmen.
In this presentation, recorded at QCon London, Cap Gemini's Steve Jones explains his concept of a business service architecture. Topics covered include how to apply SOA to existing systems, the problems one runs into when SOA is driven by technology, and the structural and organizational impact of business-driven SOA.
Ian Cartwright presents some of his work (developed with Martin Fowler) on Event Patterns, including: Event Sourcing, Event Collaboration, Parallel Model, and Retroactive Event. These patterns can be used in scenarios where a sequence of domain model changes may need to be recorded, reversed, corrected, or simply observed.