It’s Agile …. like! A Corkman’s introduction to Agile software delivery

About

Today’s goals Give you a high level overview of Agile software development methodologies Explain the benefits of using Agile Explain some of the core principles & techniques Provide you with useful insights that will help you in projects/ in the workplace

AGILE

Criticism of Waterfall Infrequent releases (often NONE) Difficult to make changes during projects Silos Late integration Lack of visibility of progress Divergence between customers expectations & end product Too much emphasis on documentation Heavyweight methodology Micro-management (sticking to plan)

A new dawn

2001 The Agile Manifesto

Agile Software Development Methodologies XP (Extreme programming) SCRUM LEAN KANBAN

Characterised by Empowered teams Multiple, shorter development cycles Frequent releases Increased collaboration Embrace change Increased emphasis on quality

Characterised by Eliminating waste Process optimisation Early integration/ fast feedback Adaptive planning (instead of sticking to a plan) Continuous improvement/ constant learning Transparency Simplicity

Why is it Agile? Fast Adaptive Respond to change

Benefits Reduced risk Earlier ROI/ value Increased visibility of progress Increased predictability Increased productivity

CHANGE

Darwin “It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is the most adaptable to change.”

People will continue to learn new & better ways to build software. We aren’t finished yet …….

DIFFERENT FLAVOURS OF AGILE

SCRUM

Self organising teams/ empowered teams Team based, collaborative approach Defined roles and responsibilities Has a prescribed cycle/ rhythm (ceremonies)

SCRUM CYCLE

SCRUM Iterative and incremental development Frequent releases Fast feedback Inspect & adapt at the core Excellent techniques for planning

XP Very similar to SCRUM Beneficial elements are taken to the extreme. e.g. eliminating waste, improving processes, making things simple, automating manual tasks Multiple short development cycles, rather than a long one Big emphasis on quality & engineering practices – TDD/ BDD – Pair programming – Refactoring – Automated testing – Continuous integration

Takeaway? Awareness of these principles/ techniques Focus on continuous improvement, learning, reducing waste Appreciation of the collaborative nature of modern software development Natural capacity to work in team, to communicate and collaborate