Body Level One Body Level Two

Body Level Three Body Level Four

A g i l e A f r i c a 2 0 1 5

DEVOPS - AGILE ON STEROIDS

So you think you’re Agile?

Stand-ups

Sprints/Iterations

User Stories and Story Walls

Retrospectives

Showcase

SCRUM

BUT…

When it’s time to deploy…

DEPLOYMENT IS A PAIN…

▫︎Deployment is manual. Requires context

▫︎ Snowflake servers

▫︎Does the code actually work? Is it not going to introduce bugs

▫︎ Versioning and rollback?

Don’t deliver on time

DON’T DELIVER ON TIME

▫︎ Process bottlenecks

▫︎Organisational

▫︎ Team

Fail to adapt to changing requirements

CHANGING REQUIREMENTS

▫︎Big Design Up Front (BDUF)

▫︎ Specific implementation details

▫︎No process to manage changes

Not disruptive in the market

NOT DISRUPTIVE

▫︎No information!

▫︎No insights into customer trends

▫︎No opportunity to iterate over ideas

Dissatisfied clients

DISSATISFIED CLIENTS

▫︎Missed deadlines

▫︎ First-mover advantage

▫︎ Software doesn’t meet the requirements

Where did we go wrong?

SILVER BULLET SYNDROME

What are the actual problems?

▫︎Culture?

▫︎Are we spending time doing the same thing over and over again?

▫︎User Feedback?

▫︎ Knowledge Silos?

Now What?

Agile is DEAD!

Let’s look for another buzzword

Culture

CULTURE

▫︎ Teamwork

▫︎Different stakeholders and skill-sets, but the SAME team

▫︎We have the same GOAL

▫︎ There has to be TRUST (Autonomous Teams)

▫︎Collaboration

▫︎Communication

▫︎Break the SILOS.

▫︎How do we optimise communication within the organisation processes?

Automation

AUTOMATE EVERYTHING!

▫︎Automated Deployment

▫︎Continuous Integration

▫︎ Every change/commit should be production ready.

▫︎Automated testing

Deployments should be boring.

AUTOMATE EVERYTHING!

▫︎Automated Infrastructure

▫︎ Infrastructure as code

▫︎ Treat your infrastructure as cattle and not horses (phoenix servers)

If it’s painful do it often

Measurement

MEASUREMENT

▫︎Metrics

▫︎ Performance metrics

▫︎ Page load-times

▫︎ Time to deploy

▫︎ Process metrics

▫︎How long does it take to release a feature?

▫︎ People metrics

▫︎User trends (time of greatest activity)

Sharing

SHARING

▫︎ Eliminate the SPECIALIST

▫︎ Share data in a way that makes sense to each stakeholder

▫︎Make information visible

▫︎Build monitors

▫︎Monitoring dashboards

▫︎Graphs of usage trends etc

The DevOps Manifesto

DEVOPS IS NOT…

▫︎ * A certification

▫︎ * A role

▫︎ * A set of tools

▫︎ * A prescriptive process

DEVOPS IS …

▫︎ * About the relationship between dev and ops

▫︎ * Cross-functional teams over organizational silos

▫︎ * Products not projects

▫︎ * Automation over documentation (and more automation... and more...)

▫︎ * Knowing that good software doesn't end with development / release

Questions?

——————————————————— @austiine04 @tc_oketch

THANK YOU