20th November 2015
etc.venues St Paul's, London, UK

How to address operational aspects effectively with Agile practices

Matthew Skelton Skelton Thatcher Consulting Ltd

Session type: Session
Session duration: 45 minutes

About this Session

Treating operational aspects of software as 'non-functional requirements' and 'an Ops problem' rather than a core part of the software product leads to poor live service and unexplained errors in Production.

Traceability, deployability, recoverability, diagnosability, monitorability, and high quality logging are key features of a software system, along with user-visible features surfaced via the UI, or a capability of an API endpoint.

However, many Product Owners understandably feel uneasy about taking on the (necessary) responsibility for prioritising operational features alongside user-visible and API features.

This session brings Scrum Masters and Product Owners up to speed on operational features and covers proven practices for improving operability in an Agile context, empowering Product Owners to make effective prioritisation choices about all kinds of product features, whether user-visible or operational.

About the Speaker

Matthew Skelton has been building, deploying, and operating commercial software systems since 1998. Co-founder and Principal Consultant at Skelton Thatcher Consulting, he specialises in helping organisations to adopt and sustain good practices for building and operating software systems: Continuous Delivery, DevOps, aspects of ITIL, and software operability.

Matthew founded and leads the 1000-member London Continuous Delivery meetup group , and instigated the first conference in Europe dedicated to Continuous Delivery, PIPELINE Conference.

He also co-facilitates the popular Experience DevOps workshop series , and is co-editor of Build Quality In, a book of Continuous Delivery and DevOps experience reports.