Agile software development is a yin and yang methodology.
Whilst appearing ingeniously simple to adopt, it can be the most complex and difficult switch your team or department will ever make. What appears to be a simple set of principles to follow can rapidly become what feels like a war of attrition as you and your teams fight to agree the best way to get work done.
In a nutshell, agile isn't always simple to execute.
In this session we'll talk (with some painful experience of our own) about the common mistakes teams make when switching to agile and how you can avoid them.
This is the story of how not to do agile - and what you can do instead.
Priya is an early adopter of agile. She works in a fast-paced agile environment at Redgate Software as a development lead. She has extensive experience of working in different roles in software development, such as scrum master, delivery lead and software tester. Her passion is helping build high-performing teams. Priya is also a PMI Agile Certified Practitioner, Certified Scrum Master and Microsoft Certified Technology Specialist.
Ben has 14 years' experience in IT. He started in testing and had roles in change management, release management and service assurance. Then he retrained as a scrum master and has headed up environments and data centres, quality assurance and software engineering in various roles. He is now a development lead at Redgate Software in Cambridge.
Ben has 8 years' agile experience, and has rolled out agile to a mixture of new teams and teams who have tried to adopt it before. He has worked in large corporates, SMEs and start-ups across a wide variety of sectors.