In this presentation filmed during QCon London 2007, Martin Fowler and Dan North talk about the communication gap existing between the developers and the customers or users. Closing this gap is extremely important in order to create successful software.
In this presentation filmed during QCon London 2007, Nat Pryce and Steve Freeman talk about TDD using Mock Objects. In their opinion, Mock Objects improves the software design and makes the code more easier to maintain and adapt to changing requirements.
In this presentation made during QCon 2007, Dave Thomas talks about expanding people's expertise in their domains of interest by not treating them uniformly as they had the same amount of knowledge and level of experience.
Although nearly everyone acknowledges the importance of user experience, usability often ends up pushed to the back of the queue. How then can we know whether what we are delivering makes sense and will work for our users? This presentation shows an approach to usability, focusing on activities in which users engage offers the potential for delivering dramatic improvements with much less effort.
A retrospective on Google's first Scrum implementation. Jeff Sutherland visited Google to do an analysis of the first Google implementation of Scrum on one of their largest distributed projects. Their strategy for inserting Scrum step by step into the Google engineering teams showed great insight and provides helpful lessons learned for all Agile teams.
In this presentation filmed during QCon London 2007, Boris Gloger speaks about retrospectives. Agile development teams learn and improve by inspecting and adapting. High performing teams inspect and adapt not only their code and tests, but also their methods and interactions.
In this presentation filmed during QCon London 2007, Joseph Pelrine talks about the challenges faced by organizations trying to adopt Agile methods. There are times when organizations fail to become agile, and Joseph offers some reasons why that happens. An important factor in Agile adoption is understanding and mitigating conflicts.
Architecture is perceived as a heavy-weight activity which does not fit into an Agile process, so many teams start without it, just to find themselves re-doing the software later because the code structure was not good enough to support maintainability and evolution. In this presentation, Coplien and Henney describe how to start with enough architecture to ensure long term success of the project.
InfoQ.com is a web app/portal implemented with the latest in portal technology and web development. This session shows the good, the bad, and the ugly of building InfoQ.com; from (lack of) initial requirements, design/implementation choices, deployment issues, and lessons learned along the way. The talk examines features of the site and their implementation in the web layer, domain model, and DB.
Writing a test makes you clarify your ideas about what needs to be done, and making the test pass means that you know that you've added a little more functionality today. Having a comprehensive suite of tests gives you the confidence to get on with things because you can tell when you've broken the system, and tests that are difficult to write show you where you need to improve.
In this presentation, recorded at QCon London, Paul Downey, who is Chief Web Services Architect for BT and a participant in many standards groups, talks about the Web and why he believes its architecture is superior to that of SOAP/WSDL-based Web services.
In this presentation recorded during QCon London 2007, Rachel Davies, director of Agile Alliance, talks about the Agile development cycle starting with user stories and planning the releases. This presentation is less about "why" one should use Agile over other development process, and more about the practical "how" one should proceed about being agile.