Episode 95: The New Guardian.co.uk website with Matt Wall and Erik DoernenBurg

Agile Approach

The Guardian project embraced a unique agile development process, focusing on short iteration cycles and adaptability. Matthew Wall explains that while they don't strictly follow XP or Scrum, their approach mirrors these methodologies by emphasizing flexibility and continuous improvement. He highlights the importance of retrospectives and evolving processes, stating, "As a single team of 90, it would be a nightmare. But each team has a retrospective at the end of each iteration and recommendations go into the next iteration." 1 Erik Doernenburg adds that this approach is crucial for managing large development teams effectively 2.

   

Integration Strategies

Continuous integration played a pivotal role in the Guardian project, ensuring consistency and efficiency across the development team. Erik Doernenburg describes the use of pair programming and collective code ownership to maintain uniformity and prevent siloed work. He notes, "One of the mantras of course, is if the build is broken, you must not check in, but somebody needs to fix the build first." 3 The implementation of a build pipeline, with multiple continuous integration servers, allowed for rapid feedback and minimized downtime, a strategy crucial for large agile projects 4.

   

Thoughtworks Impact

Thoughtworks significantly influenced the Guardian project by introducing agile methodologies and fostering a culture of test-driven development. Matthew Wall recalls the initial shock of Thoughtworks' involvement, which quickly transformed the team's approach to coding. He emphasizes, "Now we're at the time where really none of the developers on our team would even consider writing a piece of code without writing a test for it." 5 This evolution of processes, driven by learning from mistakes, highlights the importance of adaptability in software development 6.