top of page

Implementing Agile and Other Methodologies: Insights from Industry Experts

Updated: Aug 3, 2023



In today's fast-paced technology landscape, successfully delivering projects on time and within budget is a critical factor for organisations. To shed light on effective project management methodologies, we reached out to members of the London CTOs to share their thoughts and experiences.


Let's dive into their perspectives on implementing Agile and other methodologies for successful technology project delivery.

On this topic we gained insights from the following members of the LCTOs: James Conroy-Finn, John Wards, Mark Batty and Rajani Rao.


James Conroy-Finn: Embrace Adaptability and Collaboration

James highlights the importance of tailoring methodologies to fit the team's needs rather than applying a one-size-fits-all approach: ‘Some consultants shoehorn overly prescriptive processes into any and all teams thinking one size fits all. It doesn’t’.


He suggests establishing a baseline and conducting retrospectives to facilitate continuous improvement. Delegating responsibility for problem-solving to team members and celebrating their successes encourages collaboration and creates a culture of iterative improvement. James states that you should ‘treat your process like you do your product’ and follow a cycle of collaboration, delivery, reflection, and improvement.


John Wards: Emphasise Small Batch Sizes and Engineering

John's perspective on Agile centers around the principle of shipping in small batch sizes as well as taking engineering seriously. He believes that Agile software development should focus on delivering valuable increments of work. By adhering to this philosophy and not getting caught up in rigid processes, teams can maintain agility and adaptability. He also says ‘I never capitilise agile unless it’s at the start of a sentence. You can’t do agile, you can be agile though’.


Mark Batty: Building Blocks and Continuous Improvements

Mark loathes the idea of process idolisation and suggests that no single methodology is a perfect fit for all situations: “I prefer the idea of process building blocks you can take apart and rebuild to monitor and adapt processes (and related tools) to achieve continuous improvements.” By promoting the notion of methodologies as modular building blocks that can be dismantled and reconstructed to unique needs, he highlights the need for continuous improvement by monitoring and adapting the processes and tools over time. Mark also emphasises the importance of measuring progress against one’s own baseline and not comparing to external standards.


Rajani Rao: Lean Agile and Focus on User Experience

Rajani shares her experience with Lean Agile, utilising weekly sprints to deliver minimal viable products for customer feedback. She emphasises the importance of a robust CI/CD pipeline that ensures the code reaches production. Rajani also advises prioritising user/customer experience and suggests that it is important to ‘think about the digital journey of the users and ensure it’s seamless’, as well as using metrics effectively to measure conversions, and adjusting the scope of delivery to prioritise if necessary. She also highlights the significance of knowledge sharing within the team through effective backlog management and refinements. Using retrospectives to derive Kaizen (good change) and 1-1, can contribute to the development of a growth mindset, foster a culture of feedback, and enable self-organising high-performance teams.


Implementing Agile and other project management methodologies requires a thoughtful approach that aligns with the team's needs and the project's objectives. The insights shared by the members of LCTOs emphasises the value of adaptability, collaboration, continuous improvement, and a user-centric focus. By leveraging the principles and practices from various methodologies while tailoring them to suit specific circumstances, organisations can increase the likelihood of successful project delivery within time and budget constraints.


bottom of page